Client crash via HTTP/2 use-after-free
Published Oct 23, 2026 · Updated Oct 23, 2026
Use-after-free in Qt Framework's HTTP/2 client allows remote attackers to crash applications through a malicious server. The affected locus is QNetworkAccessManager in Qt Network, but the retrieved record does not identify the freed object or triggering protocol sequence. The application must connect to a malicious or compromised HTTP/2 server; the published assessment also requires active user interaction and unspecified additional conditions.
Summary
What happened
Use-after-free in Qt Framework's HTTP/2 client allows remote attackers to crash applications through a malicious server. The affected locus is QNetworkAccessManager in Qt Network, but the retrieved record does not identify the freed object or triggering protocol sequence. The application must connect to a malicious or compromised HTTP/2 server; the published assessment also requires active user interaction and unspecified additional conditions.
The record
- CVE
- CVE-2026-95620
- Published
- Oct 23, 2026
- Updated
- Oct 23, 2026
- Vendor
- The Qt Company
- Product
- Qt Framework
- Classifications
- CWE-416, CAPEC-220, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 23, 2026CVE publishedPublication date reported by the CVE source.
- Oct 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.9.0 <6.11.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us