Memory corruption via HTTP/2 POST upload race
Published Jun 11, 2025 · Updated Jul 29, 2026
Use after free in Qt Framework 6.9.0 allows attackers to corrupt application memory via concurrent HTTP/2 POST and error processing. QHttp2ProtocolHandler races a QHttp2Stream body upload against error-response handling and accesses stream state after its lifetime ends. An affected application must upload a POST body over HTTP/2 while an error response is handled; ordinary HTTP is unaffected.
Summary
What happened
Use after free in Qt Framework 6.9.0 allows attackers to corrupt application memory via concurrent HTTP/2 POST and error processing. QHttp2ProtocolHandler races a QHttp2Stream body upload against error-response handling and accesses stream state after its lifetime ends. An affected application must upload a POST body over HTTP/2 while an error response is handled; ordinary HTTP is unaffected.
The record
- CVE
- CVE-2025-5991
- Published
- Jun 11, 2025
- Updated
- Jul 29, 2026
- Vendor
- The Qt Company
- Product
- Qt Framework
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 11, 2025CVE publishedPublication date reported by the CVE source.
- Jul 29, 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
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo