CVE-2026-90827

LOWPre-NVD 3.33.3—
EchelonGraph scoreHIGH confidence

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

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

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

A vulnerability was identified in GPAC 26.07.0. This affects the function gf_node_deactivate_ex of the file scenegraph/base_scenegraph.c of the component MP4Box. Such manipulation leads to use after free. The attack must be carried out locally. The exploit is publicly available and might be used. Upgrading to version abi-16.23 is able to mitigate this issue. The name of the patch is 49dee5cad329cfed310c1682703df7daa47df31a. You should upgrade the affected component.

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 computed
Severity33% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

September 14, 2026

Last Modified

September 15, 2026

References (9)

Vendor Advisories for CVE-2026-90827(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 / 26× 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-25 10:53 UTCEG score recompute
  2. 2026-09-25 10:53 UTCGHSA enrichment
  3. 2026-09-24 14:04 UTCEPSS rescore
  4. 2026-09-23 17:54 UTCEPSS rescore
  5. 2026-09-22 16:01 UTCEPSS rescore
  6. 2026-09-22 03:57 UTCEG score recompute
  7. 2026-09-22 03:57 UTCGHSA enrichment
  8. 2026-09-21 21:09 UTCEPSS rescore
  9. 2026-09-20 20:16 UTCEPSS rescore
  10. 2026-09-18 21:25 UTCEG score recompute
  11. 2026-09-18 21:25 UTCGHSA enrichment
  12. 2026-09-18 19:28 UTCEPSS rescore
  13. 2026-09-17 19:32 UTCEPSS rescore
  14. 2026-09-16 14:09 UTCEPSS rescore
  15. 2026-09-16 05:15 UTCEPSS rescore
  16. 2026-09-15 14:54 UTCGHSA enrichment
  17. 2026-09-15 14:34 UTCEG score recompute
  18. 2026-09-15 14:34 UTCGHSA enrichment
  19. 2026-09-15 14:31 UTCNVD updateCVSS v4 → 1.9
  20. 2026-09-15 13:43 UTCEG score recompute
  21. 2026-09-15 13:43 UTCGHSA enrichment
  22. 2026-09-15 13:42 UTCMITRE cvelistV5CVSS v4 → 4.8
  23. 2026-09-14 22:20 UTCEG score recompute
  24. 2026-09-14 22:19 UTCNVD updateCVSS v4 → 1.9
  25. 2026-09-14 21:54 UTCEG score recompute
Show 1 more
  1. 2026-09-14 21:54 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-90827?
CVE-2026-90827 is a low vulnerability published on September 14, 2026. A vulnerability was identified in GPAC 26.07.0. This affects the function gfnodedeactivateex of the file scenegraph/basescenegraph.c of the component MP4Box. Such manipulation leads to use after free. The attack must be carried out locally. The exploit is publicly available and might be used.…
When was CVE-2026-90827 disclosed?
CVE-2026-90827 was first published in the National Vulnerability Database on September 14, 2026, with the most recent update on September 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90827 actively exploited?
CVE-2026-90827 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 94.7% of all scored CVEs.
What is the CVSS score of CVE-2026-90827?
CVE-2026-90827 has a CVSS v3 base score of 3.3 (NVD).
How do I remediate CVE-2026-90827?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-90827, 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-90827

Explore →

Is Your Infrastructure Affected by CVE-2026-90827?

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

Book a Demo →Browse All CVEs