When processing SVG marker references, the renderer retrieves a node by its id attribute and casts it to QSvgMarker* without verifying the node type. A non-marker element (such as a <line> element) that references itself as a marker triggers an out-of-bounds heap read due to the object size difference between QSvgLine and QSvgMarker,
followed by an endless recursion that bypasses the marker recursion
guard through incorrect virtual dispatch. The result is an application
crash (denial of service).
This issue affects Qt SVG:
from 6.7.0 before 6.8.8, from 6.9.0 before 6.11.1.
Project Subscriptions
No data.
No advisories yet.
Solution
Apply fix: https://codereview.qt-project.org/c/qt/qtsvg/+/724887
Workaround
No workaround given by the vendor.
Wed, 06 May 2026 14:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 06 May 2026 12:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A type confusion vulnerability in Qt SVG allows an attacker to cause an application crash via a crafted SVG image. When processing SVG marker references, the renderer retrieves a node by its id attribute and casts it to QSvgMarker* without verifying the node type. A non-marker element (such as a <line> element) that references itself as a marker triggers an out-of-bounds heap read due to the object size difference between QSvgLine and QSvgMarker, followed by an endless recursion that bypasses the marker recursion guard through incorrect virtual dispatch. The result is an application crash (denial of service). This issue affects Qt SVG: from 6.7.0 before 6.8.8, from 6.9.0 before 6.11.1. | |
| Title | Type confusion and heap-buffer-overflow in Qt SVG marker handling causing application crash | |
| Weaknesses | CWE-122 CWE-843 |
|
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: TQtC
Published:
Updated: 2026-05-06T13:11:44.674Z
Reserved: 2026-04-13T12:16:27.416Z
Link: CVE-2026-6210
Updated: 2026-05-06T13:11:37.140Z
Status : Received
Published: 2026-05-06T12:16:49.957
Modified: 2026-05-06T12:16:49.957
Link: CVE-2026-6210
No data.
OpenCVE Enrichment
Updated: 2026-05-06T16:00:06Z