CVE-2025-6496: HTACG tidy-html5 · NULL Pointer Dereference
Affects HTACG tidy-html5Source CVE Database V5
Not known to be exploited · CVSS 4.8 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 23 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubhtacg/tidy-html5pkg:github/htacg/tidy-html5Other threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Upgrade: The most effective mitigation is to upgrade tidy-html5 to a version later than 5.8.0 where this vulnerability is patched. Monitor HTACG project releases and apply updates promptly. 2. Access Control: Restrict local access to systems running applications that use tidy-html5, ensuring only trusted users have local login capabilities. 3. Sandboxing: Run applications using tidy-html5 in isolated environments or containers with limited privileges to contain potential crashes and prevent broader system impact. 4. Input Validation: Implement strict input validation and sanitization before passing data to tidy-html5 to reduce the likelihood of triggering the null pointer dereference. 5. Monitoring: Deploy monitoring to detect abnormal application crashes or service interruptions that may indicate exploitation attempts. 6. Incident Response: Prepare response plans for denial-of-service incidents related to this vulnerability, including rapid restart procedures and fallback mechanisms. 7. Vendor Coordination: If tidy-html5 is embedded in third-party software, coordinate with vendors to ensure timely patching and updates.
Description
A vulnerability was found in HTACG tidy-html5 5.8.0. It has been declared as problematic. This vulnerability affects the function InsertNodeAsParent of the file src/parser.c. The manipulation leads to null pointer dereference. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used.