CVE-2026-111487: qt5-qt3d security update
Affects qt5-qt3dSource GCVE Database
Not known to be exploited · CVSS 4.3 Medium : upgrade to 5.15.9-3.el9_9.1 when convenient.
Data as of 21 Nov 2026, 21:13 UTC
Thin evidence
One scorer or none| CNA (Qt) | CVSS 4.0 | 4.3 |
|---|
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.15.9-3.el9_9.1
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:U/R:U/RE:L/U:AmberExploitation evidence
Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 24 Oct 2026.
What to do
Upgrade the AlmaLinux to 5.15.9-3.el9_9.1.
Patches and advisories
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AlmaLinux 9qt5-qt3d | Affected
| Fixed in
|
| AlmaLinux 9qt5-qt3d-devel | Affected
| Fixed in
|
| AlmaLinux 9qt5-qt3d-examples | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A security update fixing this vulnerability is available in qt5-qt3d version 5.15.9-3.el9_9.1. Users should apply this update promptly to remediate the issue. Refer to the Red Hat advisory for detailed update instructions. No additional mitigation steps are indicated by the vendor.
Description
A security vulnerability in the Qt3D assimp plugin of the qt5-qt3d package allows for arbitrary code execution via an out-of-bounds write. This affects versions prior to 5.15.9-3.el9_9.1. The issue has been addressed in the fixed version 5.15.9-3.el9_9.1, and a security update is available from Red Hat.