LowCVE-2026-106339

Google Chrome: Operation on a Resource after Expiration or Release (CVE-2026-106339)

Published 06.10.2026Last modified 07.10.2026Sources: HKCERT, Debian LTS, Debian, BSI, Msrc Update Guide, CVE.org

What is affected, what to do

Use of released resource in Core in Google Chrome prior to 155.0.8059.39 allowed a remote attacker who had compromised the renderer process to potentially obtain cross-origin data via a crafted HTML page. (Chromium security severity: Low)

The available sources name no fixed version. Check the vendor guidance in the references below.

Conflicting version data — version display is hidden until the data is resolved.

Not sure whether and how you are affected? Ask a question about this vulnerability

Metrics

3.1

Priority

XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

Source: Vendor (CNA), CVSS v3

3.1

CVSS v3

Severity Low on the scale from 0 to 10.

Source: HKCERT, Debian LTS, Debian, BSI, Msrc Update Guide, CVE.org

0.2 %

EPSS score

Low — model estimates < 1% exploitation likelihood.

Source: FIRST EPSS, percentile 7.8

Show all metrics

Severity: Low
Priority (0–325) The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first? Read in glossary: 45.99 Methodology
Exploit maturity An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack. Read in glossary: no public PoC known
XIEM Effective CVSS XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command. Read in glossary: 3.1 Methodology
CVSS v3 CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions. Read in glossary: 3.1
EPSS score The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“. Read in glossary: 0.2 %; Low — model estimates < 1% exploitation likelihood.
EPSS percentile The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking. Read in glossary: 7.8; Low — this CVE sits in the lower 10% of all CVEs scored today.
KEV status The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching. Read in glossary: —
Published: 06.10.2026
CWE CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect. Read in glossary: CWE-672

Detection rules

No NEOSEC detection rule is available for this vulnerability yet.

Classification under NIS2 and CRA

Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

NIS2 NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management. Read in glossary: Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates. Read in glossary: From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001 ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security. Read in glossary: Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

Description

Source: HKCERT (CC BY 3.0 HK) · HKCERT rating: medium, Debian LTS Advisories, Debian Security Advisories, BSI WID Portal, BSI CSAF, Microsoft Security Update Guide, NVD (NIST), cvelistv5

Affected products

The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

Affected products
		Affected versions	Fixed in
Google	Chrome	`< 155.0.8059.39` `< 155.0.8059.39` `< 155.0.8059.40`	`155.0.8059.39` `155.0.8059.39` `155.0.8059.40`
google	chrome	`< 155.0.8059.39`	`155.0.8059.39`

Vendors and products

Affected operating systems

Affected operating systems

Linux	debian	chromium	`bookworm`
Linux	debian	chromium	`trixie`

Weakness classes (CWE)

CWE-672Operation on a Resource after Expiration or Release
Class
The product uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked.
Entry at MITRE CWE-672

References & sources

chromereleases.googleblog.com2026/10/stable-channel-update-for-desktop_086471744.html
issues.chromium.orgissues/553913506

Changes to this CVE

Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

07.10.2026Initial analysis by NVDNVD

Newly listed as affected:

Google Chrome (before 155.0.8059.39)

New references:

Show 3 original changes

Individual changes of this event as published by NVD
Type	Action	Before	After
Product configuration	added	—	OR cpe:2.3:a:google:chrome::::::::* versions up to (excluding) 155.0.8059.39
Reference type	added	—	Chrome: https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_086471744.html Types: Release Notes, Vendor Advisory
Reference type	added	—	Chrome: https://issues.chromium.org/issues/553913506 Types: Permissions Required

Source identifier: nvd@nist.gov

07.10.2026Record modifiedCISA ADP

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

CISA assessment (SSVC): exploitation: none known, automatable: no

Show 2 original changes

Individual changes of this event as published by NVD
Type	Action	Before	After
CVSS	added	—	AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
SSVC assessment	added	—	{"id":"CVE-2026-106339","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-10-07T10:07:21.704675Z"}

Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

06.10.2026ReceivedGoogle Chrome

Weakness type: CWE-672

Description added or changed

New references:

Show 5 original changes

Individual changes of this event as published by NVD
Type	Action	Before	After
Description	added	—	Use of released resource in Core in Google Chrome prior to 155.0.8059.39 allowed a remote attacker who had compromised the renderer process to potentially obtain cross-origin data via a crafted HTML page. (Chromium security severity: Low)
Weakness type (CWE)	added	—	CWE-672
Affected versions (publisher)	added	—	New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/106xxx/CVE-2026-106339.json">CVE-2026-106339</a>
Reference	added	—	https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_086471744.html
Reference	added	—	https://issues.chromium.org/issues/553913506

Source identifier: chrome-cve-admin@google.com

Embed badge

Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

<a href="https://intel.neosec.eu/en/cve/CVE-2026-106339"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-106339.svg?lang=en" alt="CVE-2026-106339 – NEOSEC Intel" height="20"></a>