CVE-2025-68114: Capstone doesn't check vsnprintf return in SStream_concat, allows stack buffer underflow and overflow
Noroxi assessment
Priority: Monitor (action score 39/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: azl3 rust 1.90.0-3 on Azure Linux 3.0 1.90.0-4; azl3 rust 1.90.0-4 on Azure Linux 3.0 1.90.0-4.
- Severity is disputed: the assigning authority (CNA) scores it 4.8, NVD 9.8.
Low priority for now. Upgrade to azl3 rust 1.90.0-3 on Azure Linux 3.0 1.90.0-4; azl3 rust 1.90.0-4 on Azure Linux 3.0 1.90.0-4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- BDU:2026-04943
- ALSA-2026:39309
- ALSA-2026:4898
- ALSA-2026:6817
- RHSA-2026:12781
- RHSA-2026:13923
- RHSA-2026:39309
- RHSA-2026:4898
- RHSA-2026:5123
- RHSA-2026:5124
- RHSA-2026:5125
- RHSA-2026:5224
- RHSA-2026:6817
- RLSA-2026:39309
- RLSA-2026:4898
- RLSA-2026:6817
- SUSE-SU-2026:0060-1
- SUSE-SU-2026:20054-1
- SUSE-SU-2026:20868-1
- Published
- Dec 17, 2025
- Updated
- Oct 13, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-120
Report tools
Action score
39
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 9.8
- CNA · GitHub_M
- 4.8
- 5.0 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| capstone-engine | capstone | cpe:2.3:a:capstone-engine:capstone |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
capstone-engine capstone
- <= 6.0.0-Alpha5affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- capstone-engine capstonebefore 6.0.0
- capstone-engine capstone6.0.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | capstone-java | before 5.0.1-7.el10_1 | 5.0.1-7.el10_1 |
| AlmaLinux:10 | python3-capstone | before 5.0.1-7.el10_1 | 5.0.1-7.el10_1 |
| AlmaLinux:9 | capstone | before 4.0.2-11.el9_7 | 4.0.2-11.el9_7 |
| AlmaLinux:9 | capstone | before 4.0.2-13.el9_8 | 4.0.2-13.el9_8 |
| AlmaLinux:9 | capstone-devel | before 4.0.2-11.el9_7 | 4.0.2-11.el9_7 |
| AlmaLinux:9 | capstone-devel | before 4.0.2-13.el9_8 | 4.0.2-13.el9_8 |
| AlmaLinux:9 | capstone-java | before 4.0.2-11.el9_7 | 4.0.2-11.el9_7 |
| AlmaLinux:9 | capstone-java | before 4.0.2-13.el9_8 | 4.0.2-13.el9_8 |
| AlmaLinux:9 | python3-capstone | before 4.0.2-11.el9_7 | 4.0.2-11.el9_7 |
| AlmaLinux:9 | python3-capstone | before 4.0.2-13.el9_8 | 4.0.2-13.el9_8 |
| Alpine:v3.23 | capstone | before 5.0.7-r0 | 5.0.7-r0 |
| Debian:12 | capstone | from 0 | — |
| Debian:13 | capstone | before 5.0.7-1~deb13u1 | 5.0.7-1~deb13u1 |
| Debian:14 | capstone | before 5.0.7-1 | 5.0.7-1 |
| openSUSE:Leap 15.6 | capstone | before 4.0.2-150500.3.3.1 | 4.0.2-150500.3.3.1 |
| Red Hat:enterprise_linux_eus:10.0 | capstone | before 0:5.0.1-7.el10_0 | 0:5.0.1-7.el10_0 |
| Red Hat:enterprise_linux_eus:10.0 | capstone-debuginfo | before 0:5.0.1-7.el10_0 | 0:5.0.1-7.el10_0 |
| Red Hat:enterprise_linux_eus:10.0 | capstone-debugsource | before 0:5.0.1-7.el10_0 | 0:5.0.1-7.el10_0 |
| Red Hat:enterprise_linux_eus:10.0 | capstone-devel | before 0:5.0.1-7.el10_0 | 0:5.0.1-7.el10_0 |
| Red Hat:enterprise_linux_eus:10.0 | capstone-java | before 0:5.0.1-7.el10_0 | 0:5.0.1-7.el10_0 |
| Red Hat:enterprise_linux_eus:10.0 | python3-capstone | before 0:5.0.1-7.el10_0 | 0:5.0.1-7.el10_0 |
| Red Hat:enterprise_linux:10.1 | capstone | before 0:5.0.1-7.el10_1 | 0:5.0.1-7.el10_1 |
| Red Hat:enterprise_linux:10.1 | capstone-debuginfo | before 0:5.0.1-7.el10_1 | 0:5.0.1-7.el10_1 |
| Red Hat:enterprise_linux:10.1 | capstone-debugsource | before 0:5.0.1-7.el10_1 | 0:5.0.1-7.el10_1 |
+50
Same product
capstone-engine: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-6952Integer overflow in the cs_winkernel_malloc function in winkernel_mm.c in Capstone 3.0.4 and earlier allows attackers to cause a denial of…35Monitor
- CVE-2025-67873Capstone doesn't check Skipdata length, leading to cs_insn.bytes heap buffer overflow31Monitor
- CVE-2026-55893Capstone SH disassembler `set_reg_n` heap buffer overflow via crafted SH2A FPU bytecode29Monitor
Published before and after this one in the same product
- ← EarlierCVE-2016-7151May 15, 2019 · Capstone 3.0.4 has an out-of-bounds vulnerability (SEGV caused by a read memory access) in X86_insn_reg_intel in arch/X86/X86Mapping.c.22Monitor
- Later →CVE-2026-47143Jul 21, 2026 · Capstone has a NULL Pointer Dereference with 3DNow! opcodes23Monitor
- Later →CVE-2026-49263Aug 14, 2026 · Capstone WASM `br_table` instruction-size truncation can cause no-progress disassembly and parser desynchronization8Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| azl3 rust 1.90.0-3 on Azure Linux 3.0 | 1.90.0-4 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 rust 1.90.0-4 on Azure Linux 3.0 | 1.90.0-4 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:capstone | 4.0.2-13.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:capstone-devel | 4.0.2-13.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:capstone-java | 4.0.2-13.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:python3-capstone | 4.0.2-13.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| alpine:capstone | 5.0.7-r0 · Alpine:v3.23 | Package registry (OSV) |
| debian:capstone | 5.0.7-1~deb13u1 · Debian:13 | Package registry (OSV) |
| opensuse:capstone | 4.0.2-150500.3.3.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| red hat:capstone | 0:5.0.7-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:capstone-debuginfo | 0:4.0.2-5.el9_0 · Red Hat:rhel_e4s:9.0::appstream | Package registry (OSV) |
| red hat:capstone-debugsource | 0:4.0.2-5.el9_0 · Red Hat:rhel_e4s:9.0::appstream | Package registry (OSV) |
| red hat:capstone-devel | 0:4.0.2-13.el9_8 · Red Hat:enterprise_linux:9::crb | Package registry (OSV) |
| red hat:capstone-devel | 0:5.0.7-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:capstone-java | 0:5.0.7-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:capstone-static | 0:5.0.7-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:python3-capstone | 0:4.0.2-13.el9_8 · Red Hat:enterprise_linux:9::crb | Package registry (OSV) |
| red hat:python3-capstone | 0:5.0.7-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:python3-capstone-debuginfo | 0:4.0.2-5.el9_0 · Red Hat:rhel_e4s:9.0::appstream | Package registry (OSV) |
| rocky linux:capstone | 0:4.0.2-13.el9_8 · Rocky Linux:9 | Package registry (OSV) |
| suse:capstone | 4.0.2-150500.3.3.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.
The bug in code
The whole CWE-120 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
char buf[256];
memcpy(buf, pkt->data, pkt->len);Fixed
char buf[256];
if (pkt->len > sizeof(buf)) {
return -EINVAL;
}
memcpy(buf, pkt->data, pkt->len);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
- Overflow Variables and TagsCAPEC-46likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.