Quick answers
- Is CVE-2026-107157 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-107157 being exploited in the wild.
- How severe is CVE-2026-107157?
- Informational severity, published 26 October 2026.
- Which products and versions are affected?
- Qt Framework 5.12.0 to 6.8.8, 6.9.0 to 6.11.2 (64-bit platforms only).
- Is there a fix for CVE-2026-107157?
- Yes: fixed in Qt 6.8.9, 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-107157 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-107157?
- Check whether you run Qt Framework 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.8.9, Qt 6.11.3, Qt 6.12.0
Technical details
An out-of-bounds read vulnerability exists in the QCborValue::fromCbor() function when processing specially crafted CBOR-format input. The vulnerability is reachable via input parsing with no authentication or user interaction required beyond providing the malicious data, and can result in application crash (denial of service) or potential information disclosure. The flaw affects both the Qt 5 and Qt 6 branches across most versions.
Affected products
- Qt Qt Framework 5.12.0 to 6.8.8, 6.9.0 to 6.11.2 (64-bit platforms only)
Timeline
- 2026-10-26: disclosed