Skip to main content
CVE-2024-33763VulnerabilityPublished Updated

CVE-2024-33763: lunasvg · n/a

Affects lunasvgSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 54% 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:N/I:N/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 2026-10-25.

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

1. Monitor lunasvg project repositories and security advisories closely for official patches addressing CVE-2024-33763 and apply them promptly once released. 2. Until patches are available, restrict network exposure of services utilizing lunasvg, especially those processing untrusted SVG inputs. 3. Implement input validation and sanitization to limit malformed or malicious SVG content that could trigger the vulnerability. 4. Employ runtime application monitoring to detect abnormal crashes or behavior indicative of exploitation attempts. 5. Consider sandboxing or isolating components that use lunasvg to contain potential denial-of-service impacts. 6. Review and update incident response plans to include scenarios involving SVG rendering failures. 7. If feasible, temporarily disable or replace lunasvg-dependent functionality in critical systems until a fix is applied.

Description

lunasvg v2.3.9 was discovered to contain a stack-buffer-underflow at lunasvg/source/layoutcontext.cpp.

References

Community reviews

Loading reviews…