OSV-2020-1850
Heap-buffer-overflow in fmt::v6::basic_string_view<char>::basic_string_view
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=21763
Crash type: Heap-buffer-overflow READ 2
Crash state:
fmt::v6::basic_string_view<char>::basic_string_view
fmt::v6::basic_format_arg<fmt::v6::basic_format_context<std::__1::back_insert_it
fmt::v6::basic_format_context<std::__1::back_insert_iterator<fmt::v6::internal::
What each source reports
OSV No score
Heap-buffer-overflow in fmt::v6::basic_string_view<char>::basic_string_view
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=21763
Crash type: Heap-buffer-overflow READ 2
Crash state:
fmt::v6::basic_string_view<char>::basic_string_view
fmt::v6::basic_format_arg<fmt::v6::basic_format_context<std::__1::back_insert_it
fmt::v6::basic_format_context<std::__1::back_insert_iterator<fmt::v6::internal::
- Record
OSV-2020-1850- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
libfmtOSS-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-2020-1850 is a vulnerability with no CVSS score yet in libfmt, published September 26, 2020. No source lists public exploit code. A source reports a fix.