ApplicationsHigh 8.2Patch available
CVE-2026-102633
Integer overflow in libexpat enabling heap overflow leading to RCE/DoS on 32-bit systems.
How scary is it?
updated 10 Nov 2026- Yes
Works without logging in1
No account and no user action needed (CVSS PR:N, UI:N).
- Yes
Reachable over the network1
Can be attacked remotely (CVSS AV:N).
- None known
Public exploit code is out
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
- None known
Attacks seen in the wild1
None reported that we know of. CISA's SSVC assessment says exploitation: none.
- No
On CISA's exploited list2
Not in the catalog as of our last sync.
Scare-o-meter
Routine patch
Serious on paper, with no sign of attacks that we know of. Patch in your normal cycle.
- Low signal
- Routine patch
- Act this week
- Drop everything
Why: our alert rule found no exploitation evidence and no easy remote attack path in the data we hold. Read from the same rule that decides our alert emails.
Are you affected? only if all are true
You run libexpat in an affected version>= 2.7.2 and <= 2.8.5
The CVE record states no fixed release.
As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.
See the affected products table · Source 1
An attacker can reach it over the network
CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.
Source 1
Specific conditions are met that the attacker does not control
CVSS attack complexity: High (AC:H). Needs specific conditions, a race or a particular configuration. The CVE record does not always say which.
Source 1
Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.
What to do
Per our analysisA patch is available
The CVE record we hold states no fixed release number. See the advisories in the references.
Recommendation, AI-writtenUpgrade to patched libexpat release/commit, rebuild dependent binaries, block untrusted XML inputs on 32-bit hosts.
Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.
Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.
Major vulnerability. libexpat is a widely used XML library; this overflow can enable remote code execution or widespread DoS in many applications and infrastructures.
- CVSS
- 8.2Highscored by the publisher (CNA)
- Exploited in the wild
- Not knownnot in CISA KEV as of our last sync
- EPSS
- 0.40%chance of exploitation in the next 30 daystop 66% of scored CVEsFIRST score of 21 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 29 Sept 2026analysed here 2 Oct 2026
Summary
Impact
Heap buffer overflow via crafted XML on 32-bit when parsing with libexpat 2.7.2–2.8.5; may cause memory corruption, DoS, or remote code execution.
Triage
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| libexpat | >= 2.7.2 and <= 2.8.5Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- libexpat 2.7.2 through 2.8.5 (32-bit builds)
- Any application or service statically/dynamically linking vulnerable libexpat (XML parsers, toolchains, servers)
Fix and mitigation
Action required
Immediate action required
WAF and other mitigations
Can a WAF block it? No. This is an integer overflow, usually triggered by an ordinary-looking number or size. Generic WAF rules do not recognise it; only a rule written for this specific CVE can.
Also consider: patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
- CISA SSVC
- exploitation none, automatable no, technical impact partialAssessed by CISA 29 Sept 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
Timeline
- 29 Sept 2026Published
- 29 Sept 2026CISA SSVC assessment: exploitation nonesame day later
- 2 Oct 2026Analysed by vulneraibility.com3 days later
- 10 Nov 2026CVE record last updated39 days later
Common questions
Is CVE-2026-102633 being exploited?
Not confirmed. CVE-2026-102633 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.40% probability of exploitation in the next 30 days.
How severe is CVE-2026-102633?
CVE-2026-102633 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-102633?
Yes. A fix has been recorded for CVE-2026-102633. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-102633 affect?
CVE-2026-102633 affects libexpat 2.7.2 through 2.8.5 (32-bit builds), Any application or service statically/dynamically linking vulnerable libexpat (XML parsers, toolchains, servers). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-102633?
Upgrade to patched libexpat release/commit, rebuild dependent binaries, block untrusted XML inputs on 32-bit hosts.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
6 references in the CVE record, grouped by the tags the record gives them.
Advisories (1)
- vulncheck.com /advisories/libexpat-2.7.2-through-2.8.5-integer-overflow-in-expat-realloc
Patches (2)
- github.com /libexpat/libexpat/pull/1392
- github.com /libexpat/libexpat/commit/209801d7fbaf07ab74bae8cb32dd2ab9e5846118
Other links (3)
- github.com /libexpat/libexpat/blob/R_2_8_5/expat/lib/xmlparse.c#L1003
- github.com /libexpat/libexpat
- cert-portal.siemens.com /productcert/html/ssa-457936.html
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.