Evidence used
- CISA confirms exploitation in the wild.
- A structured source references public exploit or proof-of-concept material.
- EPSS is 48.88% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-85046High confidence
Google Chromium V8 Type Confusion Vulnerability
Google · Chromium V8
8.8HighCVSS 3.1
Patch now
Patch availableCISA confirms exploitation in the wild and lists 2026-09-18 as the remediation due date.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:Critical, raised one band.upgradedsince 4 Sep 2026
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
- Confirm that the asset runs Google Chromium V8 and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
4 package statesRelease-specific package status
Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | chromium | Vendor fix publishedDebian records a fixed source-package version for this release. | 152.0.7977.82-1~deb13u1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian bookwormbookworm · source | chromium | Vendor fix publishedDebian records a fixed source-package version for this release. | 152.0.7977.82-1~deb12u1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian forkyforky · source | chromium | Vendor fix publishedDebian records a fixed source-package version for this release. | 152.0.7977.82-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian sidsid · source | chromium | Vendor fix publishedDebian records a fixed source-package version for this release. | 152.0.7977.82-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-85046 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitychromium-browser: chromium-browser: Type confusion in V8
The vendor explicitly states that these products are not affected by this CVE.
- All currently supported Red Hat products
- Summary
- A type confusion flaw was found in the V8 component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=542403045
- Remediation
- No remediation text is recorded.
CISA confirms exploitation in the wild and lists 2026-09-18 as the remediation due date.
Patch available01
What, why and how
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, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.
What
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, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.
Why
The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.
How
An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may execute code or commands in the affected security context.
What
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, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.
Why
The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.
How
An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may execute code or commands in the affected security context.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation Confirmed in the wild
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.CISA added this CVE to its Known Exploited Vulnerabilities catalogue on 2026-09-04.
Public PoC / exploit material Reference recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.
- Likely attack path
- a network path → Access of Resource Using Incompatible Type ('Type Confusion') → execute code or commands in the affected security context
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- Required interaction required
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-843 ↗
CWE-843: Access of Resource Using Incompatible Type ('Type Confusion'). The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Action
- Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
Official vendor articles1 stored document
Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.
- Chrome Releases: Stable Channel Update for Desktop →Original publisher ↗Searchable text snapshot · Captured 26 Sep 2026Chrome Releases Release updates from the Chrome team Stable Channel Update for Desktop Thursday, September 3, 2026 The Stable channel has been updated to 152.0.7977.82/.83 for Windows and Mac and 152.0.7977.82 for Linux, which will roll out over the coming days/weeks. A full list of changes in this build is available i
04
Evidence and provenance
Published 3 Sept 2026 · Last source change 21 Sept 2026, 12:53 UTC · CWE-843 · Access of Resource Using Incompatible Type ('Type Confusion')
CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source FIRST · tracked since 2026-09-04
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-70702
Product sourceCISA KEV
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- BlackTree coverageBlackTree article coverage changed from 2 BlackTree articles to 3 BlackTree articles.BlackTree editorial ↗
- Before
- 2 BlackTree articles
- After
- 3 BlackTree articles
- BlackTree coverageBlackTree article coverage changed from 1 BlackTree article to 2 BlackTree articles.BlackTree editorial ↗
- Before
- 1 BlackTree article
- After
- 2 BlackTree articles
- BlackTree coverageBlackTree article coverage changed from 1 BlackTree article to 1 BlackTree article.BlackTree editorial ↗
- Before
- 1 BlackTree article
- After
- 1 BlackTree article
- BlackTree coverageBlackTree article coverage changed from no BlackTree article to 1 BlackTree article.BlackTree editorial ↗
- Before
- no BlackTree article
- After
- 1 BlackTree article
- ENISA known-exploited stateENISA EUVD now records this CVE in its known-exploited dataset.ENISA EUVD ↗
- Before
- not listed in ENISA EUVD known-exploited dataset
- After
- listed in ENISA EUVD known-exploited dataset (EUVD-2026-70702)
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 152.0.7977.82 < 152.0.7977.82 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- After
- Chrome: 152.0.7977.82 < 152.0.7977.82 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- Vendor guidanceAuthoritative vendor guidance changed: added patch: github.com/e0562d87ad9c17042b581582c99237d798572e67; added remediation: github.com/e0562d87ad9c17042b581582c99237d798572e67.chrome-cve-admin@google.com ↗
- Before
- vendor advisory: chromereleases.googleblog.com/stable-channel-update-for-desktop_01882797386.html
- After
- patch: github.com/e0562d87ad9c17042b581582c99237d798572e67 · remediation: github.com/e0562d87ad9c17042b581582c99237d798572e67 · vendor advisory: chromereleases.googleblog.com/stable-channel-update-for-desktop_01882797386.html
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 152.0.7977.82 < 152.0.7977.82 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- 152.0.7977.82 < 152.0.7977.82 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- Remediation statusRemediation status changed from Awaiting fix to Patch available.chrome-cve-admin@google.com ↗
- Before
- Awaiting fix
- After
- Patch available
- Public exploit evidencePublic exploit evidence changed from No public exploit to Public exploit reference.serotav.github.io ↗
- Before
- No public exploit
- After
- Public exploit reference
- Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: chromereleases.googleblog.com/stable-channel-update-for-desktop_01882797386.html.chrome-cve-admin@google.com ↗
- Before
- no authoritative guidance recorded
- After
- vendor advisory: chromereleases.googleblog.com/stable-channel-update-for-desktop_01882797386.html
- ENISA EUVD mappingEUVD-2026-70702 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2026-70702"}
- CISA KEV stateCISA KEV now confirms exploitation in the wild.CISA KEV ↗
- Before
- not listed in CISA KEV
- After
- listed in CISA KEV since 2026-09-04
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
CVE published
Added to CISA KEV
Fixed release or patch reference recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.