Skip to main content
Type Vulnerability

Google

Access Control Flaw in V8 in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to read memory via a crafted HTML page

1 sourceCVE-2026-118318

At a glance

Low
30-day window, from the last update
None observed
Evidence-weighted, not popularity
Why Low

Low rather than Medium: UK relevance is 40 of 100, little UK-specific signal so far.

Briefing

  • Do not treat uncorroborated claims as confirmed breaches.

Questions to ask IT

  • Do we run Google Chrome and Microsoft Edge, and is every instance on version 156.0.8078.73 or later?
  • If it is not yet patched, what mitigation is in place, and will the fix be done by 30 Nov?

Next steps

  1. Confirm whether this affects systems or suppliers in your estate

Summary

  • Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information.

Read the original reportMicrosoft Security Update Guide RSS(opens in a new tab)

Products and services involved

Pulse

Last change 31 Oct · Recheck overdue since 1 Nov 2026, 18:24 UK time

  1. Story31 Oct 2026, 18:24 UK time · 31 Oct

    Linked reporting from Microsoft Security Update Guide RSS (vendor psirt).

    Read source (Microsoft Security Update Guide RSS)

1 entry so far. The timeline chart appears once this story has more history.

Sources

How we know

Statements extracted from sources. Higher confidence means stronger corroboration.

  • ClaimedHeadline60% confidence

    Improper access control in V8 in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to read memory via a crafted HTML page

  • ProbableSummary fact75% confidence

    Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see [Google Chrome Releases](https://chromereleases.googleblog.com/2026) for more information.

  • ConfirmedCVE identifier95% confidence

    Event involves CVE-2026-118318