Skip to main content
VulnerabilityPublished Updated

CVE-2024-33768: lunasvg · Improper Isolation or Compartmentalization

Affects lunasvgSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 57% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 May 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubkeepinggg/lunasvgpkg:github/keepinggg/lunasvgOther threatsAffected
  • =2.3.9
Fixed in–

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

AI-suggested

Until an official patch is released, organizations should implement several specific mitigations to reduce risk. First, restrict or block untrusted SVG input from external sources, especially over network interfaces exposed to the internet. Employ input validation and sanitization to detect and reject malformed or suspicious SVG files. Use application-layer firewalls or intrusion detection systems to monitor and block attempts to exploit the segmentation violation. Consider isolating or sandboxing processes that utilize lunasvg to limit the impact of potential crashes or code execution. Review and update incident response plans to include detection and mitigation of SVG-related attacks. Engage with vendors or maintainers of lunasvg to track patch releases and apply updates promptly. Where feasible, temporarily replace lunasvg with alternative SVG rendering libraries that do not contain this vulnerability. Conduct thorough security testing and code audits of applications integrating lunasvg to identify and remediate related risks.

Description

lunasvg v2.3.9 was discovered to contain a segmentation violation via the component composition_solid_source_over.

References

Community reviews

Loading reviews…