# CVE-2026-47013: Denial of service in Oracle Java SE

> An unauthenticated attacker can cause a partial denial of service in Oracle Java SE via JavaFX APIs.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jul 2026
- **Updated:** 12 Aug 2026
- **Also known as:** BIT-java-2026-47013, BIT-java-min-2026-47013, BIT-jre-2026-47013, GHSA-q3pg-mf84-hjmw, MINI-v86p-8mx4-6qhw

## What is CVE-2026-47013?

CVE-2026-47013 is a medium-severity denial of service vulnerability in Oracle Jdk, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in Oracle Java SE (component: JavaFX).   The supported version that is affected is Oracle Java SE: 8u491. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE.  Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Java SE. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. CVSS 3.1 Base Score 5.3 (Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

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


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

Products: Oracle Jdk, Oracle Jre.

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

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

## Is CVE-2026-47013 being exploited?

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

## Other vulnerabilities in Oracle Jdk

- [CVE-2012-4681](https://insights.sbomify.com/CVE-2012-4681/): Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2012-1723](https://insights.sbomify.com/CVE-2012-1723/): Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2015-4805](https://insights.sbomify.com/CVE-2015-4805/): Deserialization in n/a (critical 10.0)
- [CVE-2015-4835](https://insights.sbomify.com/CVE-2015-4835/): Other in n/a (critical 10.0)
- [CVE-2015-4843](https://insights.sbomify.com/CVE-2015-4843/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47013 and fix it if it is affected.

What it is: CVE-2026-47013 is a medium-severity denial of service vulnerability in Oracle Jdk, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47013 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.501
- java-min (Bitnami): affected all versions; fixed in 1.8.0, 8.0.501
- jre (Bitnami): affected all versions; fixed in 1.8.0, 8.0.501

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

## Sources

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

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