CVE-2026-76956: In libexpat 2.8.2 and 2.8.3 before 2.8.4, misinterpretation of getentropy's return code leads to insufficient entropy, which results in bein
Noroxi assessment
Priority: Monitor (action score 30/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.28% (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.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: libexpat project libexpat 2.8.4.
Low priority for now. Upgrade to libexpat project libexpat 2.8.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
In libexpat 2.8.2 and 2.8.3 before 2.8.4, misinterpretation of getentropy's return code leads to insufficient entropy, which results in being vulnerable to hash flooding attacks, causing a denial of service via crafted XML content.
- Published
- Aug 20, 2026
- Updated
- Sep 8, 2026
- EPSS
- 0.2% · 21th percentile
- CWE
- CWE-394
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.5
- CNA · mitre
- 5.9
- 1.6 point gap
CVSS:3.1/AV:N/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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 |
|---|---|---|
| libexpat project | libexpat | cpe:2.3:a:libexpat_project:libexpat |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- libexpat project libexpat2.8.2 and later · before 2.8.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (mitre). Independent of NVD's CPE analysis and usually ahead of it.
libexpat project libexpat
- 2.8.2 and later · before 2.8.4affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.21 | expat | before 2.8.4-r0 | 2.8.4-r0 |
| Debian:13 | expat | before 2.9.0-1~deb13u1 | 2.9.0-1~deb13u1 |
| Debian:14 | expat | before 2.8.4-1 | 2.8.4-1 |
| openSUSE:Leap 16.0 | expat | before 2.8.4-160000.1.1 | 2.8.4-160000.1.1 |
| openSUSE:Tumbleweed | expat | before 2.8.4-1.1 | 2.8.4-1.1 |
| Red Hat:hummingbird:1 | expat | before 0:2.8.4-0.1.hum1 | 0:2.8.4-0.1.hum1 |
| Red Hat:hummingbird:1 | expat | before 0:2.8.3-0.1.1.hum1 | 0:2.8.3-0.1.1.hum1 |
| Red Hat:hummingbird:1 | expat-devel | before 0:2.8.4-0.1.hum1 | 0:2.8.4-0.1.hum1 |
| Red Hat:hummingbird:1 | expat-devel | before 0:2.8.3-0.1.1.hum1 | 0:2.8.3-0.1.1.hum1 |
| Red Hat:hummingbird:1 | expat-static | before 0:2.8.4-0.1.hum1 | 0:2.8.4-0.1.hum1 |
| Red Hat:hummingbird:1 | expat-static | before 0:2.8.3-0.1.1.hum1 | 0:2.8.3-0.1.1.hum1 |
| SUSE:Linux Micro 6.2 | expat | before 2.8.4-160000.1.1 | 2.8.4-160000.1.1 |
Same product
libexpat project: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-25236xmlparse.c in Expat (aka libexpat) before 2.4.5 allows attackers to insert namespace-separator characters into namespace URIs.50Plan
- CVE-2022-23852Expat (aka libexpat) before 2.4.4 has a signed integer overflow in XML_GetBuffer, for configurations with a nonzero XML_CONTEXT_BYTES.41Plan
- CVE-2022-22822addBinding in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.41Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72522Aug 10, 2026 · libexpat before 2.8.3 has an out-of-bounds read and resultant infinite loop because low surrogates are treated the same as high surrogates d24Monitor
- ← EarlierCVE-2026-66046Aug 18, 2026 · Expat Denial of Service via storeAtts() Quadratic Complexity34Monitor
- Later →CVE-2026-76957Aug 20, 2026 · libexpat before 2.8.4 lacks handler call depth tracking with custom encoding callbacks.31Monitor
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 |
|---|---|---|
| libexpat project libexpat | 2.8.4 | Vendor (CNA) |
| alpine:expat | 2.8.4-r0 · Alpine:v3.21 | Package registry (OSV) |
| debian:expat | 2.8.4-1 · Debian:14 | Package registry (OSV) |
| debian:expat | 2.9.0-1~deb13u1 · Debian:13 | Package registry (OSV) |
| opensuse:expat | 2.8.4-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:expat | 0:2.8.3-0.1.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:expat-devel | 0:2.8.3-0.1.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:expat-devel | 0:2.8.4-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:expat-static | 0:2.8.3-0.1.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:expat-static | 0:2.8.4-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| suse:expat | 2.8.4-160000.1.1 · SUSE:Linux Micro 6.2 | 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.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-394 · Unexpected Status Code or Return ValueCVSS vector
CVSS:3.1/AV:N/AC:L/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
- 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.