Home › Intelligence › Brief
VULNERABILITY BRIEF 🟠 High Vulnerability

Out-of-Bounds Memory Access Vulnerability in Chromium (CVE-2025-14174) Affects Chrome, Edge, Opera

Chromium’s ANGLE graphics library contains an out‑of‑bounds memory‑access bug (CVE‑2025‑14174) that can be exploited through a crafted HTML page. The flaw impacts all browsers built on Chromium, including Chrome, Edge, and Opera, and requires prompt patching to maintain audit‑ready evidence of a secure environment.

Verisq™ Intelligence · 📅 October 07, 2026 · 📰 nvd.nist.gov
🟠
Severity
High
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
2 sector(s)
✅
Actions
5 recommended
📰
Source
nvd.nist.gov

Out-of-Bounds Memory Access Vulnerability in Chromium (CVE-2025-14174) Impacts Chrome, Edge, Opera

What It Is – Chromium’s ANGLE graphics library contains an out‑of‑bounds memory‑access flaw that can be triggered by a malicious HTML page. Successful exploitation allows a remote attacker to read or corrupt memory in the browser process.

Exploitability – The vulnerability is remotely exploitable via crafted web content; proof‑of‑concept code has been published. CVSS v3.1 is rated 7.5 (High).

Affected Products – Google Chrome, Microsoft Edge, Opera and any other browser built on the Chromium engine.

Why It Matters for Trust & Control Assurance

  • Patch management is a core control; timely remediation demonstrates due‑diligence and provides audit‑ready evidence of a defended environment.
  • Continuous monitoring of software versions and vulnerability feeds supplies defensible proof that the organization tracks and mitigates emerging risks.
  • Demonstrating a documented remediation workflow satisfies control objectives around change management and security testing, which many enterprise buyers now require as part of a trust posture.

Recommended Actions

  1. Verify the current Chromium version across all endpoints and compare against the vendor‑released patch for CVE‑2025‑14174.
  2. Deploy the patch through your centralized update mechanism; capture deployment logs as evidence of control execution.
  3. Update your vulnerability‑management dashboard to flag this CVE and map it to the “software patching” control area.
  4. Conduct a post‑patch validation scan to confirm the flaw is mitigated and record the results for audit purposes.

Source: CISA KEV – CVE‑2025‑14174

📰 Original Source
https://nvd.nist.gov/vuln/detail/CVE-2025-14174 ↗

This Verisq Intelligence Brief is an independent analysis. Read the original reporting at the link above.

Vulnerability exposure

Is this CVE in your supply chain?

Verisq matches published vulnerabilities against the software your vendors run, so you know which relationships this touches before the next review.

See vendor exposure →