Microsoft · MIPS: Work around LLVM bug when gp is used as global register variable
Affects MicrosoftSource GCVE Database
Not known to be exploited.
Data as of 30 Oct 2026, 06:59 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 2 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Security Response Center Microsoft | Affected
| Fixed in– |
Description
This vulnerability relates to a workaround for a bug in LLVM when the global pointer (gp) is used as a global register variable on the MIPS architecture. The information provided is minimal and does not include technical details, exploit status, or impact specifics. The affected product is Microsoft software version 3.0. No CVSS score is available, and no known exploits are reported.