CORS · Inappropriate Implementation
Source GCVE Database
Not known to be exploited · CVSS 4.2 Medium : upgrade to 151.0.7922.169 when convenient.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 151.0.7922.169
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Aug 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 16 Nov 2026.
What to do
Upgrade Chrome to 151.0.7922.169.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleChrome | Affected
| Fixed in
|
AI-suggested
Since the vulnerability affects versions prior to 151.0.7922.169, upgrading to version 151.0.7922.169 or later is recommended once a fix is confirmed. Until then, users should exercise caution with untrusted content and avoid compromising the renderer process. Monitor vendor advisories for official patches or updates.
Description
A vulnerability in the Cross-Origin Resource Sharing (CORS) implementation in Google Chrome versions prior to 151.0.7922.169 allows a remote attacker who has compromised the renderer process to bypass site isolation using a crafted HTML page. The issue is classified with medium severity and has a CVSS score of 4.2.