CVE-2026-116741
Speex (libspeex) through 1.2.1 contains an out-of-bounds write vulnerability in…
- Risk score
- 46/100
- CVSS
- 6.5 v3.1
- Exploit chance (30 days)
- 0.4%
- Published
- 26 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- Speex (libspeex) through 1.2.1 contains an out-of-bounds write vulnerability in speex_bits_read_whole_bytes() in libspeex/bits.c that mishandles length truncation for non-owned SpeexBits buffers. Attackers can stream crafted Speex data into buffers set up with speex_bits_init_buffer() or speex_bits_set_bit_buffer() to…
- Affected
- See advisory
- Fix
- Apply the vendor's security update; see the linked advisory.
- Exploitation
- No known exploitation
Why it is Yellow
- CVSS 6.5 medium
References
- https://github.com/xiph/speex
- https://github.com/xiph/speex/blob/Speex-1.2.1/libspeex/bits.c#L177
- https://github.com/xiph/speex/issues/42
- https://gitlab.xiph.org/xiph/speex/-/merge_requests/32
- https://hackmd.io/@haindpwn/speex-bits-read-whole-bytes-oob-write
- https://www.vulncheck.com/advisories/speex-through-1.2.1-out-of-bounds-write-via-speex-bits-read-whole-bytes
Original description
Speex (libspeex) through 1.2.1 contains an out-of-bounds write vulnerability in speex_bits_read_whole_bytes() in libspeex/bits.c that mishandles length truncation for non-owned SpeexBits buffers. Attackers can stream crafted Speex data into buffers set up with speex_bits_init_buffer() or speex_bits_set_bit_buffer() to corrupt heap or stack memory and crash applications.
Last activity 26 Oct 2026. Patch Forecast updates every hour.