NVIDIA GPU and Tegra hardware contain a vulnerability in the internal microcontroller, which may allow a user with elevated privileges to ac
Noroxi assessment
Priority: Monitor (action score 16/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. Special conditions such as timing or configuration are required.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
NVIDIA GPU and Tegra hardware contain a vulnerability in the internal microcontroller, which may allow a user with elevated privileges to access protected information by identifying, exploiting, and loading vulnerable microcode. Such an attack may lead to information disclosure.
- Published
- Nov 20, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
16
Monitor
Low priority for now.
- CVSS
- 16 / 40 · 4.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- 4.1
- CNA · nvidia
- 4.1
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| nvidia | dgx-1 p100 | cpe:2.3:h:nvidia:dgx-1_p100 |
| nvidia | dgx-1 v100 | cpe:2.3:h:nvidia:dgx-1_v100 |
| nvidia | dgx-2 | cpe:2.3:h:nvidia:dgx-2 |
| nvidia | dgx station a100 | cpe:2.3:h:nvidia:dgx_station_a100 |
| nvidia | drive constellation | cpe:2.3:h:nvidia:drive_constellation |
| nvidia | geforce gt 605 | cpe:2.3:h:nvidia:geforce_gt_605 |
| nvidia | geforce gt 610 | cpe:2.3:h:nvidia:geforce_gt_610 |
| nvidia | geforce gt 620 | cpe:2.3:h:nvidia:geforce_gt_620 |
| nvidia | geforce gt 625 | cpe:2.3:h:nvidia:geforce_gt_625 |
| nvidia | geforce gt 630 | cpe:2.3:h:nvidia:geforce_gt_630 |
| nvidia | geforce gt 635 | cpe:2.3:h:nvidia:geforce_gt_635 |
| nvidia | geforce gt 640 | cpe:2.3:h:nvidia:geforce_gt_640 |
and 125 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- nvidia dgx station a100all versions
- nvidia dgx-1 p100all versions
- nvidia dgx-1 v100all versions
- nvidia dgx-2all versions
- nvidia drive constellationall versions
- nvidia geforce gt 605all versions
- nvidia geforce gt 610all versions
- nvidia geforce gt 620all versions
- nvidia geforce gt 625all versions
- nvidia geforce gt 630all versions
- nvidia geforce gt 635all versions
- nvidia geforce gt 640all versions
- nvidia geforce gt 705all versions
- nvidia geforce gt 710all versions
- nvidia geforce gt 720all versions
- nvidia geforce gt 730all versions
- nvidia geforce gt 740all versions
- nvidia geforce gtx 1050all versions
- nvidia geforce gtx 1050 tiall versions
- nvidia geforce gtx 1060all versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (nvidia). Independent of NVD's CPE analysis and usually ahead of it.
NVIDIA NVIDIA GPU and Tegra hardware
- Maxwell (except GM206), Tegra X1, Tegra X1+affected
Same product
nvidia: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-34400NVIDIA GPU and Tegra hardware contain a vulnerability in the internal microcontroller which may allow a user with elevated privileges to gai17Monitor
- CVE-2021-34399NVIDIA GPU and Tegra hardware contain a vulnerability in the internal microcontroller which may allow a user with elevated privileges to gai17Monitor
- CVE-2021-1125NVIDIA GPU and Tegra hardware contain a vulnerability in the internal microcontroller which may allow a user with elevated privileges to cor17Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-1088Nov 20, 2021 · NVIDIA GPU and Tegra hardware contain a vulnerability in the internal microcontroller which may allow a user with elevated privileges to uti17Monitor
- ← EarlierCVE-2021-1105Nov 20, 2021 · NVIDIA GPU and Tegra hardware contain a vulnerability in the internal microcontroller which may allow a user with elevated privileges to acc17Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
- NVIDIA Public Bug BountyIntigriti · paid · up to $15,000
- NVIDIA Vulnerability Disclosure ProgramIntigriti · disclosure only (VDP)
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-21-0934 · Nov 22, 2021(NVIDIA Zafiyeti)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- Administrator privileges are required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.