CVE-2026-132765

MEDIUMPre-NVD 6.66.6
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.6 from GitHub Security Advisory (severity: MODERATE) published 2026-11-19. A secondary CVSS source baseline 6.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-129351 (ENISA EUVD) · GHSA-gmg6-rv8r-m9ch (GitHub Security Advisories)Source: ENISA EUVD

6.6EG
EchelonGraph verdictPlan mitigationThe upstream fix is not in a release yet: until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule, then apply it (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.6Exploit: No code on recordExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

GPAC MP4Box through 26.07.0 contains a use-after-free vulnerability in gf_node_try_destroy because Conditional node commands keep raw pointers to target nodes freed by gf_sg_reset(). Attackers can supply a crafted XMT scene processed with -info or -add to trigger heap use-after-free, crashing the process and corrupting heap memory.

CVSS v3
6.6
EG Score
6.6MEDIUMhigh confidence
EG Risk
46
EG Risk 46/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity66% × 45%
Impact severity (EG Severity): CVSS 6.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: An upstream fix is merged but not yet in a tagged release. Until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule, then apply it.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.6): severity, escalated by confirmed exploitation. This CVE's 6.6 is its impact severity (EG Severity), not escalated.

EG Severity
6.6 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

An upstream fix is merged but not yet in a tagged release. Until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule, then apply it.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 18, 2026

Last Modified

November 19, 2026

Advisory Details (6)

Auto-updated Nov 18, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
Web page

GPAC MP4Box through 26.07.0 Use-After-Free in gf_node_try_destroy via Conditional Command | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gpac-mp4box-through-26.07.0-use-after-free-in-gf-node-try-destroy-via-conditional-command
Web page

pocs/res/gpac/MP4Box/125/125_gf_node_try_destroy_scenegraph_base_scenegraph_c_704 at main · sigdevel/pocs · GitHub

https://github.com/sigdevel/pocs/blob/main/res/gpac/MP4Box/125/125_gf_node_try_destroy_scenegraph_base_scenegraph_c_704
Web page

gpac/src/scenegraph/base_scenegraph.c at v26.07.0 · gpac/gpac · GitHub

https://github.com/gpac/gpac/blob/v26.07.0/src/scenegraph/base_scenegraph.c#L700-L710
GitHub commit

commit 5e620eff3bea (gpac/gpac)

Fix landed in gpac/gpac commit 5e620eff3bea — awaiting tagged release

https://github.com/gpac/gpac/commit/5e620eff3bea16972dd948b2a153e416ffb1c81d
Web page

[security] scenegraph/base_scenegraph.c:704 Use-After-Free in gf_node_try_destroy · Issue #3764 · gpac/gpac · GitHub

https://github.com/gpac/gpac/issues/3764
Web page

[security] scenegraph/base_scenegraph.c:704 Use-After-Free in gf_node_try_destroy · Issue #3762 · gpac/gpac · GitHub

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

Vendor Advisories for CVE-2026-132765(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 10× in last 7d / 10× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-11-20 05:48 UTCGHSA enrichmentGHSA-gmg6-rv8r-m9ch · GitHub severity MODERATE · GitHub CVSS 6.6
  4. 2026-11-19 20:30 UTCEchelonGraph re-scored
  5. 2026-11-19 20:30 UTCGHSA enrichmentGHSA-gmg6-rv8r-m9ch · GitHub severity MODERATE · GitHub CVSS 6.6
  6. 2026-11-19 19:42 UTCEchelonGraph re-scored
  7. 2026-11-19 19:42 UTCGHSA enrichmentGHSA-gmg6-rv8r-m9ch · GitHub severity MODERATE · GitHub CVSS 6.6
  8. 2026-11-19 19:24 UTCEchelonGraph re-scored
  9. 2026-11-19 19:24 UTCGHSA enrichmentGHSA-gmg6-rv8r-m9ch · GitHub severity MODERATE · GitHub CVSS 6.6
  10. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-11-19 00:47 UTCEchelonGraph re-scored
  12. 2026-11-19 00:47 UTCGHSA enrichmentGHSA-gmg6-rv8r-m9ch · GitHub severity MODERATE · GitHub CVSS 6.6
  13. 2026-11-19 00:28 UTCEchelonGraph re-scored
  14. 2026-11-19 00:03 UTCENISA EUVD ID recordedEUVD-2026-129351 · Source: ENISA EUVD
  15. 2026-11-18 23:23 UTCEchelonGraph re-scoredFirst assessed: 6.6 MEDIUM
  16. 2026-11-18 23:22 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-132765?
CVE-2026-132765 is a medium-severity vulnerability; its CVE record was published on November 18, 2026. GPAC MP4Box through 26.07.0 contains a use-after-free vulnerability in gf_node_try_destroy because Conditional node commands keep raw pointers to target nodes freed by gf_sg_reset(). Attackers can supply a crafted XMT scene processed with -info or -add to trigger heap use-after-free, crashing the…
When was CVE-2026-132765 made public?
CVE-2026-132765 was made public on July 23, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on November 18, 2026. EchelonGraph's copy of the record carries a last-modified date of November 19, 2026; the record at its source may have been updated since.
Is CVE-2026-132765 actively exploited?
CVE-2026-132765 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-132765?
CVE-2026-132765 has a CVSS base score of 6.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-132765?
An upstream fix for CVE-2026-132765 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-132765 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-132765?

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