# CVE-2025-31277: Apple Multiple Products Buffer Overflow

> Attackers can execute arbitrary code by tricking users into visiting malicious web content in Safari or Apple operating systems.

- **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 20 Mar 2026 (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:** 29 Jul 2025
- **Updated:** 21 Sep 2026
- **Also known as:** DEBIAN-CVE-2025-31277, GHSA-vrfh-8v52-6452, UBUNTU-CVE-2025-31277

## What is CVE-2025-31277?

CVE-2025-31277 is a high-severity memory corruption vulnerability in Apple Ipados, published on 29 Jul 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

The issue was addressed with improved memory handling. This issue is fixed in Safari 18.6, iOS 18.6 and iPadOS 18.6, macOS Sequoia 15.6, tvOS 18.6, visionOS 2.6, watchOS 11.6. Processing maliciously crafted web content may lead to memory corruption.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 15 products.


Products: Apple Ipados, Apple Iphone Os, Apple Macos, Apple Safari, Apple Tvos, Apple Visionos, Apple Watchos, Redhat Enterprise Linux, Redhat Enterprise Linux Aus, Redhat Enterprise Linux Els, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Tus, Redhat Enterprise Linux Update Services for Sap Solutions, Webkitgtk Webkitgtk, Wpewebkit Wpe Webkit.

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

Upgrade to a fixed version. US federal agencies must fix it by 3 Apr 2026.

## Is CVE-2025-31277 being exploited?

Yes. Attackers have exploited CVE-2025-31277 in the wild since at least 20 Mar 2026.

Public exploit code:

- Static analysis of the DarkSword iOS WebKit exploit chain — delivery, staging, and CVE breakdown   (CVE-2025-31277, CVE-2025-43529) (github_poc): https://github.com/stationedK-06/DarkSword_analysis

## 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-31277 and fix it if it is affected.

What it is: CVE-2025-31277 is a high-severity memory corruption vulnerability in Apple Ipados, published on 29 Jul 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-31277 in the wild since at least 20 Mar 2026.

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-31277/ (Markdown: https://insights.sbomify.com/CVE-2025-31277/index.md)
```

## Sources

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

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