Skip to main content
CVE-2024-45508VulnerabilityPublished Updated

CVE-2024-45508: htmldoc · n/a

Affects htmldocSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 1.9.19 as a priority.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.9.19
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Sep 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

Upgrade michaelrsweet/htmldoc to 1.9.19.

Affected software

ProductAffectedFixed in
GitHubmichaelrsweet/htmldocpkg:github/michaelrsweet/htmldocOther threatsAffected
  • <1.9.19
Fixed in
  • 1.9.19

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-45508, organizations should prioritize upgrading HTMLDOC to version 1.9.19 or later once the patch is officially released. Until then, consider the following specific measures: 1) Restrict access to HTMLDOC services to trusted networks and users to reduce exposure to untrusted input. 2) Implement strict input validation and sanitization on HTML content before processing to minimize the risk of triggering the vulnerability. 3) Employ sandboxing or containerization for the HTMLDOC process to limit the impact of potential exploitation. 4) Monitor logs and system behavior for anomalies indicative of exploitation attempts, such as crashes or unusual memory activity. 5) If upgrading is not immediately possible, consider disabling or isolating the parse_paragraph functionality or the entire HTMLDOC service temporarily. 6) Maintain an incident response plan to quickly address any suspected exploitation. These targeted actions go beyond generic advice by focusing on reducing attack surface and limiting damage while awaiting official patches.

Description

HTMLDOC before 1.9.19 has an out-of-bounds write in parse_paragraph in ps-pdf.cxx because of an attempt to strip leading whitespace from a whitespace-only node.

References

Community reviews

Loading reviews…