Vulnerability in QtCore (CVE-2025-5455)
Summary
Vulnerability in QtCore (CVE-2025-5455). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 5.15.19 or later.
Original description
The description as published by the source.
An issue was found in the private API function qDecodeDataUrl() in QtCore, which is used in QTextDocument and QNetworkReply, and, potentially, in user code.
If the function was called with malformed data, for example, an URL that
contained a "charset" parameter that lacked a value (such as
"data:charset,"), and Qt was built with assertions enabled, then it would hit an assertion, resulting in a denial of service
(abort).
This impacts Qt up to 5.15.18, 6.0.0->6.5.8, 6.6.0->6.8.3 and 6.9.0. This has been fixed in 5.15.19, 6.5.9, 6.8.4 and 6.9.1.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-5455 has been found in QtCore.
Risk of unauthorized operations or information disclosure.
What to do: upgrade QtCore to 5.15.19 or later.
If unsure, ask your IT team or search "QtCore CVE-2025-5455" on the vendor's site.
CVE-2025-5455 (QtCore) — CWE-20
Patched: 5.15.19 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in QtCore.
Check the vendor advisory for the affected versions of QtCore.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 5.15.19.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'QtCore' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'QtCore' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
QtCoreを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade QtCore to 5.15.19ステージング環境で 5.15.19 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2025-5455 qt6-base
- Ubuntu UBUNTU-CVE-2025-5455 qtbase-opensource-src