LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32777: libexpat before 2.7.5 allows an infinite loop while parsing DTD content.

libexpat before 2.7.5 allows an infinite loop while parsing DTD content.

MediumCVSS 4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-32777 is a denial-of-service issue in libexpat before 2.7.5. When parsing certain DTD content, the parser can enter an infinite loop. Business impact is likely service slowdown or interruption where vulnerable libexpat processes untrusted XML, not data theft or system takeover based on current sources.

Executive priority

Treat as a targeted availability risk. Prioritize systems where XML parsing supports critical services, industrial operations, or externally supplied data. It is not currently supported as an emergency exploitation event.

Technical view

The CVE describes CWE-835: an infinite loop while parsing DTD content in libexpat before 2.7.5. CVSS 3.1 is 4.0 with local attack vector, no privileges, no user interaction, and low availability impact only. The record does not indicate confidentiality or integrity impact.

Likely exposure

Exposure is most relevant for applications, appliances, or embedded products that include libexpat before 2.7.5 and parse DTD-bearing XML. Downstream vendor impact may vary; Siemens has a related advisory.

Exploitation context

The source bundle does not show CISA KEV listing or cited active exploitation. A vulnerable program must parse triggering DTD content. Current public scoring indicates availability impact rather than code execution or data compromise.

Researcher notes

The affected-version statement comes from the CVE description: libexpat before 2.7.5. The bundled affected array appears sparse, so validate against upstream pull requests, issue 1161, OSS-Fuzz, and downstream vendor advisories before final asset scoping.

Mitigation direction

  • Inventory systems and products that include libexpat.
  • Upgrade libexpat to 2.7.5 or later where applicable.
  • Check Siemens and other vendor advisories for product-specific updates.
  • Prioritize internet-facing or automation-critical XML processing services.
  • If no update is available, follow vendor guidance for compensating controls.

Validation and detection

  • Confirm libexpat versions in applications, containers, appliances, and firmware.
  • Identify services that parse XML with DTD content.
  • Review vendor SBOMs and advisories for bundled libexpat.
  • Verify patched builds use libexpat 2.7.5 or later.
  • Monitor affected services for hangs or abnormal resource usage.
Prepared
Confidence
medium
Sources
7

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-835: 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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-32777 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ScoreVersionSeverityVectorExploitImpactSource
4CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L2.51.4mitre

Vulnerability scoring details

Base CVSS 3.1 score

4Medium
CVSS 3.1 vector shape for CVE-2026-32777Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
libexpat projectlibexpat0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-835 · source CWE mapping

Loop with Unreachable Exit Condition ('Infinite Loop')

Loop with Unreachable Exit Condition ('Infinite Loop') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.