Every CVE Search/ Get API key

OSV-2020-182

Heap-buffer-overflow in hb_array_t<OT::IntType<unsigned char, 1u> const> hb_array_t<OT::IntType<unsigned

No scoreFix available

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=20249

Crash type: Heap-buffer-overflow READ 1
Crash state:
hb_array_t<OT::IntType<unsigned char, 1u> const> hb_array_t<OT::IntType<unsigned
OT::UnsizedArrayOf<OT::IntType<unsigned char, 1u> >::copy
OT::SBIXGlyph::copy

What each source reports

OSV No score

Heap-buffer-overflow in hb_array_t<OT::IntType<unsigned char, 1u> const> hb_array_t<OT::IntType<unsigned

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=20249

Crash type: Heap-buffer-overflow READ 1
Crash state:
hb_array_t<OT::IntType<unsigned char, 1u> const> hb_array_t<OT::IntType<unsigned
OT::UnsizedArrayOf<OT::IntType<unsigned char, 1u> >::copy
OT::SBIXGlyph::copy
Record
OSV-2020-182
Updated
2026-11-02

Affected packages

Affected packages
PackageAffectedFixed
harfbuzz
OSS-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

History
RecordedChangedSources
first indexedOSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

OSV-2020-182 is a vulnerability with no CVSS score yet in harfbuzz, published June 24, 2020. No source lists public exploit code. A source reports a fix.

References

MoveEnter Open