What is CVE-2026-85046?

CVE-2026-85046 is Google Chromium V8 Type Confusion Vulnerability. The supplied enrichment data classifies it as Memory Corruption mapped to CWE-843 Type Confusion.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

7 public PoC repositories reported; 1 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-85046 using CVSS 8.8, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVhighMemory Corruptionpublic exploit

CVE-2026-85046

CVE-2026-85046 — Google Chromium V8 Type Confusion Vulnerability

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2026-85046 in CISA KEV with required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Type confusion in V8 in Google Chrome prior to 152.0.7977.82 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)

Published Sep 3, 2026Updated Sep 4, 2026Sources: NVD, Google (CNA), CISA, FIRST EPSS, GitHub, GitHub Security Advisory, Red Hat (VEX), SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Sep 4, 2026

EPSS

ahead of 38% of scored CVEs

Affects

Google

Chrome

CVSS base

8.8

high

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade Chrome to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Federal deadline Sep 18, 2026 — in 13 days

Red Hat VEX · CVE-2026-85046

fixed0affected0not affected1

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Google	Chrome	152.0.7977.82 to < 152.0.7977.82	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

Required

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
8.8	CVSS 3.1	high	2.8	5.9	CNA, GHSA, Red Hat (VEX)

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-843 · Access of Resource Using Incompatible Type ('Type Confusion')

Read Memory
Modify Memory
Execute Unauthorized Code or Commands
DoS: Crash, Exit, or Restart

Weakness & attack patterns

CWE-843Type Confusion

Inferred from the weakness class — not observed against this CVE.

CAPEC-100 · Overflow BuffersCAPEC-123 · Buffer Manipulation

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Sep 4, 2026

Federal deadline

Sep 18, 2026

in 13 days

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

1 of the 5 sampled are weaponized

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable Chrome.
Monitor for scanner or exploit-pattern traffic after 7 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added to CISA KEV catalog
Sep 4, 2026 · CISA
Added · CVSS 3.1 8.8 (AV:N)
Sep 4, 2026 · NVD
Initial · CVE published
Sep 3, 2026 · NVD
Added · GHSA-84qv-4wj5-wwmm published (high)
Sep 3, 2026 · GitHub Security Advisory
CVE published by MITRE.
Sep 3, 2026 · SOCRadar CTI

Source activity

Readings a source repeats on a schedule, counted rather than listed.

2×SvrsSep 4, 2026 · SOCRadar CTI
2×Github ReposSep 4, 2026 · SOCRadar CTI
1×Tweets · 4 times tweeted.Sep 4, 2026 · SOCRadar CTI
1×CVE appeared in the Cve Trends.Sep 4, 2026 · SOCRadar CTI
1×4 times mentioned on 3 Telegram channelsSep 4, 2026 · SOCRadar CTI

References

9 on the record

chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_01882797386.html
Release Notes, Vendor Advisory, NIST
issues.chromium.org/issues/542403045
Permissions Required, NIST
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-85046
US Government Resource, NIST
nvd.nist.gov/vuln/detail/CVE-2026-85046
NVD, Vendor Advisory
github.com/advisories/GHSA-84qv-4wj5-wwmm
Exploit, Third Party Advisory
access.redhat.com/security/cve/CVE-2026-85046
Vendor Advisory
www.cve.org/CVERecord?id=CVE-2026-85046
Vendor Advisory
www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
US Government Resource

Coverage

2 stories from the feeds we poll

Elsewhere on this site

Googleevery CVE for this vendor
September 2026what else CISA listed
Memory Corruptionsame class
CWE-843other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-85046 is Google Chromium V8 Type Confusion Vulnerability, a high vulnerability affecting Chrome from Google. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 7 public PoC repositories reported; 1 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 8.8 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.