CVE-2026-92475

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory (severity: LOW) published 2026-09-16. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A weakness has been identified in GPAC 26.08-DEV. This impacts the function wait_for_header_and_parse of the file src/utils/downloader.c. This manipulation of the argument Content-Range causes out-of-bounds read. The attack requires local access. The exploit has been made available to the public and could be used for attacks. Upgrading to version abi-16.26 will fix this issue. Patch name: c74a3065038ede35c1c7b75fa493a69ef6bcdb84. It is recommended to upgrade the affected component.

CVSS v3
5.3
EG Score
5.3(high)
EG Risk
28(Track)
EG Risk 28/100SSVC: Track

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 computed
Severity53% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

September 16, 2026

Last Modified

September 17, 2026

Advisory Details (3)

Auto-updated Sep 16, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

GitHub - gpac/gpac: GPAC Ultramedia OSS for Video Streaming & Next-Gen Multimedia Transcoding, Packaging & Delivery · GitHub

https://github.com/gpac/gpac/
github_commit

commit c74a3065038e (gpac/gpac)

Fix landed in gpac/gpac commit c74a3065038e — awaiting tagged release

https://github.com/gpac/gpac/commit/c74a3065038ede35c1c7b75fa493a69ef6bcdb84
generic

Heap buffer overflow in wait_for_header_and_parse (src/utils/downloader.c:3822) parsing a truncated Content-Range response header · Issue #3859 · gpac/gpac · GitHub

https://github.com/gpac/gpac/issues/3859

Vendor Advisories for CVE-2026-92475(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 12× 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.

  1. 2026-09-20 00:29 UTCEG score recompute
  2. 2026-09-20 00:29 UTCGHSA enrichment
  3. 2026-09-18 22:55 UTCEG score recompute
  4. 2026-09-18 22:55 UTCGHSA enrichment
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-17 21:22 UTCEG score recompute
  7. 2026-09-17 21:22 UTCGHSA enrichment
  8. 2026-09-17 19:32 UTCEPSS rescore
  9. 2026-09-16 21:00 UTCEG score recompute
  10. 2026-09-16 20:25 UTCNVD updateCVSS v4 → 1.9
  11. 2026-09-16 19:54 UTCEG score recompute
  12. 2026-09-16 19:54 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-92475?
CVE-2026-92475 is a medium vulnerability published on September 16, 2026. A weakness has been identified in GPAC 26.08-DEV. This impacts the function waitforheaderandparse of the file src/utils/downloader.c. This manipulation of the argument Content-Range causes out-of-bounds read. The attack requires local access. The exploit has been made available to the public and…
When was CVE-2026-92475 disclosed?
CVE-2026-92475 was first published in the National Vulnerability Database on September 16, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92475 actively exploited?
CVE-2026-92475 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.2% of all scored CVEs.
What is the CVSS score of CVE-2026-92475?
CVE-2026-92475 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-92475?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-92475, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-92475

Explore →

Is Your Infrastructure Affected by CVE-2026-92475?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs