# CVE-2025-14174: Google Chromium Out of Bounds Memory Access

> A remote attacker can trigger out-of-bounds memory access in Chrome on Mac via a crafted HTML page, potentially leading to code execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 12 Dec 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Dec 2025
- **Updated:** 21 Sep 2026
- **Also known as:** DEBIAN-CVE-2025-14174, GHSA-9fjm-6w64-76r7, UBUNTU-CVE-2025-14174

## What is CVE-2025-14174?

CVE-2025-14174 is a high-severity memory corruption vulnerability in Apple Ipados, published on 12 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Out of bounds memory access in ANGLE in Google Chrome on Mac prior to 143.0.7499.110 allowed a remote attacker to perform out of bounds memory access via a crafted HTML page. (Chromium security severity: High)

Weakness: CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2025-14174?

It affects 9 products.


Products: Apple Ipados, Apple Iphone Os, Apple Macos, Apple Safari, Apple Tvos, Apple Visionos, Apple Watchos, Google Chrome, Microsoft Edge Chromium.

## How do I fix CVE-2025-14174?

Upgrade to a fixed version. US federal agencies must fix it by 2 Jan 2026.

## Is CVE-2025-14174 being exploited?

Yes. Attackers have exploited CVE-2025-14174 in the wild since at least 12 Dec 2025.

Public exploit code:

- Proof-of-Concept exploit for CVE-2025-14174 (EUVD-2025-203113) - Memory corruption in ANGLE allowing out-of-bounds access and RCE in web browsers. Reliable on iOS/Android/Windows, including patched systems with incomplete fixes. (github_poc): https://github.com/Satirush/CVE-2025-14174-Poc
- Analysis and PoC for CVE-2025-14174 - ANGLE Metal OOB write (iOS Safari, macOS Chrome) (github_poc): https://github.com/typeconfused/CVE-2025-14174-analysis
- https://github.com/George0Papasotiriou/CVE-2025-14174-Chrome-Zero-Day (github_poc): https://github.com/George0Papasotiriou/CVE-2025-14174-Chrome-Zero-Day

## Other vulnerabilities in Apple Ipados

- [CVE-2025-43300](https://insights.sbomify.com/CVE-2025-43300/): Apple iOS, iPadOS, and macOS Out-of-Bounds Write (critical 10.0, exploited in the wild)
- [CVE-2025-24201](https://insights.sbomify.com/CVE-2025-24201/): Apple Multiple Products WebKit Out-of-Bounds Write (critical 10.0, exploited in the wild)
- [CVE-2025-24085](https://insights.sbomify.com/CVE-2025-24085/): Apple Multiple Products Use-After-Free (critical 10.0, exploited in the wild)
- [CVE-2025-31200](https://insights.sbomify.com/CVE-2025-31200/): Apple Multiple Products Memory Corruption (critical 9.8, exploited in the wild)
- [CVE-2025-31201](https://insights.sbomify.com/CVE-2025-31201/): Apple Multiple Products Arbitrary Read and Write (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14174 and fix it if it is affected.

What it is: CVE-2025-14174 is a high-severity memory corruption vulnerability in Apple Ipados, published on 12 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2025-14174 in the wild since at least 12 Dec 2025.

Affected product: Apple Ipados. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-14174/ (Markdown: https://insights.sbomify.com/CVE-2025-14174/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-14174
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-14174
- OSV: https://osv.dev/vulnerability/CVE-2025-14174

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-14174/
Summaries are generated and may contain mistakes; the official description above is the record.