GeForce: Missing Authorization
CVE-2026-24190 is a high-severity missing authorization vulnerability in GeForce from NVIDIA, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. Affected GeForce versions: All driver versions prior to 595.71.05; All driver versions prior to 580.159.03; All driver versions prior to 535.309.01, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.22% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update GPU Display Driver to 535.309.01 or 539.72 or 580.159.03 or 582.53, whichever matches your release line, or a later version.
- Read the advisory on nvidia.custhelp.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| NVIDIA | GeForce | All driver versions prior to 595.71.05; All driver versions prior to 580.159.03; All driver versions prior to 535.309.01; All driver versions prior to 596.36 | Not stated |
| NVIDIA | NVIDIA RTX, Quadro, NVS | All driver versions prior to 595.71.05; All driver versions prior to 580.159.03; All driver versions prior to 535.309.01; All driver versions prior to 596.36; All driver versions prior to 582.53; All driver versions prior to 539.72 | Not stated |
| NVIDIA | Tesla | All driver versions prior to 595.71.05; All driver versions prior to 580.159.03; All driver versions prior to 535.309.01; All driver versions prior to 596.36; All driver versions prior to 582.53; All driver versions prior to 539.72 | Not stated |
| NVIDIA | GPU Display Driver | 535 up to, but not including, 535.309.01; 535 up to, but not including, 539.72; 580 up to, but not including, 580.159.03; 580 up to, but not including, 582.53; 595 up to, but not including, 595.36; 595 up to, but not including, 595.71.05 | 535.309.01, 539.72, 580.159.03, 582.53, 595.36, 595.71.05 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (nvidia.com).
Official description
NVIDIA Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer, where a user could cause improper access to GPU resources. A successful exploit of this vulnerability might lead to denial of service, escalation of privileges, information disclosure, data tampering, and code execution.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Authorization
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
How developers prevent this class of flaw
- Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- nvd.nist.gov/vuln/detail/CVE-2026-24190Third Party Advisory
- cve.org/CVERecord?id=CVE-2026-24190Third Party Advisory
Other vulnerabilities in GeForce
- 7.1 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.0 High severity
- 7.8 High severity
Recent Missing Authorization vulnerabilities
- 7.1 High severity
- 7.5 High severity
- 7.5 High severity
- 9.0 Critical severity
- 7.3 High severity
- 8.2 High severity
Spotted an error? Tell us.