Google Chrome

Not in CISA KEVCVE-2026-118306CWE-119

Not confirmed exploited. No WAF vendor names it yet.

Edge rules

0/8

Our test

No exploit yet

CVSS

9.6

EPSS

0.4% Top 69%

Posts, 14d

Published

2026-10-27

Memory corruption in FileSystem in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical)

Edge coverage

Claimed by vendors

CloudflareNo public claimNot named AWSNo public claimNot named Microsoft AzureNo public claimNot named Google CloudNo public claimNot named FastlyNo public claimNot named F5No public claimNot named AkamaiNo public sourceNo public changelog OWASP CRSNo public claimNot named

Ask Vigil

AI · answers from this page

Ask about CVE-2026-118306: who's covered, what to patch first, how vendors compare. I cite sources and won't help with attacks.

Workers AI (Llama 3.3). Can be wrong: check the cited source.

Severity, decoded

CVSS 3.1

9.6Critical

Critical · 9.6 / 10

Exploitable over the network, with no privileges and user interaction, leading to full loss of confidentiality, integrity and availability, and the impact can reach components beyond the vulnerable one.

Over the internetNo login neededNeeds a user to actWorks reliablySpreads beyond the appFull compromise

How the score is built8 metrics

Attack vectorAn attacker can reach it over the internet; no access to your network needed.
Network
Attack complexityNo special conditions are needed; the attack works reliably.
Low
Privileges requiredNo account or login is needed.
None
User interactionA user has to do something first, such as open a file or click a link.
Required
ScopeThe attack can spread beyond the vulnerable component to other parts of the system.
Changed
Confidentiality impactAn attacker can read all data the affected component holds, or the most sensitive parts of it.
High
Integrity impactAn attacker can change any data or files the affected component protects.
High
Availability impactAn attacker can take the component down completely or keep it from serving anyone.
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

CISA's assessmentSSVC, from the CVE record

ExploitationNone

CISA has seen no public exploit and no attacks.

AutomatableNo

At least one step needs hands-on work, which slows mass attacks.

Technical impactTotal

A successful attack gives full control over the affected software or all of its data.

Public exploits

None found

0 Metasploit0 Exploit-DB0 Scanner template0 GitHub PoCs

No exploit in Exploit-DB or Metasploit, and no scanner template. That lowers, but doesn't remove, the chance of mass exploitation.

Timeline

2026-10-27
CVE published
CVE List
2026-11-02
First social mention we saw

Vendor statements

Quoted

CloudflareWAF Managed RulesNo public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Each row gives the rule ID and its default action. The feed starts in January 2025, so older rules are missing.

AWSAWS WAF Managed RulesNo public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. AWS often describes a vulnerability without naming its CVE (for example "Log4j"). We count only entries that name the CVE, so AWS coverage is understated.

Microsoft AzureFront Door and Application Gateway WAF (DRS)No public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. The rule tables name CVEs but carry no dates, so Azure is left out of every time-to-rule figure.

Google CloudCloud Armor preconfigured WAF rulesNo public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Google names few CVEs: the release notes start in May 2024 and the rules reference lists CVEs without dates. Its cve-canary rules are opt-in.

FastlyNext-Gen WAF virtual patchesNo public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. The feed holds only the latest 25 changes, so history builds up from the day we started reading it.

F5Attack signatures (Distributed Cloud WAF)No public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Each signature lists the CVEs it references, with its id and date. F5 does not state a default action; signatures enforce once staging ends in your policy.

AkamaiApp & API Protector (Adaptive Security Engine)No public source

This vendor publishes no machine-readable rule changelog we can check.

OWASP CRSCore Rule Set (open source, used inside many WAFs)No public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. CRS rarely names CVEs: it relies on generic detections. Our own lab measures what it actually blocks.

Is your site covered?

We find your CDN or WAF in public DNS and match it to this CVE. Nothing is sent to your site.

Vigilbase OS

Know the day a CVE like this reaches your stack.

Connects the security tools you already pay for. Vigil investigates, makes the fixes you authorise and verifies them.

Get started

Our lab test

Measured

Nothing to replay yet

No public exploit request exists for it yet. Flaws in kernels, libraries or VPN clients can't be reached through a WAF at all.

We'll test it within a minute of a template appearing in nuclei-templates.

Watching for templates · checked just now4,450 CVEs tested

Exposure

Estimates

No website count: Chrome isn't web software we can count from the outside.

0.37%chance of exploitation in 30 days

FIRST EPSS, updated daily. Top 69% of all CVEs by this score.

For agents

$ curl https://cve.vigilbase.com/api/v1/cves/CVE-2026-118306

MCP server Markdown CVE.org NVD