CVE-2026-47143: Capstone has a NULL Pointer Dereference with 3DNow! opcodes
Noroxi assessment
Priority: Monitor (action score 23/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.46% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: azl3 rust 1.90.0-10 on Azure Linux 3.0 1.90.0-10; azl3 rust 1.90.0-9 on Azure Linux 3.0 1.90.0-10.
Low priority for now. Upgrade to azl3 rust 1.90.0-10 on Azure Linux 3.0 1.90.0-10; azl3 rust 1.90.0-9 on Azure Linux 3.0 1.90.0-10 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. Versions prior to 6.0.0-Alpha8 and 5.0.8 have a NULL pointer dereference in `modRMRequired()` and `decode()` when disassembling 3DNow! opcodes (`0F 0F`) in builds compiled with `-DCAPSTONE_X86_REDUCE`, allowing a remote attacker to crash any application using the reduced X86 Capstone library by supplying a crafted input containing the 4-byte sequence `0F 0F <modrm> <imm8>`. Versions 6.0.0-Alpha8 and 5.0.8 patch the issue.
- Published
- Jul 21, 2026
- Updated
- Oct 24, 2026
- EPSS
- 0.4% · 40th percentile
- CWE
- CWE-476
Report tools
Action score
23
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.9
- CNA · GitHub_M
- 5.1
- 0.8 point gap
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
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
- < 5.0.8, < 6.0.0-Alpha8affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- capstone-engine capstonebefore 5.0.8
- 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 |
|---|---|---|---|
| Alpine:v3.23 | capstone | before 5.0.8-r0 | 5.0.8-r0 |
| Debian:12 | capstone | from 0 | — |
| Debian:14 | capstone | before 5.0.9-1 | 5.0.9-1 |
| PyPI | capstone | before 5.0.8 | 5.0.8 |
| Red Hat:hummingbird:1 | capstone | before 0:5.0.8-0.1.hum1 | 0:5.0.8-0.1.hum1 |
| Red Hat:hummingbird:1 | capstone-devel | before 0:5.0.8-0.1.hum1 | 0:5.0.8-0.1.hum1 |
| Red Hat:hummingbird:1 | capstone-java | before 0:5.0.8-0.1.hum1 | 0:5.0.8-0.1.hum1 |
| Red Hat:hummingbird:1 | capstone-static | before 0:5.0.8-0.1.hum1 | 0:5.0.8-0.1.hum1 |
| Red Hat:hummingbird:1 | python3-capstone | before 0:5.0.8-0.1.hum1 | 0:5.0.8-0.1.hum1 |
Same product
capstone-engine: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-68114Capstone doesn't check vsnprintf return in SStream_concat, allows stack buffer underflow and overflow39Monitor
- 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
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-49263Aug 14, 2026 · Capstone WASM `br_table` instruction-size truncation can cause no-progress disassembly and parser desynchronization8Monitor
- Later →CVE-2026-49282Aug 14, 2026 · Capstone M68K and RISCV `cs_insn_name()` invalid IDs can trigger out-of-bounds reads and process crashes20Monitor
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-10 on Azure Linux 3.0 | 1.90.0-10 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 rust 1.90.0-9 on Azure Linux 3.0 | 1.90.0-10 · CBL-Mariner Releases | Microsoft (MSRC) |
| alpine:capstone | 5.0.8-r0 · Alpine:v3.23 | Package registry (OSV) |
| debian:capstone | 5.0.9-1 · Debian:14 | Package registry (OSV) |
| PyPI:capstone | 5.0.8 | Package registry (OSV) |
| red hat:capstone | 0:5.0.8-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:capstone-devel | 0:5.0.8-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:capstone-java | 0:5.0.8-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:capstone-static | 0:5.0.8-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:python3-capstone | 0:5.0.8-0.1.hum1 · Red Hat:hummingbird:1 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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: 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.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.