CVE-2025-68114

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.2% (9th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2025-203995 (ENISA EUVD)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate 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.2%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Capstone is a disassembly framework. In versions 6.0.0-Alpha5 and prior, an unchecked vsnprintf return in SStream_concat lets a malicious cs_opt_mem.vsnprintf drive SStream’s index negative or past the end, leading to a stack buffer underflow/overflow when the next write occurs. Commit 2c7797182a1618be12017d7d41e0b6581d5d529e fixes the issue.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
9th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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, 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).

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

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.

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

December 17, 2025

Last Modified

October 13, 2026

Advisory Details (2)

Auto-updated Oct 28, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Unchecked vsnprintf return in SStream_concat allows stack buffer underflow&overflow · Advisory · capstone-engine/capstone · GitHub

https://github.com/capstone-engine/capstone/security/advisories/GHSA-85f5-6xr3-q76r
GitHub commit

commit 2c7797182a16 (capstone-engine/capstone)

Fix landed in capstone-engine/capstone commit 2c7797182a16 — awaiting tagged release

https://github.com/capstone-engine/capstone/commit/2c7797182a1618be12017d7d41e0b6581d5d529e

Vendor Advisories for CVE-2025-68114(10)

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

Patch Availability(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatcapstone-0:4.0.2-13.el9_82026-07-14redhat
redhatcapstone-0:4.0.2-5.el9_02026-05-06redhat
redhatcapstone-main-5.0.7-0.1.hum12026-05-01redhat
redhatcapstone-0:5.0.1-7.el10_12026-04-07redhat
redhatcapstone-0:5.0.1-7.el10_02026-03-23redhat
redhatcapstone-0:4.0.2-11.el9_62026-03-19redhat
redhatcapstone-0:4.0.2-11.el9_42026-03-19redhat
redhatcapstone-0:4.0.2-11.el9_22026-03-19redhat
redhatcapstone-0:4.0.2-11.el9_72026-03-18redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
capstone4.0.2-3 ... 5.0.9-1 (13 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
capstone4.0.2-5 ... 5.0.9-1 (11 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
capstone5.0.6-1
  • every version up to 5.0.7-1~deb13u1: fixed in 5.0.7-1~deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
capstone5.0.6-1, 5.0.7-1~deb13u1
  • every version up to 5.0.7-1: fixed in 5.0.7-1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 73× 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 99 of 235 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 136 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Same vendor

1 shown

redhat:RHSA-2026:12781

Frequently asked(5)

What is CVE-2025-68114?
CVE-2025-68114 is a critical-severity vulnerability; its CVE record was published on December 17, 2025. Capstone is a disassembly framework. In versions 6.0.0-Alpha5 and prior, an unchecked vsnprintf return in SStream_concat lets a malicious cs_opt_mem.vsnprintf drive SStream’s index negative or past the end, leading to a stack buffer underflow/overflow when the next write occurs. Commit…
When was the CVE record for CVE-2025-68114 published?
The CVE record for CVE-2025-68114 was published on December 17, 2025. 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 13, 2026; the record at its source may have been updated since.
Is CVE-2025-68114 actively exploited?
CVE-2025-68114 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-68114?
CVE-2025-68114 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2025-68114?
A fix for CVE-2025-68114 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-68114 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-2025-68114

Explore →

Is Your Infrastructure Affected by CVE-2025-68114?

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

Book a Demo →Browse All CVEs