Skip to content

ApplicationsHigh 8.3Patch available

CVE-2026-131000

Chrome sandbox-escape RCE via WebAppInstalls input validation bug.

How scary is it?

updated 18 Nov 2026
  • Yes

    Works without logging in1

    No account needed, but a person has to act, such as opening a link or a file (CVSS PR:N, UI:R).

  • Yes

    Reachable over the network1

    Can be attacked remotely (CVSS AV:N).

  • None known

    Public exploit code is out

    None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.

  • None known

    Attacks seen in the wild1

    None reported that we know of. CISA's SSVC assessment says exploitation: none.

  • No

    On CISA's exploited list2

    Not in the catalog as of our last sync.

Scare-o-meter

Routine patch

Serious on paper, with no sign of attacks that we know of. Patch in your normal cycle.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: our alert rule found no exploitation evidence and no easy remote attack path in the data we hold. Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. You run Google Chrome in an affected version< 158.0.8127.36

    The CVE record states no fixed release.

    As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.

    See the affected products table · Source 1

  2. An attacker can reach it over the network

    CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.

    Source 1

  3. A person takes an action, such as opening a link or a file

    CVSS user interaction: required (UI:R). A victim must click, open or otherwise cooperate.

    Source 1

  4. Specific conditions are met that the attacker does not control

    CVSS attack complexity: High (AC:H). Needs specific conditions, a race or a particular configuration. The CVE record does not always say which.

    Source 1

Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.

What to do

  1. Per our analysisA patch is available

    The CVE record we hold states no fixed release number. See the advisories in the references.

    See the references

  2. Recommendation, AI-writtenUpdate Chrome to 158.0.8127.36 or later immediately across endpoints.

    Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.

Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.

Major vulnerability. Chrome is widely deployed; a sandbox-escape RCE can lead to host compromise across enterprises and should be broadly communicated.

CVSS
8.3Highscored by CISA
Exploited in the wild
Not knownnot in CISA KEV as of our last sync
EPSS
0.39%chance of exploitation in the next 30 daystop 67% of scored CVEsFIRST score of 21 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
17 Nov 2026analysed here 18 Nov 2026

Summary

Impact

An attacker who controls the renderer can use crafted HTML to execute arbitrary code outside Chrome's sandbox, enabling host compromise.

Triage

Exploitable
At runtime
Attack vector
network
Weakness
  • CWE-20 Improper Input Validation
Can a WAF block it?
Partly. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
Google Chrome< 158.0.8127.36Vendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • Google Chrome (desktop) <158.0.8127.36
  • Chromium-based builds

Fix and mitigation

Action required

Immediate action required

WAF and other mitigations

Can a WAF block it? Partly. The bug can be reached over the network, so generic WAF rules may stop some attacks. Its weakness type is unknown, so we cannot be more precise.

Also consider: patch

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
CISA SSVC
exploitation none, automatable no, technical impact totalAssessed by CISA 17 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Timeline

  1. 17 Nov 2026CISA SSVC assessment: exploitation none
  2. 17 Nov 2026Published1 day later
  3. 18 Nov 2026CVE record last updatedsame day later
  4. 18 Nov 2026Analysed by vulneraibility.comsame day later

Common questions

Is CVE-2026-131000 being exploited?

Not confirmed. CVE-2026-131000 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.39% probability of exploitation in the next 30 days.

How severe is CVE-2026-131000?

CVE-2026-131000 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-131000?

Yes. A fix has been recorded for CVE-2026-131000. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-131000 affect?

CVE-2026-131000 affects Google Chrome (desktop) <158.0.8127.36, Chromium-based builds. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-131000?

Update Chrome to 158.0.8127.36 or later immediately across endpoints.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

2 references in the CVE record, grouped by the tags the record gives them.

Other links (2)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.