# CVE-2026-20608: Denial of service in Safari

> Processing maliciously crafted web content may cause an unexpected process crash in Apple Safari and related operating systems.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 Feb 2026
- **Updated:** 15 Jul 2026
- **Also known as:** BIT-java-2026-20608, BIT-java-min-2026-20608, BIT-jre-2026-20608, DEBIAN-CVE-2026-20608, GHSA-jhq4-533p-8p4c, MINI-6mm6-cfr6-r49c, UBUNTU-CVE-2026-20608

## What is CVE-2026-20608?

CVE-2026-20608 is a medium-severity denial of service vulnerability in Apple Ipados, published on 11 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

This issue was addressed through improved state management. This issue is fixed in Safari 26.3, iOS 18.7.5 and iPadOS 18.7.5, iOS 26.3 and iPadOS 26.3, macOS Tahoe 26.3, visionOS 26.3. Processing maliciously crafted web content may lead to an unexpected process crash.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input), CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-20608?

3 open source packages ship an affected version, including java, java-min and jre. It affects 5 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `java` | Bitnami | All versions | 1.8.0, 8.0.491 |
| `java-min` | Bitnami | All versions | 1.8.0, 8.0.491 |
| `jre` | Bitnami | All versions | 1.8.0, 8.0.491 |

Products: Apple Ipados, Apple Iphone Os, Apple Macos, Apple Safari, Apple Visionos.

## How do I fix CVE-2026-20608?

Upgrade java to a fixed version for your release line: 1.8.0 or 8.0.491.

## Is CVE-2026-20608 being exploited?

There is no known exploitation of CVE-2026-20608 in the wild and no public exploit code.

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

What it is: CVE-2026-20608 is a medium-severity denial of service vulnerability in Apple Ipados, published on 11 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-20608 in the wild and no public exploit code.

Affected packages and fixed versions:
- java (Bitnami): affected all versions; fixed in 1.8.0, 8.0.491
- java-min (Bitnami): affected all versions; fixed in 1.8.0, 8.0.491
- jre (Bitnami): affected all versions; fixed in 1.8.0, 8.0.491

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

## Sources

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

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