Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-84327Published 2026-09-01

CVE-2026-84327 — Google Chrome

medium

As of 2026-09-08, CVE-2026-84327 is a MEDIUM-severity vulnerability in Google Chrome, CVSS v3.1 6.5, EPSS 0.3% (21.5th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-84327, most recently “Microsoft September 2026 Patch Tuesday — 999 CVEs, 3 actively exploited zero-days (CVE-2026-85880, CVE-2026-81963, CVE-2026-85046)”.

CVSS v3.1
6.5/10Medium
EPSS
0.3%Higher than 21.5% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
1Campaigns referencing it
Priority
4.1/10Threadlinqs triage score
Published
Updated 2026-09-08
CVSS v3.1 6.5 (MEDIUM) · EPSS 0.3% (higher than 21.5% of all scored CVEs) · Priority 4.1/10 · Published 2026-09-01

Last updated:

What is CVE-2026-84327?

Incorrect authorization in Autofill in Google Chrome on on Android prior to 152.0.7977.75 allowed a remote attacker leveraging social engineering to obtain sensitive information via a crafted HTML page. (Chromium security severity: Low)

The record classifies CVE-2026-84327 under weakness class CWE-863. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs a user to take an action first, and has high impact on confidentiality. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 79 days ago.

Severity and exploitation probability

CVSS v3.1 base score
6.5 — MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
EPSS (FIRST)
0.3% probability of exploitation in the next 30 days, higher than 21.5% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
4.1/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-09-01

Is CVE-2026-84327 being exploited?

It currently carries a trending score of 31 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-84327

Vendor advisory: https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop.html. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2026-84327

1 tracked threat in the Threadlinqs corpus references CVE-2026-84327, either in the campaign’s CVE list or as an indicator on the campaign record.

    Sources

    Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories. This product uses the NVD API but is not endorsed or certified by the NVD.

    Other references