Belledonne Communications bcg729 through 1.1.2 contains an out-of-bounds read vulnerability in the decodeSIDframe() function in src/cng.c that allows unauthenticated network-adjacent attackers to trigger a heap read beyond buffer boundaries by sending a zero-length comfort-noise RTP payload. A zero-length payload causes an integer underflow in the uint8_t filter order calculation, which wraps to 255 and is clamped to 10, causing the function to unconditionally read 11 bytes from a zero-byte buffer, resulting in media process termination or silent consumption of adjacent heap memory as reflection coefficients.
CVE-2026-71980
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-17. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 27%
- KEV
- Not listed
Published
August 17, 2026
Last Modified
August 17, 2026
Advisory Details (3)
Auto-updated Aug 17, 2026Belledonne Communications bcg729 1.1.2 Out-of-Bounds Read via decodeSIDframe() | Advisories | VulnCheck
https://www.vulncheck.com/advisories/belledonne-communications-bcg729-out-of-bounds-read-via-decodesidframeOut-of-bounds heap read in decodeSIDframe() on a zero-length RFC 3389 comfort-noise payload (CVE-2026-71980) · Issue #23 · BelledonneCommunications/bcg729 · GitHub
https://github.com/BelledonneCommunications/bcg729/issues/23Vendor Advisories for CVE-2026-71980(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 19× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-21 04:55 UTCEG score recompute
- 2026-08-21 04:55 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 17:22 UTCGHSA enrichment
- 2026-08-20 05:50 UTCGHSA enrichment
- 2026-08-19 18:17 UTCEG score recompute
- 2026-08-19 18:17 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 06:14 UTCGHSA enrichment
- 2026-08-18 18:33 UTCEG score recompute
- 2026-08-18 18:33 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 07:00 UTCGHSA enrichment
- 2026-08-17 19:27 UTCEG score recompute
- 2026-08-17 19:27 UTCGHSA enrichment
- 2026-08-17 18:22 UTCEG score recompute
- 2026-08-17 18:00 UTCEG score recompute
- 2026-08-17 18:00 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-71980?
When was CVE-2026-71980 disclosed?
Is CVE-2026-71980 actively exploited?
What is the CVSS score of CVE-2026-71980?
How do I remediate CVE-2026-71980?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-71980
Is Your Infrastructure Affected by CVE-2026-71980?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.