CVE-2026-91090

LOWPre-NVD 3.93.9—
EchelonGraph scoreHIGH confidence

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

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

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

A vulnerability was determined in GPAC up to f1219cde. The affected element is the function gf_node_activate_ex of the file scenegraph/base_scenegraph.c. This manipulation causes stack-based buffer overflow. It is possible to launch the attack on the local host. The exploit has been publicly disclosed and may be utilized. Upgrading to version abi-16.23 is sufficient to fix this issue. Patch name: 9eb40df4448b88d6a6ce3454657c06f47eff0b24. The affected component should be upgraded.

CVSS v3
3.9
EG Score
3.9(high)
EG Risk
34(Track)
EG Risk 34/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
Severity39% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

September 15, 2026

Last Modified

September 17, 2026

References (9)

Vendor Advisories for CVE-2026-91090(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 10× in last 7d / 23× 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-24 14:04 UTCEPSS rescore
  2. 2026-09-23 19:22 UTCEG score recompute
  3. 2026-09-23 19:22 UTCGHSA enrichment
  4. 2026-09-23 17:54 UTCEPSS rescore
  5. 2026-09-22 16:01 UTCEPSS rescore
  6. 2026-09-21 21:09 UTCEPSS rescore
  7. 2026-09-20 20:16 UTCEPSS rescore
  8. 2026-09-20 16:44 UTCEG score recompute
  9. 2026-09-20 16:44 UTCGHSA enrichment
  10. 2026-09-18 19:28 UTCEPSS rescore
  11. 2026-09-17 19:32 UTCEPSS rescore
  12. 2026-09-17 14:21 UTCNVD updateCVSS v4 → 0.9
  13. 2026-09-17 14:19 UTCEG score recompute
  14. 2026-09-17 14:19 UTCGHSA enrichment
  15. 2026-09-17 14:19 UTCMITRE cvelistV5CVSS v4 → 2.4
  16. 2026-09-16 14:09 UTCEPSS rescore
  17. 2026-09-16 05:15 UTCEPSS rescore
  18. 2026-09-15 14:52 UTCEG score recompute
  19. 2026-09-15 14:52 UTCGHSA enrichment
  20. 2026-09-15 08:26 UTCEG score recompute
  21. 2026-09-15 08:25 UTCNVD updateCVSS v4 → 0.9
  22. 2026-09-15 07:43 UTCEG score recompute
  23. 2026-09-15 07:42 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-91090?
CVE-2026-91090 is a low vulnerability published on September 15, 2026. A vulnerability was determined in GPAC up to f1219cde. The affected element is the function gfnodeactivateex of the file scenegraph/basescenegraph.c. This manipulation causes stack-based buffer overflow. It is possible to launch the attack on the local host. The exploit has been publicly disclosed…
When was CVE-2026-91090 disclosed?
CVE-2026-91090 was first published in the National Vulnerability Database on September 15, 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-91090 actively exploited?
CVE-2026-91090 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.5% of all scored CVEs.
What is the CVSS score of CVE-2026-91090?
CVE-2026-91090 has a CVSS v3 base score of 3.9 (NVD).
How do I remediate CVE-2026-91090?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-91090, 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-91090

Explore →

Is Your Infrastructure Affected by CVE-2026-91090?

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

Book a Demo →Browse All CVEs