CVE-2024-36048: qtnetworkauth · n/a
Affects qtnetworkauthSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical · fixed in 6.7.1 : patch qtnetworkauth as a priority.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.7.1, 6.5.6, 6.2.13 +1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 May 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-25.
What to do
Upgrade org.qtproject/qtnetworkauth to 6.7.1, 6.5.6, 6.2.13 or 5.15.17.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavenorg.qtproject/qtnetworkauthpkg:maven/org.qtproject/qtnetworkauthOther threats | 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
European organizations should immediately identify all applications and systems using affected Qt versions, including embedded devices and third-party software dependencies. They must prioritize upgrading to the fixed Qt versions: 5.15.17 or later, 6.2.13 or later, 6.5.6 or later, and 6.7.1 or later as applicable. Where immediate patching is not feasible, organizations should implement compensating controls such as network segmentation to isolate vulnerable systems, enhanced monitoring for suspicious OAuth token usage, and strict access controls on systems handling OAuth authentication. Developers should audit their use of QAbstractOAuth to ensure no custom overrides weaken PRNG seeding further. Additionally, organizations should review OAuth token lifetimes and revoke potentially compromised tokens. Coordinating with software vendors and embedded device manufacturers to obtain patches or mitigations is critical. Finally, security teams should prepare incident response plans for potential exploitation scenarios involving OAuth token compromise.
Description
QAbstractOAuth in Qt Network Authorization in Qt before 5.15.17, 6.x before 6.2.13, 6.3.x through 6.5.x before 6.5.6, and 6.6.x through 6.7.x before 6.7.1 uses only the time to seed the PRNG, which may result in guessable values.
References
- codereview.qt-project.org/c/qt/qtnetworkauth/+/560317 (opens in a new tab)
- codereview.qt-project.org/c/qt/qtnetworkauth/+/560368 (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RGB6KUPJFQWUBKXVDPJUMAD6KNJJEWPW/ (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZPHAI3DKDCIU6XLNS6PV6GFS2PHH3GZM/ (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZOOZZZSK5PNRHFGQMUGUHVYWLILFJCRS/ (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RGB6KUPJFQWUBKXVDPJUMAD6KNJJEWPW/ (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZPHAI3DKDCIU6XLNS6PV6GFS2PHH3GZM/ (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZOOZZZSK5PNRHFGQMUGUHVYWLILFJCRS/ (opens in a new tab)