CVE-2026-110944Qt Framework allocation without limits
CVE-2026-110944 is a allocation without limits in Qt Framework, rated low (2.7 on CVSS 4.0).
Why this priority: Low severity, with no exploitation signal.
Published · Updated · NVD status: Awaiting Analysis
What it is
Resources are allocated without a cap, so a caller can exhaust them.
How it is reached
An attacker can exploit it over the network, without an account, and nobody has to click anything.
What an attacker gains
The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker exhaust CPU, memory or connections until the service stops answering. The damage can spread past the vulnerable component into others.
Is it being exploited?
There is no public report of exploitation yet. It can be exploited automatically, at scale. EPSS estimates a 0.29% chance of exploitation activity in the next 30 days, higher than 22% of scored CVEs.
What to do
- Upgrade Qt Framework to a fixed version for your release line (6.11.3, 6.12.1).
- Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
Description from NVD
Resource exhaustion vulnerability in the HTTP request handling of the QHttpServer component of Qt HTTP Server.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Public entry points and shared services that must stay up. The flaw sits between untrusted traffic and shared capacity.
Trust boundaries in play
- Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
- Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
- Between untrusted traffic and shared capacity. An attacker who crosses it can exhaust CPU, memory or connections until the service stops answering.
Questions to answer about your own systems
- Where does Qt Framework run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.