OESA-2026-4750: speex security update

Published Nov 11, 2026
·
Updated

Speex is an Open Source/Free Software patent-free audio compression format designed for speech. The Speex Project aims to lower the barrier of entry for voice applications by providing a free alternative to expensive proprietary speech codecs. Moreover, Speex is well-adapted to Internet applications and provides useful features that are not present in most other codecs. Security Fix(es):

Speex (libspeex) through 1.2.1 contains an out-of-bounds write vulnerability in speexbitsreadwholebytes() in libspeex/bits.c that mishandles length truncation for non-owned SpeexBits buffers. Attackers can stream crafted Speex data into buffers set up with speexbitsinitbuffer() or speexbitssetbitbuffer() to corrupt heap or stack memory and crash applications.(CVE-2026-116741)

Affected Software

1 affected componentFixes available
openeuler/speex<1.2.1-3.oe2403sp3
1.2.1-3.oe2403sp3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade openeuler/speex to a version that resolves this vulnerability.

    Fixed in 1.2.1-3.oe2403sp3

Event History

Nov 11, 2026
Advisory Published
via OSV·12:25 PM
Data Sourced
via OSV·12:25 PM
DescriptionSeverityAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

Which applications are exposed to this issue?

Applications using libspeex through 1.2.1 are exposed when they process attacker-controlled Speex data using non-owned SpeexBits buffers initialized with speex_bits_init_buffer() or speex_bits_set_bit_buffer().

2

What does an attacker need to exploit the vulnerability?

An attacker needs to be able to stream crafted Speex data to a vulnerable application. No authentication or user interaction is required according to the supplied severity vector.

3

What is the likely impact of successful exploitation?

Crafted input can cause an out-of-bounds write that corrupts heap or stack memory and crashes the application. The provided severity information indicates high availability impact and low integrity impact.

4

How can I determine whether my application is affected?

Check whether it uses libspeex version 1.2.1 or earlier and whether its code paths process untrusted Speex input through buffers configured with speex_bits_init_buffer() or speex_bits_set_bit_buffer().

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203