Quick answers
- Is CVE-2026-16762 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-16762 being exploited in the wild.
- How severe is CVE-2026-16762?
- Informational severity, published 23 October 2026.
- Which products and versions are affected?
- Qt <unknown.
- Is there a fix for CVE-2026-16762?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-16762 attacked?
- It is attacked over the network or with local access, in a software library.
- Am I affected by CVE-2026-16762?
- 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.
Technical details
QXmlStreamReader exhibits a denial-of-service vulnerability where specially crafted XML documents trigger disproportionate CPU consumption during parsing. The attack requires only network or local ability to supply malicious XML input to an application using the affected component; no authentication or user interaction beyond parsing the input is necessary. An attacker gains temporary denial of service against the affected application process, with no code execution or data exposure.
Affected products
- Qt Qt <unknown
Timeline
- 2026-10-23: disclosed