# CVE-2023-21830: Deserialization in Java SE JDK and JRE > Unauthenticated attackers can modify data in Java SE and GraalVM via a deserialization flaw in sandboxed client environments. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 17 Jan 2023 - **Updated:** 28 May 2026 - **Also known as:** BIT-java-2023-21830, BIT-java-min-2023-21830, BIT-jre-2023-21830, CLEANSTART-2026-LG84885, DEBIAN-CVE-2023-21830, GHSA-xw85-qpwr-ch8h, MINI-32vj-96cm-6pcw, MINI-5gv5-44cf-6278, MINI-g5j5-jvq6-h5v6, MINI-rqj3-rxqw-52gm, UBUNTU-CVE-2023-21830, openSUSE-SU-2024:12756-1 ## What is CVE-2023-21830? CVE-2023-21830 is a medium-severity unsafe deserialization vulnerability in Oracle Graalvm, published on 17 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Vulnerability in the Oracle Java SE, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Serialization). Supported versions that are affected are Oracle Java SE: 8u351, 8u351-perf; Oracle GraalVM Enterprise Edition: 20.3.8 and 21.3.4. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Java SE, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability 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. This vulnerability does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator). CVSS 3.1 Base Score 5.3 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N). ## Which versions are affected by CVE-2023-21830? 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.361 | | `java-min` | Bitnami | All versions | 1.8.0, 8.0.361 | | `jre` | Bitnami | All versions | 1.8.0, 8.0.361 | | `java-1_8_0-openj9` | openSUSE:Tumbleweed | All versions | 1.8.0.362-1.1 | Products: Azul Zulu, Oracle Communications Unified Assurance, Oracle Graalvm, Oracle Jdk, Oracle Jre. ## How do I fix CVE-2023-21830? Upgrade java to a fixed version for your release line: 1.8.0 or 8.0.361. ## Is CVE-2023-21830 being exploited? There is no known exploitation of CVE-2023-21830 in the wild and no public exploit code. ## Other vulnerabilities in Oracle Graalvm - [CVE-2022-21449](https://insights.sbomify.com/CVE-2022-21449/): Other in Java SE JDK and JRE (high 7.5) - [CVE-2022-21476](https://insights.sbomify.com/CVE-2022-21476/): Information disclosure in Java SE JDK and JRE (high 7.5) - [CVE-2022-21541](https://insights.sbomify.com/CVE-2022-21541/): Other in Java SE JDK and JRE (medium 5.9) - [CVE-2023-21835](https://insights.sbomify.com/CVE-2023-21835/): Denial of service in Java SE JDK and JRE (medium 5.3) - [CVE-2022-21618](https://insights.sbomify.com/CVE-2022-21618/): Auth bypass in Java SE JDK and JRE (medium 5.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-21830 and fix it if it is affected. What it is: CVE-2023-21830 is a medium-severity unsafe deserialization vulnerability in Oracle Graalvm, published on 17 Jan 2023. 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-2023-21830 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.361 - java-min (Bitnami): affected all versions; fixed in 1.8.0, 8.0.361 - jre (Bitnami): affected all versions; fixed in 1.8.0, 8.0.361 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-2023-21830/ (Markdown: https://insights.sbomify.com/CVE-2023-21830/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-21830 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-21830 - OSV: https://osv.dev/vulnerability/CVE-2023-21830 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-21830/ Summaries are generated and may contain mistakes; the official description above is the record.