NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel mode layer where an unprivileged user could bypass read-only memory protection due to incorrect authorization, enabling write access to memory marked read-only. A successful exploit of this vulnerability might lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering.
CVE-2026-47591
HIGHPre-NVD 7.87.8—Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-30. A secondary CVSS source baseline 7.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v3
- 7.8
- EG Score
- 7.8HIGHhigh confidence
- EG Risk
- 35EG Risk 35/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity78% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix. - EPSS PROB
- 0.1%
- EPSS %ILE
- 1st
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).
No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
September 30, 2026
Last Modified
October 2, 2026
Advisory Details (2)
Auto-updated Sep 30, 2026No patch confirmed yet.
generic
product-security/2026/5861 at main · NVIDIA/product-security · GitHub
https://github.com/NVIDIA/product-security/tree/main/2026/5861Vendor Advisories for CVE-2026-47591(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(9 across 3 ecosystems)
Debian:12(5)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nvidia-graphics-drivers | 1.0.6629+1-2 ... 555.58.02-3 (645 versions) |
| — |
| nvidia-graphics-drivers-tesla | 418.116.00-1 ... 525.85.12-1 (29 versions) |
| — |
| nvidia-graphics-drivers-tesla-470 | 470.103.01-1 ... 470.82.01-1 (54 versions) |
| — |
| nvidia-graphics-drivers-tesla-535 | 535.216.01-1 ... 535.274.02-2 (11 versions) |
| — |
| nvidia-open-gpu-kernel-modules | 515.43.04-1 ... 555.58.02-2 (65 versions) |
| — |
Debian:13(3)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nvidia-graphics-drivers | 1.0.6629+1-2 ... 555.58.02-3 (644 versions) |
| — |
| nvidia-graphics-drivers-tesla-535 | 535.216.01-1 ... 535.274.02-2 (11 versions) |
| — |
| nvidia-open-gpu-kernel-modules | 515.43.04-1 ... 555.58.02-2 (65 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nvidia-graphics-drivers | 1.0.6629+1-2 ... 555.58.02-3 (644 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 25× in last 7d / 25× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-05 09:32 UTCEG score recompute
- 2026-10-05 09:32 UTCGHSA enrichment
- 2026-10-04 23:22 UTCEPSS rescore
- 2026-10-04 20:44 UTCGHSA enrichment
- 2026-10-04 07:55 UTCGHSA enrichment
- 2026-10-03 19:05 UTCEG score recompute
- 2026-10-03 19:05 UTCGHSA enrichment
- 2026-10-03 14:25 UTCEPSS rescore
- 2026-10-03 06:14 UTCEG score recompute
- 2026-10-03 06:14 UTCGHSA enrichment
- 2026-10-02 17:25 UTCGHSA enrichment
- 2026-10-02 04:32 UTCEG score recompute
- 2026-10-02 04:32 UTCGHSA enrichment
- 2026-10-02 04:05 UTCEG score recompute
- 2026-10-02 04:04 UTCGHSA enrichment
- 2026-10-01 20:08 UTCEG score recompute
- 2026-10-01 20:08 UTCGHSA enrichment
- 2026-10-01 19:50 UTCEPSS rescore
- 2026-10-01 07:19 UTCEG score recompute
- 2026-10-01 07:19 UTCGHSA enrichment
- 2026-09-30 18:31 UTCEG score recompute
- 2026-09-30 18:06 UTCEG score recompute
- 2026-09-30 16:20 UTCEG score recompute
- 2026-09-30 16:03 UTCEG score recompute
- 2026-09-30 16:01 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-47591?
CVE-2026-47591 is a high vulnerability published on September 30, 2026. NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel mode layer where an unprivileged user could bypass read-only memory protection due to incorrect authorization, enabling write access to memory marked read-only. A successful exploit of this vulnerability might lead to code…
When was CVE-2026-47591 disclosed?
CVE-2026-47591 was first published on September 30, 2026, with the most recent update on October 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47591 actively exploited?
CVE-2026-47591 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47591?
CVE-2026-47591 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-47591?
No fix for CVE-2026-47591 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-47591 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47591
Is Your Infrastructure Affected by CVE-2026-47591?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.