# CVE-2026-22016: XML external entity in Oracle GraalVM Enterprise Edition > Unauthenticated attackers can exploit JAXP APIs to access critical data via XML External Entity injection in Oracle Java SE and GraalVM. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 21 Apr 2026 - **Updated:** 18 Sep 2026 - **Also known as:** BELL-CVE-2026-22016, BIT-java-2026-22016, BIT-java-min-2026-22016, BIT-jre-2026-22016, CLSA-2026-1777942551, CLSA-2026-1777943369, CLSA-2026-1777943705, DEBIAN-CVE-2026-22016, GHSA-9m62-hmpm-rr2m, MINI-2872-8whj-5h87, MINI-2pwp-f3q6-64pv, MINI-68wv-rhpm-7r9g, MINI-69cm-8p66-xrrf, MINI-7fcg-gx4p-wv7p, MINI-7vp5-7qjg-5gm6, MINI-94rj-fm66-j59h, MINI-9mm3-v4fp-xhqp, MINI-f5wp-5cm8-5rx9, MINI-ghqg-wf6x-c742, MINI-gpjh-9pfx-86wq, MINI-j5gp-7449-3mp4, MINI-jcqg-5ph6-q2c9, MINI-mj79-pjm3-hm4c, MINI-mw2m-r4g8-ghp9, MINI-p5rf-2x6j-g94c, MINI-pcxx-hr36-33f5, MINI-pwqc-j988-9364, MINI-q5xx-8w2g-c8hx, MINI-qvcp-mf6r-hvjw, MINI-w8vp-jx7v-jwf6, MINI-wj65-48r2-wrgx, MINI-wwv9-g859-7vcj, MINI-x23x-4h9f-pjxq, MINI-x426-23hr-gp65, MINI-xh4q-h3j2-2rxf, UBUNTU-CVE-2026-22016 ## What is CVE-2026-22016? CVE-2026-22016 is a high-severity vulnerability in Oracle Graalvm, published on 21 Apr 2026. 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 for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: JAXP). Supported versions that are affected are Oracle Java SE: 8u481, 8u481-b50, 8u481-perf, 11.0.30, 17.0.18, 21.0.10, 25.0.2, 26; Oracle GraalVM for JDK: 17.0.18 and 21.0.10; Oracle GraalVM Enterprise Edition: 21.3.17. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. 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 7.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N). Weakness: CWE-611 (Improper Restriction of XML External Entity Reference), CWE-502 (Deserialization of Untrusted Data), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2026-22016? 3 open source packages ship an affected version, including java, java-min and jre. It affects 4 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `java` | Bitnami | All versions | 1.8.0, 8.0.491, 11.0.31, 17.0.19, 21.0.11, 25.0.3, 26.0.1 | | `java-min` | Bitnami | All versions | 1.8.0, 8.0.491, 11.0.31, 17.0.19, 21.0.11, 25.0.3, 26.0.1 | | `jre` | Bitnami | All versions | 1.8.0, 8.0.491, 11.0.31, 17.0.19, 21.0.11, 25.0.3, 26.0.1 | Products: Oracle Graalvm, Oracle Graalvm for Jdk, Oracle Jdk, Oracle Jre. ## How do I fix CVE-2026-22016? Upgrade java to a fixed version for your release line: 1.8.0, 8.0.491, 11.0.31 or 17.0.19. ## Is CVE-2026-22016 being exploited? There is no known exploitation of CVE-2026-22016 in the wild and no public exploit code. Public exploit code: - https://github.com/George0Papasotiriou/CVE-2026-22016-IPFS-CID-Spoofing-via-Multihash-Length-Extension (github_poc): https://github.com/George0Papasotiriou/CVE-2026-22016-IPFS-CID-Spoofing-via-Multihash-Length-Extension ## Other vulnerabilities in Oracle Graalvm - [CVE-2025-50059](https://insights.sbomify.com/CVE-2025-50059/): Security feature bypass in Oracle GraalVM Enterprise Edition (high 8.6) - [CVE-2021-32803](https://insights.sbomify.com/CVE-2021-32803/): Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning (high 8.2) - [CVE-2021-32804](https://insights.sbomify.com/CVE-2021-32804/): Arbitrary File Creation/Overwrite due to insufficient absolute path sanitization (high 8.2) - [CVE-2025-30749](https://insights.sbomify.com/CVE-2025-30749/): Code injection in Oracle GraalVM Enterprise Edition (high 8.1) - [CVE-2025-50106](https://insights.sbomify.com/CVE-2025-50106/): Code injection in Oracle GraalVM Enterprise Edition (high 8.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-22016 and fix it if it is affected. What it is: CVE-2026-22016 is a high-severity vulnerability in Oracle Graalvm, published on 21 Apr 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-22016 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, 11.0.31, 17.0.19, 21.0.11, 25.0.3, 26.0.1 - java-min (Bitnami): affected all versions; fixed in 1.8.0, 8.0.491, 11.0.31, 17.0.19, 21.0.11, 25.0.3, 26.0.1 - jre (Bitnami): affected all versions; fixed in 1.8.0, 8.0.491, 11.0.31, 17.0.19, 21.0.11, 25.0.3, 26.0.1 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-22016/ (Markdown: https://insights.sbomify.com/CVE-2026-22016/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-22016 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-22016 - OSV: https://osv.dev/vulnerability/CVE-2026-22016 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-22016/ Summaries are generated and may contain mistakes; the official description above is the record.