A security flaw has been discovered in GPAC up to f1219cde. Affected by this vulnerability is the function stbl_GetSampleInfos of the file isomedia/stbl_read.c of the component MP4Box. The manipulation results in reachable assertion. The attack must be initiated from a local position. The exploit has been released to the public and may be used for attacks. Upgrading to version abi-16.23 addresses this issue. The patch is identified as 49dee5cad329cfed310c1682703df7daa47df31a. It is advisable to upgrade the affected component.
CVE-2026-90613
Score 3.3 from GitHub Security Advisory (severity: LOW) published 2026-09-14. a secondary CVSS source baseline 3.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.3
- EG Score
- 3.3(high)
- EG Risk
- 31(Track)EG Risk 31/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 computedSeverity33% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 2%
- KEV
- Not listed
Published
September 14, 2026
Last Modified
September 16, 2026
References (9)
- cna@vuldbhttps://github.com/gpac/gpac/
- cna@vuldbhttps://github.com/gpac/gpac/commit/49dee5cad329cfed310c1682703df7daa47df31a
- cna@vuldbhttps://github.com/gpac/gpac/issues/3822
- cna@vuldbhttps://github.com/gpac/gpac/releases/tag/abi-16.23
- cna@vuldbhttps://github.com/r1ck9-2q/cve_summit/blob/main/Vuln-GPAC-MP4Box-Assertion-Failure-in-stbl-Handling.md
- cna@vuldbhttps://vuldb.com/cve/CVE-2026-90613
- cna@vuldbhttps://vuldb.com/submit/913520
- cna@vuldbhttps://vuldb.com/vuln/403195
- cna@vuldbhttps://vuldb.com/vuln/403195/cti
Vendor Advisories for CVE-2026-90613(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 18× in last 7d / 18× 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-09-19 09:43 UTCEG score recompute
- 2026-09-19 09:43 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-16 15:29 UTCEG score recompute
- 2026-09-16 15:29 UTCGHSA enrichment
- 2026-09-16 15:19 UTCNVD updateCVSS v4 → 1.9
- 2026-09-16 14:52 UTCEG score recompute
- 2026-09-16 14:52 UTCGHSA enrichment
- 2026-09-16 14:45 UTCMITRE cvelistV5CVSS v4 → 4.8
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 21:05 UTCEG score recompute
- 2026-09-14 21:05 UTCGHSA enrichment
- 2026-09-14 02:20 UTCEG score recompute
- 2026-09-14 02:20 UTCNVD updateCVSS v4 → 1.9
- 2026-09-14 01:45 UTCEG score recompute
- 2026-09-14 01:44 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-90613?
When was CVE-2026-90613 disclosed?
Is CVE-2026-90613 actively exploited?
What is the CVSS score of CVE-2026-90613?
How do I remediate CVE-2026-90613?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-90613
Is Your Infrastructure Affected by CVE-2026-90613?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.