BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-76039High confidence

Google Chrome: Use of Incorrectly-Resolved Name or Reference

Google · Chrome

6.5MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.32% for the current model date.

Compensating controls

  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Google Chrome and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-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.

4 package states
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 releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcechromiumVendor fix publishedDebian records a fixed source-package version for this release.151.0.7922.169-1~deb13u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcechromiumVendor fix publishedDebian records a fixed source-package version for this release.151.0.7922.169-1~deb12u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcechromiumVendor fix publishedDebian records a fixed source-package version for this release.151.0.7922.169-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcechromiumVendor fix publishedDebian records a fixed source-package version for this release.151.0.7922.169-1Debian Security Tracker ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative 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.

1 current
CVE-2026-76039 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitychromium-browser: Chromium: Information disclosure via incorrect reference resolution
1 known not affected

The vendor explicitly states that these products are not affected by this CVE.

  • All currently supported Red Hat products
Summary
A flaw was found in Chromium, specifically in its Core component on Android. This vulnerability, caused by incorrect reference resolution, allows a remote attacker to obtain sensitive information. By leveraging social engineering and a specially crafted HTML page, an attacker could exploit this flaw to disclose confidential data.
Remediation
No remediation text is recorded.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-61228

No EUVD known-exploited evidence

Incorrect reference resolution in Core in Google Chrome on on Android prior to 151.0.7922.169 allowed a remote attacker leveraging social engineering to obtain sensitive information via a crafted HTML page. (Chromium security severity: High)

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
6.5 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified
01

What, why and how

Incorrect reference resolution in Core in Google Chrome on on Android prior to 151.0.7922.169 allowed a remote attacker leveraging social engineering to obtain sensitive information via a crafted HTML page. (Chromium security severity: High)

What

Incorrect reference resolution in Core in Google Chrome on on Android prior to 151.0.7922.169 allowed a remote attacker leveraging social engineering to obtain sensitive information via a crafted HTML page. (Chromium security severity: High)

Why

The product uses a name or reference to access a resource, but the name/reference resolves to a resource that is outside of the intended control sphere.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may obtain information outside the intended access boundary.

What

Incorrect reference resolution in Core in Google Chrome on on Android prior to 151.0.7922.169 allowed a remote attacker leveraging social engineering to obtain sensitive information via a crafted HTML page. (Chromium security severity: High)

Why

The product uses a name or reference to access a resource, but the name/reference resolves to a resource that is outside of the intended control sphere.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may obtain information outside the intended access boundary.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Use of Incorrectly-Resolved Name or Reference → obtain information outside the intended access boundary
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-706 ↗

CWE-706: Use of Incorrectly-Resolved Name or Reference. The product uses a name or reference to access a resource, but the name/reference resolves to a resource that is outside of the intended control sphere.

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:N/A:N

Common 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.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-706
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-61228Official EUVD mapping

Incorrect reference resolution in Core in Google Chrome on on Android prior to 151.0.7922.169 allowed a remote attacker leveraging social engineering to obtain sensitive information via a crafted HTML page. (Chromium security severity: High)

Official EUVD record ↗
BSI · German · WID-SEC-2026-2908Google Chrome und Microsoft Edge: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Google Chrome und Microsoft Edge ausnutzen, um beliebigen Programmcode auszuführen, sensible Informationen offenzulegen, Sicherheitsmaßnahmen zu umgehen oder Denial-of-Service-Zustände zu verursachen.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1171Multiples vulnérabilités dans Microsoft Edge

ft Edge Date de la première version 14 septembre 2026 Date de la dernière version 14 septembre 2026 Source(s) Bulletin de sécurité Microsoft Edge CVE-2026-76017 du 11 septembre 2026 Bulletin de sécurité Microsoft Edge CVE-2026-76018 du 11 septembre 2026 Bulletin de sécurité Microsoft Edge CVE-2026-76019 du 11 septembre 2026 Bulletin de sécurité Microsoft Edge CVE-2026-76021 du 11 septembre 2026 Bulletin de sécurité Microsoft Edge CVE-2026-76022 du 11 septembre 2026 Bulletin de sécurité Microsoft Edge CVE-2026-76023 du 11 septembre 2026 Bulletin de sécurité Microsoft Edge CVE-2026-76036 du 11 septembre 2026 Bulletin de sécurité Microsoft Edge CVE-2026-76039 du 11 septembre 2026 Bulletin de sécurité Microsoft Edge CVE-2026-77490 du 11 septembre 2026 Bulletin de sécurité Microsoft Edge CVE-2026-84330 du 11 septembre 2026 Bulletin de sécurité Microsoft Edge CVE-2026-84333 du 11 septembre 2026 Bulletin de sécurité Microsoft Edge CVE-2026-84352 du 11 septembre 2026 Bulletin de sécurité Microsoft Edge CVE-2026-85042 du 11 septembre 2026 Bulletin de sécurité Microsoft Edge CVE-2026-85043 du 11 septembre 2026 Bulletin de sécurité Microsoft Edge CVE-2026-85045 du 11 septembre 2026 Bulletin de sécurité Microsoft Edge CVE-2026-85048 du 11 septembre 2026 Bulletin de sécurité Microsoft Edge CVE-2026-85049 d

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1045Multiples vulnérabilités dans Google Chrome

De multiples vulnérabilités ont été découvertes dans Google Chrome. Elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur.

Official advisory ↗
CSIRT Italia · Italian · risolte-vulnerabilita-in-google-chrome-68Risolte vulnerabilità in Google Chrome

Google ha rilasciato un aggiornamento per il browser Chrome al fine di correggere 15 nuove vulnerabilità di sicurezza, di cui 2 con gravità “critica” e 13 con gravità “alta”.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-029610GoogleのGoogle Chromeにおける誤って解決された名前や参照の使用に関する脆弱性

151.0.7922.169より前のAndroid版Google ChromeのCoreにおける不正な参照解決により、リモートの攻撃者がソーシャルエンジニアリングを悪用して、細工されたHTMLページを通じて機密情報を取得できる可能性がありました。(Chromiumのセキュリティ重大度は高いです)

Official advisory ↗
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.
Fix not verified
Affected
Chrome: 151.0.7922.169 < 151.0.7922.169
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
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 Tuesday, August 18, 2026 The Stable channel has been updated to 151.0.7922.169/.170 for Windows and Mac and 151.0.7922.169 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 18 Aug 2026 · Last source change 19 Aug 2026, 11:26 UTC · CWE-706 · Use of Incorrectly-Resolved Name or Reference

CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-23
European sourceENISA EUVD · EUVD-2026-61228
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: chromereleases.googleblog.com/stable-channel-update-for-desktop_0826575033.html; added vendor advisory: issues.chromium.org/525167753.
    Before
    no authoritative guidance recorded
    After
    vendor advisory: chromereleases.googleblog.com/stable-channel-update-for-desktop_0826575033.html · vendor advisory: issues.chromium.org/525167753
    chrome-cve-admin@google.com ↗
  2. SeveritySeverity changed from Unknown to Medium.
    Before
    Unknown
    After
    Medium
    CISA ADP ↗
  3. CVSS scoreCVSS score changed from not recorded to 6.5 (CVSS 3.1 · CISA ADP · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N).
    Before
    not recorded
    After
    6.5 (CVSS 3.1 · CISA ADP · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N)
    CISA ADP ↗
  4. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
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.
Free version - for non-commercial use only.CVE-2026-76039 · cve.blacktree.nl