Distribution advisory
This page covers CVE-2026-22016 as tracked by BellSoft, for the package openjdk-nik-23-17. The fix is available in version 23.0.12-r0; earlier versions remain affected.
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity none, availability none.
CVSS metrics in full
The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Attack vector: Network — reachable from anywhere that can route to the service.
- Attack complexity: Low — the attack works reliably, with no preparation.
- Privileges required: None — an unauthenticated stranger can try it.
- User interaction: None — nobody has to be tricked into anything.
- Scope: Unchanged — the damage stays inside the vulnerable component.
- Confidentiality impact: High — total loss, or loss the attacker controls.
- Integrity impact: None.
- Availability impact: None.
Weakness class
BELL-CVE-2026-22016 is classified as CWE-200: Exposure of Sensitive Information. Information that should stay internal is disclosed to someone who is not authorised to see it.
Affected software
BELL-CVE-2026-22016 is recorded against 23 packages.
- openjdk-nik-23-17 (from 23.0.4-r1 up to 23.0.12-r0)
- openjdk-nik-23-21 (from 23.1.3-r1 up to 23.1.11-r0)
- openjdk-nik-25-25 (from 25.0.0-r0 up to 25.0.3-r0)
- openjdk11 (from 11.0.19_p7-r0 up to 11.0.31_p11-r0)
- openjdk11-container-jre (from 11.0.19_p7-r0 up to 11.0.31_p11-r0)
- openjdk11-lite (from 11.0.19_p7-r1 up to 11.0.31_p11-r0)
- openjdk11-perf (from 11.0.29_p11-r0 up to 11.0.31_p12-r0)
- openjdk17 (from 17.0.7_p7-r1 up to 17.0.19_p11-r0)
- openjdk17-container-jre (from 17.0.7_p7-r0 up to 17.0.19_p11-r0)
- openjdk17-crac (from 17.0.10_p13-r0 up to 17.0.19_p12-r0)
- openjdk17-lite (from 17.0.7_p7-r1 up to 17.0.19_p11-r0)
- openjdk21 (from 21_p37-r0 up to 21.0.11_p11-r0)
- openjdk21-container-jre (from 21_p37-r0 up to 21.0.11_p11-r0)
- openjdk21-crac (from 21.0.2_p15-r0 up to 21.0.11_p12-r0)
- openjdk21-lite (from 21_p37-r0 up to 21.0.11_p11-r0)
- openjdk25 (from 25_p37-r0 up to 25.0.3_p11-r0)
- openjdk25-container-jre (from 25_p37-r0 up to 25.0.3_p11-r0)
- openjdk25-lite (from 25_p37-r0 up to 25.0.3_p11-r0)
- openjdk26 (from 26_p37-r0 up to 26.0.1_p10-r0)
- openjdk26-container-jre (from 26_p37-r0 up to 26.0.1_p10-r0)
- openjdk26-lite (from 26_p37-r0 up to 26.0.1_p10-r0)
- openjdk8 (from 8u372_p7-r1 up to 8.492_p9-r0)
- openjdk8-perf (from 8.472_p10-r0 up to 8.492_p10-r0)
Timeline and source
Published on 23 April 2026 and last revised on 4 August 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
docs.bell-sw.com (Advisory)
Other advisories for this package
openjdk-nik-23-17 has other advisories on record. If you are patching this one, these are worth checking on the same host:
Same weakness in other software
These advisories are the same class of weakness (CWE-200: Exposure of Sensitive Information) in other software:
