CVE-2024-46478: htmldoc · Classic Buffer Overflow
Affects htmldocSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 24 Oct 2024
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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubmichaelrsweet/htmldocpkg:github/michaelrsweet/htmldocOther 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
- Immediately audit all systems to identify instances of HTMLDOC version 1.9.18 or earlier and isolate them from untrusted networks.
- Apply vendor patches or updates as soon as they become available; monitor official HTMLDOC repositories and security advisories closely.
- If patches are unavailable, implement network-level access controls to restrict inbound traffic to services using HTMLDOC, limiting exposure to trusted users only.
- Employ application-layer protections such as sandboxing HTMLDOC processes or running them with least privilege to contain potential exploitation.
- Utilize runtime memory protection mechanisms like Address Space Layout Randomization (ASLR), Data Execution Prevention (DEP), and stack canaries to mitigate buffer overflow exploitation.
- Monitor system and application logs for anomalous behavior indicative of exploitation attempts, including unexpected crashes or unusual process activity.
- Consider replacing HTMLDOC with alternative, actively maintained document processing tools if feasible.
- Educate development and operations teams about secure coding practices to prevent similar vulnerabilities in custom integrations.
- Conduct regular vulnerability scanning and penetration testing focused on document processing components to detect weaknesses early.
Description
HTMLDOC v1.9.18 contains a buffer overflow in parse_pre function,ps-pdf.cxx:5681.