VulnerabilityPublished 1 May 2024Updated 4 Dec 2024

CVE-2024-33766: lunasvg · Divide By Zero

Affects lunasvgSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 48% 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:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 1 May 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubkeepinggg/lunasvg`pkg:github/keepinggg/lunasvg`Other threats	Affected =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

To mitigate CVE-2024-33766, organizations should monitor the lunasvg project and related security advisories for official patches or updates addressing the floating point exception. Until a patch is available, consider implementing input validation and sanitization to detect and reject malformed or suspicious SVG files that could trigger the vulnerability. Employ runtime protections such as exception handling around SVG rendering calls to prevent application crashes from propagating and causing denial of service. Where possible, isolate SVG processing in sandboxed environments to limit impact in case of crashes. Additionally, conduct code reviews and testing focused on floating point operations within lunasvg integrations. Network-level protections such as web application firewalls (WAFs) can help detect and block exploit attempts targeting SVG processing endpoints. Finally, maintain robust monitoring and incident response capabilities to quickly identify and respond to any exploitation attempts.

Description

lunasvg v2.3.9 was discovered to contain an FPE (Floating Point Exception) at blend_transformed_tiled_argb.isra.0.

Impact

The primary impact of CVE-2024-33766 is a denial of service condition caused by application crashes when processing maliciously crafted SVG images. This can disrupt services relying on lunasvg for SVG rendering, including web applications, graphic design tools, and embedded systems that handle SVG content. While the vulnerability does not compromise confidentiality or integrity, the availability impact can be significant in environments where SVG rendering is critical, potentially leading to service outages or degraded user experience. Organizations that embed lunasvg in client-facing or automated processing systems may face increased risk of operational disruption. The ease of exploitation (no authentication or user interaction required) and network accessibility increase the threat level, especially in internet-facing applications. However, the lack of known exploits in the wild and absence of patches currently limit immediate widespread impact.

References

github.com/keepinggg/poc/tree/main/poc_of_lunasvg (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 03:00 UTC

WeaknessesCWE-369

Technical details

References

Community reviews

Related threats