CVE-2026-25210: In libexpat before 2.7.4, the doContent function does not properly determine the buffer size bufSize becaus...
In libexpat before 2.7.4, the doContent function does not properly determine the buffer size bufSize because there is no integer overflow check for tag buffer reallocation.
Security readout for executives and security teams
Plain-English summary
CVE-2026-25210 is an integer overflow issue in libexpat's XML parsing code before 2.7.4. A crafted local input could cause incorrect memory handling with potential confidentiality and integrity impact. The CVSS vector is local and high complexity, so urgency is moderate unless libexpat processes untrusted local files in sensitive workflows.
Executive priority
Schedule remediation through normal vulnerability management, with faster action for systems handling untrusted XML or sensitive data. No active exploitation is cited, but confidentiality and integrity impacts justify tracking and patching affected dependencies.
Technical view
The issue is CWE-190 in libexpat's doContent function. tag buffer reallocation does not properly check integer overflow when determining bufSize. The CVSS 3.1 score is 6.9: local attack vector, high attack complexity, no privileges, no user interaction, unchanged scope, high confidentiality and integrity impact, and low availability impact.
Likely exposure
Exposure is likely where applications, appliances, or embedded products include libexpat before 2.7.4 and parse XML from local or staged inputs. The source bundle names libexpat and references a Siemens advisory, but it does not enumerate affected Siemens products here.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. The CVSS vector is local and high complexity, which limits broad remote exploitation assumptions. Treat this as a dependency risk until vendor advisories confirm exposure in deployed products.
Researcher notes
The public record is sparse in the bundle. The key technical clue is missing integer-overflow checking during tag buffer reallocation in doContent. Avoid assuming affected downstream products beyond referenced advisories unless vendor-specific evidence confirms bundling and vulnerable versions.
Mitigation direction
Upgrade libexpat to 2.7.4 or later where directly managed.
Track vendor advisories for products bundling libexpat.
Prioritize systems parsing untrusted XML in sensitive workflows.
Apply vendor-supplied updates for downstream appliances or software.
If updates are unavailable, restrict untrusted XML processing where feasible.
Validation and detection
Inventory applications and devices that bundle libexpat.
Confirm deployed libexpat versions are 2.7.4 or later.
Review SBOMs and vendor advisories for transitive exposure.
Check whether XML inputs are local-only, staged, or user-controlled.
Document compensating controls when vendor fixes are pending.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-190: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
2ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-190 · source CWE mapping
Integer Overflow or Wraparound
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.