CVE-2024-0097 is a high severity (CVSS 7.5) improper privilege management flaw in NVIDIA ChatRTX for Windows, tied to interprocess communication between different processes on the machine. NVIDIA lists versions up to and including 0.2.1 as affected, and ChatRTX 0.3 is the fixed release. Update affected Windows machines.
What's affected
NVIDIA bulletin 5533 lists NVIDIA ChatRTX for Windows, all versions up to and including 0.2.1, as affected. It says earlier releases are also affected. The fix is ChatRTX 0.3.
This CVE is the companion of CVE-2024-0096, which covers a separate flaw in the same UI. One upgrade covers both.
How to check if you're exposed
There is no package manager check for a typical ChatRTX install. Look at the version in the application itself or in the Windows installed programs list. For managed fleets, query installed software from your endpoint tool and filter on the ChatRTX name. Versions at or below 0.2.1 are in scope.
What to do now
- Locate every Windows machine running ChatRTX, including personal workstations used for local AI experiments.
- Upgrade to ChatRTX 0.3 or later.
- On machines you cannot update right away, restrict who has local accounts.
- Uninstall ChatRTX where it is no longer used.
Why it matters
The weakness type is CWE-269. The NVD description says a user can cause improper privilege management by exploiting interprocess communication between different processes. In general terms, one process trusts messages from another without enough checks on who sent them and what they are allowed to ask for.
NVIDIA lists information disclosure, escalation of privileges and data tampering as outcomes. The vector is local with high complexity, and the record does not show exploitation in the wild. Local AI tools often run next to private files, which is the reason to patch even a local flaw. Safeguard has a free in-browser dependency scan at gold.safeguard.sh/scan, and the Gold directory lists the CVE and CWE pages used here.
Quick check
Does updating fix CVE-2024-0096 too?
Yes. NVIDIA lists the same fixed ChatRTX version, 0.3, for both CVEs.
Is a remote attacker able to use this?
The vector is local, so the attacker needs a foothold on the machine first.
Sources
Last reviewed: 19 October 2026.
