CVE-2026-14610

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

Score 5.3 from GitHub Security Advisory (severity: LOW) published 2026-07-03. A secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-41601 (ENISA EUVD) · GHSA-rc6p-2pj8-p4v9 (GitHub Security Advisories)Source: ENISA EUVD

5.3EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (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.1%CVSS: 5.3Exploit: 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.

A flaw has been found in Open Asset Import Library Assimp up to 6.0.5. Impacted is the function Assimp::CSMImporter::InternReadFile of the file code/AssetLib/CSM/CSMLoader.cpp of the component CSM File Handler. This manipulation causes heap-based buffer overflow. The attack is restricted to local execution. The exploit has been published and may be used. Patch name: eb84eec580d3f4ba2f0fd87409b7d0744620f11e. Applying a patch is the recommended action to fix this issue.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
40
EG Risk 40/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)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 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. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.1%
EPSS %ILE
2nd
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.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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.Each input and its source: 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. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

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.

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

July 3, 2026

Last Modified

October 25, 2026

Advisory Details (3)

Auto-updated Jul 8, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr, github_commit.
GitHub pull request

fix: prevent heap buffer overflow in CSM loader on non-positive frame range

Fix merged in assimp/assimp PR #6649 on 2026-06-04 — awaiting tagged release

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

Bug: Heap-buffer-overflow in CSMImporter::InternReadFile due to insufficiently allocated buffer for position keys · Issue #6622 · assimp/assimp · GitHub

https://github.com/assimp/assimp/issues/6622
GitHub commit

commit eb84eec580d3 (assimp/assimp)

Fix landed in assimp/assimp commit eb84eec580d3 — awaiting tagged release

https://github.com/assimp/assimp/commit/eb84eec580d3f4ba2f0fd87409b7d0744620f11e

