Threats / Google / CVE-2026-85046

CVE-2026-85046 · EUVD no mirror located · GCVE no mirror located Verified 2026-09-07

Google Chromium V8 vulnerability

Google Chromium V8 contains a type confusion vulnerability that allows a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, incl

Verdict

Today item — known-exploited.

Confirmed exploited in the wild (CISA KEV). Prioritize remediation now and verify exposure.

CISA KEV Yes · 2026-09-04⁵EPSS 0.01162 (verify live)⁶Exploit Public PoC⁷CVSS 8.8 (CISA)⁴CISA SSVC Exploitation: active · Automatable: no · Impact: total⁴

Is it exploitable?

— the evidence, ranked above the score

Exploit available

Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.

vulncheck.com ↗Confirmed

Reported exploitation

4 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.

chromereleases.googleblo ↗euvd.enisa.europa.eu ↗previdian.com ↗cisa.gov ↗Confirmed

Exploited in the wild

Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-09-04).

CISA KEV ↗Confirmed

Probability (EPSS)

EPSS 0.01162 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.

FIRST EPSS ↗High

Severity / affected

CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) · Affected: Google, Chromium V8. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.

CISA-ADP ↗Reported

Weakness (CWE)

Mapped to CWE-843 Type Confusion — weakness family: Memory safety.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.

CVE.org ↗Reported

CISA SSVC (triage disposition)

Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.

CISA-ADP ↗Reported

Currency of the record

CISA added this to its KEV catalog 1 day after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.

CISA KEV ↗CVE.org ↗Reported

WeaknessCWE-843 · Type ConfusionMemory safety

Who’s exploiting it?

— attribution turns risk into urgency

Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

Why it matters

— the attack path, told twice: adversary, then board

Attacker/business narrative framing is pending triage for this record — see Coverage & confidence below. Facts and verdict above are derived deterministically from the public feed.

What to do

— defensible action

Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.¹

Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.

Coverage & confidence

— what we know, and what we don’t

Established (cited)

KEV listing (CISA)

EPSS probability (FIRST)

Public PoC available (VulnCheck)

4 reported-exploitation source(s)

CVSS 8.8 — CISA-assigned (CVE.org ADP)

CISA SSVC triage disposition (CVE.org ADP)

CWE weakness mapping — CNA-assigned (CVE.org)

Public exploit availability

Catalogued by Chrome (CNA)

Coverage gaps — stated, not hidden

No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.

EPSS & exposure are time-varying; verify live at the source.

Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.

No finder is named in the public CVE record — attribution scoped to the sources checked.

Attacker/business narrative framing pending triage.

Disclosure & credit²

Catalogued by ChromeCNA

Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.

Found an error? Propose a correction.

A correction is a cited counter-claim — it must cite a source, gets reviewed by a second human, and is never auto-applied. See the correction convention and our identity npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.

With JavaScript off: publish a signed kind 1111 Nostr event tagging ["r", "https://basicsecurity.net/threat/cve-2026-85046.html"], ["v", "sha256:a793b082f36a1256a807885777875603e7243f5d85add6b0e6c1b94979414cbd"] (the record version), plus ["src", "<your source URL>"] and ["t", "correction"], per the correction convention. Our identity: npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y. Cite-or-die: an event with no src is a coverage finding, not a proposal.