LiveActive security incident?Get immediate response
CVE Record

CVE-2025-6069: HTMLParser quadratic complexity when processing malformed inputs

The html.parser.HTMLParser class had worse-case quadratic complexity when processing certain crafted malformed inputs potentially leading to amplified denial-of-service.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Malformed HTML can make Python’s built-in HTML parser perform disproportionately expensive work, potentially slowing or disrupting a service. The issue affects availability, not data confidentiality or integrity. Risk is greatest where applications parse attacker-influenced HTML.

Executive priority

Schedule remediation through normal vulnerability management, accelerating internet-facing or high-volume services that parse user-controlled HTML. Confirm exposure before treating this as an emergency; current evidence supports availability risk but not active exploitation.

Technical view

CVE-2025-6069 is a CWE-1333 algorithmic-complexity issue in html.parser.HTMLParser. Certain malformed inputs trigger worst-case quadratic processing, enabling amplified denial of service. CVSS 3.1 is 4.3: network-accessible, low complexity, low privileges, no user interaction, and low availability impact.

Likely exposure

Potentially exposed systems use affected CPython versions and pass network-supplied or otherwise untrusted HTML into HTMLParser. The supplied version data does not clearly establish complete affected ranges or exact fixed releases, so deployments require vendor-specific verification.

Exploitation context

The bundle does not establish active exploitation, and the CVE is not listed as KEV. Exploitation requires low privileges according to the CVSS vector. Successful abuse may consume excessive processing time, but no confidentiality or integrity impact is identified.

Researcher notes

The referenced issue, pull request, and commits document upstream correction work. However, the supplied bundle does not map each commit to a complete affected or fixed release matrix. Researchers should preserve that uncertainty and consult the Python advisory or distributor notices for branch-specific status.

Mitigation direction

  • Identify services that parse untrusted HTML using html.parser.HTMLParser.
  • Upgrade to a supported CPython build incorporating the referenced upstream patches.
  • Confirm exact fixed package versions through Python or operating-system distributor guidance.
  • Temporarily reduce untrusted HTML exposure where upgrades cannot be completed promptly.

Validation and detection

  • Inventory deployed Python versions and applications invoking HTMLParser.
  • Trace whether authenticated or network-originated HTML can reach the parser.
  • Confirm installed packages contain an upstream fix or documented vendor backport.
  • Run vendor-approved regression tests in staging and monitor parser latency and CPU usage.
Prepared
Confidence
high
Sources
8

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-1333: 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-2025-6069 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 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
1ADP providers
11Source 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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L2.81.4PSF

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2025-6069Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Python Software FoundationCPython0, 3.10.0, 3.11.0, 3.12.0, 3.13.0, 3.14.0a1unaffected
Weakness

CWE details

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

CWE-1333 · source CWE mapping

Inefficient Regular Expression Complexity

Inefficient Regular Expression Complexity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.