Vendor Advisories for CVE-2026-14610(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
assimp5.0.1~ds0-2 ... 6.0.5+ds-1 (34 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
assimp5.2.5~ds0-1 ... 6.0.5+ds-1 (14 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
assimp5.4.3+ds-2 ... 6.0.5+ds-1 (7 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
assimp5.4.3+ds-2 ... 6.0.5+ds-1 (7 versions)
  • every version on: no fix on record
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 38× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 100 of 207 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 107 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  4. 2026-10-25 15:30 UTCGHSA enrichmentGHSA-rc6p-2pj8-p4v9 · GitHub severity LOW · GitHub CVSS 5.3
  5. 2026-10-25 15:25 UTCNVD updateCVSS v4 → 1.9
  6. 2026-10-25 14:48 UTCEG score recompute
  7. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-10-23 06:29 UTCEG score recompute
  10. 2026-10-23 06:29 UTCGHSA enrichmentGHSA-rc6p-2pj8-p4v9 · GitHub severity LOW · GitHub CVSS 5.3
  11. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-10-18 05:02 UTCEG score recompute
  16. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-10-13 14:24 UTCOSV refresh
  22. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-10-12 16:33 UTCEG score recompute
  24. 2026-10-11 20:10 UTCEG score recompute
  25. 2026-10-11 18:22 UTCEG score recompute
Show 75 more
  1. 2026-10-11 14:56 UTCEG score recompute
  2. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  4. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  5. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  7. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  13. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  15. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  16. 2026-09-23 06:34 UTCEG score recompute
  17. 2026-09-23 06:34 UTCGHSA enrichmentGHSA-rc6p-2pj8-p4v9 · GitHub severity LOW · GitHub CVSS 5.3
  18. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  19. 2026-09-18 06:11 UTCEG score recompute
  20. 2026-09-18 06:11 UTCGHSA enrichmentGHSA-rc6p-2pj8-p4v9 · GitHub severity LOW · GitHub CVSS 5.3
  21. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  22. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  24. 2026-09-13 11:56 UTCEG score recompute
  25. 2026-09-13 11:56 UTCGHSA enrichmentGHSA-rc6p-2pj8-p4v9 · GitHub severity LOW · GitHub CVSS 5.3
  26. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  27. 2026-09-12 13:57 UTCEG score recompute
  28. 2026-09-12 13:57 UTCGHSA enrichmentGHSA-rc6p-2pj8-p4v9 · GitHub severity LOW · GitHub CVSS 5.3
  29. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  30. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  31. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  32. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  33. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  34. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  35. 2026-09-05 23:40 UTCEG score recompute
  36. 2026-09-05 23:40 UTCGHSA enrichmentGHSA-rc6p-2pj8-p4v9 · GitHub severity LOW · GitHub CVSS 5.3
  37. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  38. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  39. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  40. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  41. 2026-08-30 11:18 UTCEG score recompute
  42. 2026-08-30 11:18 UTCGHSA enrichmentGHSA-rc6p-2pj8-p4v9 · GitHub severity LOW · GitHub CVSS 5.3
  43. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  44. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  45. 2026-08-27 22:11 UTCEG score recompute
  46. 2026-08-27 22:11 UTCGHSA enrichmentGHSA-rc6p-2pj8-p4v9 · GitHub severity LOW · GitHub CVSS 5.3
  47. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  48. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  49. 2026-08-26 14:30 UTCEG score recompute
  50. 2026-08-26 14:30 UTCGHSA enrichmentGHSA-rc6p-2pj8-p4v9 · GitHub severity LOW · GitHub CVSS 5.3
  51. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  52. 2026-08-24 23:27 UTCEG score recompute
  53. 2026-08-24 23:27 UTCGHSA enrichmentGHSA-rc6p-2pj8-p4v9 · GitHub severity LOW · GitHub CVSS 5.3
  54. 2026-08-24 01:36 UTCGHSA enrichmentGHSA-rc6p-2pj8-p4v9 · GitHub severity LOW · GitHub CVSS 5.3
  55. 2026-08-23 03:45 UTCEG score recompute
  56. 2026-08-23 03:45 UTCGHSA enrichmentGHSA-rc6p-2pj8-p4v9 · GitHub severity LOW · GitHub CVSS 5.3
  57. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  58. 2026-08-22 05:54 UTCEG score recompute
  59. 2026-08-22 05:54 UTCGHSA enrichmentGHSA-rc6p-2pj8-p4v9 · GitHub severity LOW · GitHub CVSS 5.3
  60. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  61. 2026-08-21 05:32 UTCEG score recompute
  62. 2026-08-21 05:32 UTCGHSA enrichmentGHSA-rc6p-2pj8-p4v9 · GitHub severity LOW · GitHub CVSS 5.3
  63. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  64. 2026-08-20 07:41 UTCEG score recompute
  65. 2026-08-20 07:41 UTCGHSA enrichmentGHSA-rc6p-2pj8-p4v9 · GitHub severity LOW · GitHub CVSS 5.3
  66. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  67. 2026-08-19 09:51 UTCEG score recompute
  68. 2026-08-19 09:51 UTCGHSA enrichmentGHSA-rc6p-2pj8-p4v9 · GitHub severity LOW · GitHub CVSS 5.3
  69. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  70. 2026-08-18 11:43 UTCEG score recompute
  71. 2026-08-18 11:43 UTCGHSA enrichmentGHSA-rc6p-2pj8-p4v9 · GitHub severity LOW · GitHub CVSS 5.3
  72. 2026-08-17 12:17 UTCEG score recompute
  73. 2026-08-17 12:17 UTCGHSA enrichmentGHSA-rc6p-2pj8-p4v9 · GitHub severity LOW · GitHub CVSS 5.3
  74. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  75. 2026-08-16 14:11 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-14610?
CVE-2026-14610 is a medium-severity vulnerability; its CVE record was published on July 3, 2026. A flaw has been found in Open Asset Import Library Assimp up to 6.0.5. Impacted is the function Assimp::CSMImporter::InternReadFile of the file code/AssetLib/CSM/CSMLoader.cpp of the component CSM File Handler. This manipulation causes heap-based buffer overflow. The attack is restricted to local…
When was the CVE record for CVE-2026-14610 published?
The CVE record for CVE-2026-14610 was published on July 3, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 25, 2026; the record at its source may have been updated since.
Is CVE-2026-14610 actively exploited?
CVE-2026-14610 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-14610?
CVE-2026-14610 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-14610?
An upstream fix for CVE-2026-14610 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-14610 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-14610

Explore →

Is Your Infrastructure Affected by CVE-2026-14610?

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