Skip to content
major vulnerability· requires attention

Chrome is widely used; this info‑disclosure in Chrome on macOS can expose sensitive data via crafted pages and warrants org‑wide attention.

Web

CVE-2026-106274

8.8
High
EPSS 0.28%Patch availableOct 9, 2026

Chrome on macOS info‑disclosure via crafted HTML allows data exposure.

common questions

Is CVE-2026-106274 being exploited?

Not confirmed. CVE-2026-106274 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.28% probability of exploitation in the next 30 days.

How severe is CVE-2026-106274?

CVE-2026-106274 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-106274?

Yes. A fix has been recorded for CVE-2026-106274. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-106274 affect?

CVE-2026-106274 affects Google Chrome < 155.0.8059.39 on macOS. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-106274?

Upgrade Chrome on macOS to 155.0.8059.39+ immediately; caution users about unsolicited links.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Google Chrome < 155.0.8059.39 on macOS
impact

Remote information disclosure via a crafted HTML page (social engineering) allowing attackers to obtain sensitive user data.

action required

Patch when possible

affected versions
Google Chrome
  • affected< 155.0.8059.39

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free