{"id":"CVE-2026-116741","kind":"vulnerability","aliases":["CVE-2026-116741"],"related":[],"title":"Speex: out-of-bounds write in bit reader lets crafted audio corrupt memory","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.","summary":"Speex (libspeex) through 1.2.1 has an out-of-bounds write in speex_bits_read_whole_bytes() when the bit buffer is set with speex_bits_init_buffer() or speex_bits_set_bit_buffer(). Streaming crafted Speex data can corrupt heap or stack memory and crash the application.","severity":"high","cvss":8.3,"epss":null,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["c","libspeex","media-servers","package","voip"],"not_affected_if":["no-untrusted-audio-input"],"how_to_check":"- Check whether the application links libspeex: `pkg-config --modversion speex` or `ldd <binary> | grep speex`\n- Search the codebase for `speex_bits_init_buffer` or `speex_bits_set_bit_buffer`\n- Check the installed version against the sources: `speex` through `1.2.1` is affected, fixed version unknown","fix":"- Upgrade libspeex to a release newer than `1.2.1` once a fixed version is published (unknown in the sources)\n- Until then, avoid feeding untrusted Speex streams into buffers set up with speex_bits_init_buffer() or speex_bits_set_bit_buffer()","status":"open","published_at":"2026-10-26T22:16:58+00:00","first_seen_at":"2026-10-26T22:25:34+00:00","triaged_at":"2026-10-26T22:27:41+00:00","updated_at":"2026-10-26T22:27:41+00:00","category":"package","confidence":0.5,"triage":{"at":"2026-10-26T22:27:41Z","model":"claude-haiku-5-5","output":{"fix":"- Upgrade libspeex to a release newer than `1.2.1` once a fixed version is published (unknown in the sources)\n- Until then, avoid feeding untrusted Speex streams into buffers set up with speex_bits_init_buffer() or speex_bits_set_bit_buffer()","reach":"unknown","title":"Speex: out-of-bounds write in bit reader lets crafted audio corrupt memory","impact":"high","summary":"Speex (libspeex) through 1.2.1 has an out-of-bounds write in speex_bits_read_whole_bytes() when the bit buffer is set with speex_bits_init_buffer() or speex_bits_set_bit_buffer(). Streaming crafted Speex data can corrupt heap or stack memory and crash the application.","category":"package","nicknames":[],"who_cares":["libspeex","c","voip","media-servers"],"confidence":0.5,"needs_auth":"unknown","worst_case":"Memory corruption crashes the app, possibly allowing code execution","analyst_note":"Find the fixed Speex version and confirm whether the default buffer path is affected, using the NVD entry and upstream Speex commits for libspeex/bits.c.","how_to_check":"- Check whether the application links libspeex: `pkg-config --modversion speex` or `ldd <binary> | grep speex`\n- Search the codebase for `speex_bits_init_buffer` or `speex_bits_set_bit_buffer`\n- Check the installed version against the sources: `speex` through `1.2.1` is affected, fixed version unknown","needs_analyst":true,"not_affected_if":["no-untrusted-audio-input"],"who_is_affected":"Applications that decode Speex audio from untrusted sources, such as VoIP, voice chat or media servers, and that use the non-owned buffer API (speex_bits_init_buffer or speex_bits_set_bit_buffer) are exposed. Programs that only decode local files they control, or that use the default owned-buffer path, are less exposed. unknown whether the default path is safe.","user_interaction":"no","needs_special_setup":"yes","severity_if_unknown":"high"},"cost_usd":0.000707,"input_tokens":3380,"output_tokens":738,"severity_before":"high"},"analyst_status":null,"analyst_note":null,"search":"'-116741':17A,20A '-2026':16A,19A '1.2.1':31B,79C 'applic':75B,135C 'attack':106C 'audio':12A 'bit':8A,41B,47B,53B,58B,60B,90C,118C,123C,125C 'bound':5A,37B,85C 'buffer':48B,55B,61B,105C,113C,120C,126C 'byte':44B,93C 'c':21B 'contain':80C 'corrupt':13A,67B,128C 'craft':11A,63B,109C 'crash':73B,134C 'cve':15A,18A 'data':65B,111C 'heap':68B,129C 'init':54B,119C 'length':98C 'let':10A 'libspeex':22B,29B,77C 'libspeex/bits.c':95C 'media':24B 'media-serv':23B 'memori':14A,71B,132C 'mishandl':97C 'non':102C 'non-own':101C 'out-of-bound':2A,34B,82C 'own':103C 'packag':26B 'read':42B,91C 'reader':9A 'server':25B 'set':50B,59B,114C,124C 'speex':1A,28B,40B,52B,57B,64B,76C,89C,110C,117C,122C 'speexbit':104C 'stack':70B,131C 'stream':62B,108C 'truncat':99C 'voip':27B 'vulner':87C 'whole':43B,92C 'write':6A,38B,86C","nicknames":[],"mitigations":[],"who_affected":"Applications that decode Speex audio from untrusted sources, such as VoIP, voice chat or media servers, and that use the non-owned buffer API (speex_bits_init_buffer or speex_bits_set_bit_buffer) are exposed. Programs that only decode local files they control, or that use the default owned-buffer path, are less exposed. unknown whether the default path is safe.","tier":"B","verified":{},"analyst_revisit_at":null,"first_public_at":"2026-10-26T22:16:58+00:00","kev":null,"cvss_vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","cvss_by":"disclosure@vulncheck.com","poc_count":0,"sources":[{"source":"nvd","external_id":"CVE-2026-116741","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-116741","severity":null,"published_at":"2026-10-26T22:16:58+00:00","modified_at":"2026-10-26T22:16:58+00:00","first_seen_at":"2026-10-26T22:25:34+00:00","fetched_at":"2026-10-26T22:25:34+00:00","note":null}],"documents":[],"notice":"Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai"}