CVE-2026-129479

MEDIUMPre-NVD 5.55.5
EchelonGraph scoreHIGH confidence

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

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

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

Also known asEUVD-2026-126028 (ENISA EUVD) · GHSA-f8x5-qxqq-cgrr (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Assimp through 6.0.6 contains an integer overflow vulnerability in OgreBinarySerializer::ReadSubMesh that allows attackers to crash applications by supplying crafted Ogre binary .mesh files. Attackers can set a large index count so the 32-bit buffer size wraps, causing a segmentation fault in aiMesh::~aiMesh() during scene teardown.

CVSS v3
5.5
EG Score
5.5MEDIUMhigh confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
5th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (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.

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 15, 2026

Last Modified

November 16, 2026

Advisory Details (4)

Auto-updated Nov 15, 2026
Patch available. Sources: github_pr.
Web page

Assimp through 6.0.6 Integer Overflow via OgreBinarySerializer::ReadSubMesh | Advisories | VulnCheck

https://www.vulncheck.com/advisories/assimp-through-6.0.6-integer-overflow-via-ogrebinaryserializer-readsubmesh
Web page

assimp/code/AssetLib/Ogre/OgreBinarySerializer.cpp at v6.0.6 · assimp/assimp · GitHub

https://github.com/assimp/assimp/blob/v6.0.6/code/AssetLib/Ogre/OgreBinarySerializer.cpp#L362-L374
GitHub pull request

Ogre: fix 32-bit overflow in the index buffer size computation

Upstream fix in progress (PR #7026 · assimp/assimp, state=open)

https://github.com/assimp/assimp/pull/7026
Web page

SIGSEGV in OgreBinarySerializer::ReadSubMesh via 32-bit wraparound in the index-buffer size · Issue #6930 · assimp/assimp · GitHub

https://github.com/assimp/assimp/issues/6930

Vendor Advisories for CVE-2026-129479(2)

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 / 12× 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% · 5th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-11-20 05:43 UTCEchelonGraph re-scored
  4. 2026-11-20 05:43 UTCVendor advisory
  5. 2026-11-20 05:43 UTCGHSA enrichmentGHSA-f8x5-qxqq-cgrr · GitHub severity MODERATE · GitHub CVSS 5.5
  6. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-11-18 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-11-17 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  9. 2026-11-16 19:38 UTCEchelonGraph re-scored
  10. 2026-11-16 19:37 UTCGHSA enrichmentGHSA-f8x5-qxqq-cgrr · GitHub severity MODERATE · GitHub CVSS 5.5
  11. 2026-11-16 16:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  12. 2026-11-15 15:47 UTCEchelonGraph re-scored
  13. 2026-11-15 15:47 UTCGHSA enrichmentGHSA-f8x5-qxqq-cgrr · GitHub severity MODERATE · GitHub CVSS 5.5
  14. 2026-11-15 14:29 UTCEchelonGraph re-scored
  15. 2026-11-15 14:02 UTCENISA EUVD ID recordedEUVD-2026-126028 · Source: ENISA EUVD
  16. 2026-11-15 13:22 UTCEchelonGraph re-scoredFirst assessed: 5.5 MEDIUM
  17. 2026-11-15 13:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-129479?
CVE-2026-129479 is a medium-severity vulnerability; its CVE record was published on November 15, 2026. Assimp through 6.0.6 contains an integer overflow vulnerability in OgreBinarySerializer::ReadSubMesh that allows attackers to crash applications by supplying crafted Ogre binary .mesh files. Attackers can set a large index count so the 32-bit buffer size wraps, causing a segmentation fault in…
When was CVE-2026-129479 made public?
CVE-2026-129479 was made public on October 13, 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 15, 2026. EchelonGraph's copy of the record carries a last-modified date of November 16, 2026; the record at its source may have been updated since.
Is CVE-2026-129479 actively exploited?
CVE-2026-129479 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-129479?
CVE-2026-129479 has a CVSS base score of 5.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-129479?
A fix for CVE-2026-129479 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-129479 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-129479?

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