CVE-2026-12027: Inappropriate implementation in Headless in Google Chrome prior to 149.0.7827.115 allowed a remote attacker who had compromised the renderer…
Noroxi assessment
Priority: Monitor (action score 38/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.22% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: chromium (Debian:12) 149.0.7827.114-1~deb12u1; chromium (Debian:13) 149.0.7827.114-1~deb13u1; chromium (Debian:14) 149.0.7827.114-1.
Low priority for now. Upgrade to chromium (Debian:12) 149.0.7827.114-1~deb12u1; chromium (Debian:13) 149.0.7827.114-1~deb13u1; chromium (Debian:14) 149.0.7827.114-1 or later.
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
Inappropriate implementation in Headless in Google Chrome prior to 149.0.7827.115 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
- Published
- Jun 11, 2026
- Updated
- Oct 26, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-250
Report tools
Action score
38
Low priority for now.
- CVSS
- 38 / 40 · 9.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi 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 |
|---|---|---|
| chrome | cpe:2.3:a:google:chrome | |
| apple | macos | cpe:2.3:o:apple:macos |
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| microsoft | windows | cpe:2.3:o:microsoft:windows |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Chrome). Independent of NVD's CPE analysis and usually ahead of it.
Google Chrome
- 149.0.7827.115 and later · before 149.0.7827.115affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- google chromebefore 149.0.7827.115
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | chromium | before 149.0.7827.114-1~deb12u1 | 149.0.7827.114-1~deb12u1 |
| Debian:13 | chromium | before 149.0.7827.114-1~deb13u1 | 149.0.7827.114-1~deb13u1 |
| Debian:14 | chromium | before 149.0.7827.114-1 | 149.0.7827.114-1 |
| openSUSE:Tumbleweed | chromium | before 149.0.7827.114-1.1 | 149.0.7827.114-1.1 |
Same product
google: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-4863Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187 and libwebp 1.3.2 allowed a remote attacker to perform an out of…KEV95Now
- CVE-2021-21224Type confusion in V8 in Google Chrome prior to 90.0.4430.85 allowed a remote attacker to execute arbitrary code inside a sandbox via a…KEV90Now
- CVE-2018-17463Incorrect side effect annotation in V8 in Google Chrome prior to 70.0.3538.64 allowed a remote attacker to execute arbitrary code inside a…KEV90Now
Published before and after this one in the same product
- ← EarlierCVE-2026-12025Jun 11, 2026 · Insufficient validation of untrusted input in Network in Google Chrome prior to 149.0.7827.115 allowed a remote attacker who had…21Monitor
- ← EarlierCVE-2026-12026Jun 11, 2026 · Out of bounds read in Video in Google Chrome on ChromeOS prior to 149.0.7827.115 allowed a remote attacker who had compromised the renderer…26Monitor
- Later →CVE-2026-12028Jun 11, 2026 · Use after free in GPU in Google Chrome on Android prior to 149.0.7827.115 allowed a remote attacker who had compromised the renderer…33Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:chromium | 149.0.7827.114-1~deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:chromium | 149.0.7827.114-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-111677 days apartInappropriate implementation in WebView in Google Chrome on Android prior to 149.0.7827.53 allowed a remote attacker who had compromised…38Monitor
- CVE-2026-113342131 days apartPrivilege elevation in Network in Google Chrome prior to 156.0.8078.47 allowed a remote attacker leveraging social engineering to bypass…38Monitor
- CVE-2026-121234145 days apartPrivilege elevation in Contacts in Google Chrome on on Android prior to 157.0.8103.38 allowed a remote attacker to potentially execute…38Monitor
- CVE-2026-7601870 days apartPrivilege elevation in Import in Google Chrome prior to 151.0.7922.173 allowed a remote attacker leveraging social engineering to…35Monitor
- CVE-2026-113221131 days apartPrivilege elevation in Google Lens in Google Chrome prior to 156.0.8078.47 allowed a remote attacker who had compromised the renderer…35Monitor
- CVE-2026-8750689 days apartPrivilege elevation in WebUI in Google Chrome prior to 153.0.8010.36 allowed a remote attacker who had compromised the renderer process to…33Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-250 · Execution with Unnecessary PrivilegesCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.