Process interruption via unreleased parser allocations
Published Jun 23, 2025 · Updated Jun 23, 2025
Memory leak in HTML Tidy 5.8.0 allows local users to consume process memory by parsing a crafted HTML or XML file. The parser creates nodes, attributes, and strings through defaultAlloc in src/alloc.c but fails to release all allocated blocks after parsing. Local ability to supply input to a Tidy process is required, and repeated processing can exhaust memory and interrupt that process.
Summary
What happened
Memory leak in HTML Tidy 5.8.0 allows local users to consume process memory by parsing a crafted HTML or XML file. The parser creates nodes, attributes, and strings through defaultAlloc in src/alloc.c but fails to release all allocated blocks after parsing. Local ability to supply input to a Tidy process is required, and repeated processing can exhaust memory and interrupt that process.
The record
- CVE
- CVE-2025-6498
- Published
- Jun 23, 2025
- Updated
- Jun 23, 2025
- Vendor
- HTML Tidy Advocacy Community Group
- Product
- HTML Tidy
- Classifications
- CWE-401, CWE-404, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 23, 2025CVE publishedPublication date reported by the CVE source.
- Jun 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.8.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- tidy-html5_crash_3.txt reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo