Application crash via HTTP/2 null pointer dereference
Published Oct 26, 2026 · Updated Oct 26, 2026
A null dereference in Qt Framework's QNetworkAccessManager lets remote attackers crash applications via HTTP/2 replies. Withholding SETTINGS ACK lets a server plant a null pointer through RST_STREAM on a completed stream, then trigger its dereference with PUSH_PROMISE for that stream. Exploitation requires a connection to a malicious or compromised HTTP/2 server and active user interaction; the documented consequence is an application crash.
Summary
What happened
A null dereference in Qt Framework's QNetworkAccessManager lets remote attackers crash applications via HTTP/2 replies. Withholding SETTINGS ACK lets a server plant a null pointer through RST_STREAM on a completed stream, then trigger its dereference with PUSH_PROMISE for that stream. Exploitation requires a connection to a malicious or compromised HTTP/2 server and active user interaction; the documented consequence is an application crash.
The record
- CVE
- CVE-2026-96432
- Published
- Oct 26, 2026
- Updated
- Oct 26, 2026
- Vendor
- The Qt Company
- Product
- Qt Framework
- Classifications
- CWE-476, CAPEC-220, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 26, 2026CVE publishedPublication date reported by the CVE source.
- Oct 26, 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.8.0 <=6.8.9
- Affected versionversion=6.9.0 <=6.11.2
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