LiveActive security incident?Get immediate response
CVE Record

CVE-2021-42260: TinyXML through 2.6.2 has an infinite loop in TiXmlParsingData::Stamp in tinyxmlparser.cpp via the TIXML_UT...

TinyXML through 2.6.2 has an infinite loop in TiXmlParsingData::Stamp in tinyxmlparser.cpp via the TIXML_UTF_LEAD_0 case. It can be triggered by a crafted XML message and leads to a denial of service.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

TinyXML can get stuck in an infinite loop when handling a specially crafted XML message. For affected software, the practical risk is service disruption, not data theft. Priority depends on whether business-critical systems parse XML from users, partners, APIs, or other untrusted sources.

Executive priority

Prioritize systems where XML parsing is internet-facing, partner-facing, or needed for core operations. This is mainly an availability risk, so remediation urgency should track business impact of service downtime.

Technical view

TinyXML through 2.6.2 has a denial-of-service flaw in TiXmlParsingData::Stamp in tinyxmlparser.cpp, specifically associated with the TIXML_UTF_LEAD_0 case. A crafted XML message can trigger an infinite loop during parsing. Public sources cite Debian and Fedora security updates, but the bundle does not provide CVSS details.

Likely exposure

Exposure is most likely in applications, appliances, or distro packages using TinyXML through 2.6.2 to parse untrusted XML. Embedded or vendored copies matter because they may not appear as obvious package dependencies.

Exploitation context

The provided sources describe a crafted XML denial-of-service trigger. There is no KEV listing and no cited evidence of active exploitation in the source bundle. Treat exploitation status as unconfirmed unless vendor intelligence says otherwise.

Researcher notes

The public record is narrow: affected component, function, trigger class, and denial-of-service impact are described, but no CVSS, CWE, or broad product list is provided. Avoid extrapolating beyond TinyXML through 2.6.2 and downstream patched packages.

Mitigation direction

  • Apply TinyXML security updates from the relevant OS or software vendor.
  • Check Debian and Fedora advisories if those platforms are in scope.
  • Inventory vendored TinyXML copies, not only package-managed installations.
  • Reduce or gate untrusted XML parsing where feasible.
  • Monitor vendor guidance for fixed versions or backported patches.

Validation and detection

  • Search SBOMs and dependency inventories for TinyXML through 2.6.2.
  • Identify services that accept XML from users, partners, or external APIs.
  • Confirm updated packages match vendor security advisory guidance.
  • Review embedded third-party source trees for bundled TinyXML code.
  • Run non-offensive regression tests for malformed XML handling after remediation.
Prepared
Confidence
medium
Sources
7

Public sources used

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.

cve · low confidence lookup

CVE-2021-42260 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
8Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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