Quick answers
- Is CVE-2026-95620 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-95620 being exploited in the wild.
- How severe is CVE-2026-95620?
- Informational severity, published 23 October 2026.
- Which products and versions are affected?
- Qt 6.9.0 to 6.11.2.
- Is there a fix for CVE-2026-95620?
- Yes: fixed in Qt 6.11.3, Qt 6.12.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-95620 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-95620?
- Check whether you run Qt at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Qt 6.11.3, Qt 6.12.0
Technical details
A use-after-free vulnerability exists in Qt's QNetworkAccessManager HTTP/2 client support within the Qt Network module. A malicious or compromised HTTP/2 server can trigger this defect by sending crafted responses, causing the client application to access freed memory and crash. The vulnerability requires only that the application connect to an HTTP/2 server; no authentication or user interaction beyond normal network communication is needed.
Affected products
- Qt Qt 6.9.0 to 6.11.2
Timeline
- 2026-10-23: disclosed