OSV-2025-111
Stack-buffer-overflow in absl::debugging_internal::ParseLocalNameSuffix
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=395959258
Crash type: Stack-buffer-overflow WRITE 1
Crash state:
absl::debugging_internal::ParseLocalNameSuffix
absl::debugging_internal::ParseName
absl::debugging_internal::ParseClassEnumType
What each source reports
OSV No score
Stack-buffer-overflow in absl::debugging_internal::ParseLocalNameSuffix
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=395959258
Crash type: Stack-buffer-overflow WRITE 1
Crash state:
absl::debugging_internal::ParseLocalNameSuffix
absl::debugging_internal::ParseName
absl::debugging_internal::ParseClassEnumType
- Record
OSV-2025-111- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
bloatyOSS-Fuzz |
Commit ranges | Not evaluated |
Not evaluated means the source gave git commits or a range we can't read, so we can't tell which releases are affected. A fixed version beside it is the source’s own claim.
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
OSV-2025-111 is a vulnerability with no CVSS score yet in bloaty, published February 13, 2025. No source lists public exploit code. A source reports a fix.