CVE-2023-32763

An issue was discovered in Qt before 5.15.15, 6.x before 6.2.9, and 6.3.x through 6.5.x before 6.5.1. When a SVG file with an image inside it is rendered, a QTextLayout buffer overflow can be triggered.

Published: 2023-05-28 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-32763 is rated Low Risk (38.7/100): CVSS High severity, with low exploitation likelihood (EPSS 0.09%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-32763

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-21 0.57% 0.09% -0.48%
2 2025-11-18 0.09% 0.57% +0.48%
3 2025-04-15 — 0.09% —

Full EPSS history (12 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-32763

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2023-32763

OS Trackers for CVE-2023-32763

vendor priority summary link
alpine — CVE-2023-32763: 2 source package rows (qt5-qtbase, qt6-qtbase); 12 state rows across 6 repos (3.18-community, 3.19-community, 3.20-community, 3.21-community, 3.22-community, edge-community); fixed 12, open 0. https://security.alpinelinux.org/vuln/CVE-2023-32763
debian not yet assigned CVE-2023-32763 not yet assigned priority: Debian including 3 source packages (qt6-base, qtbase-opensource-src, qtbase-opensource-src-gles), 14 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 13, open 1. https://security-tracker.debian.org/tracker/CVE-2023-32763
gentoo normal CVE-2023-32763: 1 GLSA(s) (202402-03), 1 atom(s) (dev-qt/qtgui); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2023-32763
suse high — https://www.suse.com/security/cve/CVE-2023-32763/
ubuntu medium CVE-2023-32763 medium priority: Ubuntu including 3 source packages (qt6-base, qtbase-opensource-src, qtbase-opensource-src-gles), 39 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 21, needs-triage 10, not-affected 4, DNE 3, released 1. https://ubuntu.com/security/CVE-2023-32763

Affected software / configurations for CVE-2023-32763

Vendor Product Version Raw CPE
qt qt < 5.15.15 cpe:2.3:a:qt:qt:*:*:*:*:*:*:*:*
qt qt >= 6.0.0, < 6.2.9 cpe:2.3:a:qt:qt:*:*:*:*:*:*:*:*
qt qt >= 6.3.0, < 6.5.1 cpe:2.3:a:qt:qt:*:*:*:*:*:*:*:*

References for CVE-2023-32763

cvelogic Threat Intelligence