p PatchFirst

PatchFirst · Latest vulnerabilities

qtsvg-opensource-src vulnerabilities

Vulnerabilities published for qtsvg-opensource-src in the last 30 days: 1. Listed in the KEV catalogue: 0.

RSS ↗
Filter vulnerabilities
Clear filters

Vulnerabilities: 8

  1. CVE-2026-8168

    High · CVSS 7.1EPSS 0.4%No fix published

    Denial-of-service vulnerability in the SVG parser and renderer impacts Qt

    Uncontrolled recursion in the SVG parser and renderer of the Qt SVG module (QtSvg) in Qt Group Qt allows attackers to cause a denial of service (application crash via stack exhaustion) via a crafted SVG file with deeply nested elements.

    Published Updated
  2. CVE-2026-6210

    High · CVSS 8.7EPSS 0.47%No fix published

    Type confusion and heap-buffer-overflow in Qt SVG marker handling causing application crash

    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 SV

    Published Updated
  3. CVE-2021-3481

    High · CVSS 7.1EPSS 0.55%Fix available

    CVE-2021-3481

    A flaw was found in Qt. An out-of-bounds read vulnerability was found in QRadialFetchSimd in qt/qtbase/src/gui/painting/qdrawhelper_p.h in Qt/Qtbase. While rendering and displaying a crafted Scalable Vector Graphics (SVG) file this flaw may lead to an unauthorized memory access. The highest threat from this vulnerability is to data confidentiality and the application availability.

    • Update to 5.15.2-3
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →