basicsecurity.net
Proof, not just disclosure.
Threats / Google / CVE-2025-14174
CVE-2025-14174 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Google Chromium vulnerability

Out of bounds memory access vulnerability in Chromium's ANGLE graphics library allows remote attackers to trigger memory corruption via crafted HTML pages.

Verdict

Today item — known-exploited.

Remote attackers can exploit this vulnerability by hosting or distributing malicious HTML content that triggers out of bounds memory access in ANGLE, potentially leading to crashes, information disclosure, or code execution in affected Chromium-based browsers.

CISA KEV Yes · 2025-12-123EPSS 0.22216 (verify live)4Exploit Public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
10 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-12-12).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.22216 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Google, Chromium. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
Craft and host malicious HTML that triggers out of bounds memory access in ANGLE graphics processing
Business
Users visiting compromised or attacker-controlled websites experience browser crashes or potential code execution
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
Distribute the malicious HTML through phishing, watering hole attacks, or compromised legitimate websites
Business
Widespread user exposure across Chrome, Edge, Opera and other Chromium-based browsers creates support burden and reputation damage
3

Lateral reach — past segmentation narrative 3

Attacker
Leverage memory corruption to read sensitive data from browser memory or escalate to arbitrary code execution
Business
Potential data theft, credential compromise, or malware installation affecting user systems and organizational security
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Public PoC available (VulnCheck)
  • 10 reported-exploitation source(s)
  • Public exploit availability
  • Catalogued by Chrome (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by ChromeCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.