CVE-2024-30161: In Qt 6.5.4, 6.5.5, and 6.6.2, QNetworkReply header data might be accessed via a dangling pointer in Qt for We

Routine

MEDIUM 6.5REMOTEDOWNGRADE

CVE-2024-30161 is a medium-severity flaw (CVSS 6.5) affecting qt. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In Qt 6.5.4, 6.5.5, and 6.6.2, QNetworkReply header data might be accessed via a dangling pointer in Qt for WebAssembly (wasm). (Earlier and later versions are unaffected.)

Why this priority

Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 61%)
CISA exploited list	No
Weakness	CWE-416
Published	2024-03-24
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: qt

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-03-24 01:15 UTCPublished CVE record published
2026-06-17 07:26 UTCUpdated Record last modified

qt qt DOWNGRADE

Affected: 6.5.4 · 6.5.5 · 6.6.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 6.5.4

1. Check installed version

apt-cache policy qt || rpm -q qt || qt --version

2. No fixed release: DOWNGRADE to a release before 6.5.4 (Debian / Ubuntu)

apt-cache madison qt sudo apt install qt=<VERSION_BEFORE_6.5.4> sudo apt-mark hold qt

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list qt sudo dnf downgrade qt-<VERSION_BEFORE_6.5.4> sudo dnf versionlock add qt

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-30161?

qt: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2024-30161 being exploited?

CVE-2024-30161 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-30161 affect?

CVE-2024-30161 affects qt. Severity is medium (CVSS 6.5). In Qt 6.5.4, 6.5.5, and 6.6.2, QNetworkReply header data might be accessed via a dangling pointer in Qt for WebAssembly (wasm). (Earlier and later versions are unaffected.)

How urgent is CVE-2024-30161?

Priority 38/100. Remotely exploitable, no login, no user action

Related CVEs

CVE-2023-51714 CRITICAL 9.8 MITIGATE UPGRADE An issue was discovered in the HTTP2 implementation in Qt before 5.15.17, 6.x before 6.2.11, 6.3.x through 6.5
CVE-2020-0570 HIGH 7.3 UPGRADE MITIGATE Uncontrolled search path in the QT Library before 5.14.0, 5.12.7 and 5.9.10 may allow an authenticated user to
CVE-2025-5683 MEDIUM 5.5 UPGRADE When loading a specifically crafted ICNS format image file in QImage then it will trigger a crash. This issu
CVE-2024-39936 HIGH 8.6 UPGRADE An issue was discovered in HTTP2 in Qt before 5.15.18, 6.x before 6.2.13, 6.3.x through 6.5.x before 6.5.7, an
CVE-2024-36048 CRITICAL 9.8 UPGRADE MITIGATE 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

References

← Back to latest CVEs