CVE-2026-45729
Null Pointer Dereference in Thor Vector Graphics Engine
Publication date: 2026-06-01
Last updated on: 2026-06-01
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| thorvg | thorvg | to 1.0.5 (exc) |
| thorvg | thor_vector_graphics | to 1.0.5 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-476 | The product dereferences a pointer that it expects to be valid but is NULL. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-45729 is a null pointer dereference vulnerability in the Thor Vector Graphics (ThorVG) library, specifically in the SvgLoader::run() function. When the library processes untrusted or malformed SVG data, the svgSceneBuild() function can return a null pointer without proper validation. This leads to the application crashing due to a segmentation fault when it tries to dereference this null pointer.
The vulnerability affects versions of ThorVG up to 1.0.0 and can be triggered with a minimal 6-byte payload. It requires no privileges but does require user interaction to process the malicious SVG data. The issue was patched in version 1.0.5 by adding checks to prevent dereferencing null pointers and improving exception handling during SVG parsing.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability in ThorVG (CVE-2026-45729) results in a denial of service (application crash) when processing untrusted SVG files due to a null pointer dereference. It does not lead to data exposure, memory corruption, or unauthorized access.
Because the issue only causes a crash without compromising data confidentiality or integrity, it has limited direct impact on compliance with standards like GDPR or HIPAA, which primarily focus on protecting personal data privacy and security.
However, denial of service vulnerabilities can indirectly affect compliance if they disrupt availability requirements or system reliability, which are components of some regulatory frameworks.
How can this vulnerability impact me? :
This vulnerability can cause applications using the ThorVG library to crash when processing specially crafted malicious SVG files. The impact is a denial of service (DoS) condition, where the affected process terminates unexpectedly.
Since the vulnerability does not lead to memory corruption or data exposure, it does not allow attackers to execute arbitrary code or access sensitive information. However, the crash can disrupt normal application operations, potentially affecting user experience or availability.
Applications that rely on ThorVG for SVG rendering, such as Samsung Tizen OS, Godot Engine, and LVGL, are potentially impacted if they process untrusted SVG inputs.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for crashes or denial of service events in applications using the ThorVG library when processing SVG files, especially untrusted or malformed SVG inputs.
Fuzz testing tools like AFL++ were used to discover this issue by feeding malformed SVG data to the SvgLoader::run() function, causing a crash with a minimal 6-byte payload.
To detect exploitation attempts or crashes, you can check application logs or system crash reports for segmentation faults related to SVG processing.
Suggested commands include:
- Use system logs to find crashes: `journalctl -xe` or `dmesg | grep segfault`
- Monitor application logs for unexpected terminations or errors during SVG file processing.
- Run fuzz testing on your SVG processing components using AFL++ or similar fuzzers to identify if malformed SVG inputs cause crashes.
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to upgrade the ThorVG library to version 1.0.5 or later, where the vulnerability has been patched.
The patch includes improved robustness in the SVG loader by adding null pointer checks and exception handling to prevent crashes from malformed SVG inputs.
If upgrading immediately is not possible, avoid processing untrusted or malformed SVG files with affected versions of ThorVG to reduce the risk of denial of service.
Additionally, monitor your applications for crashes and apply any vendor-specific patches or updates that incorporate the fix.