SUSE · java-17-openj9-17.0.21.0-1.1 on GA media
Affects SUSESource GCVE Database
Not known to be exploited · CVSS 6.5 Medium.
Data as of 6 Nov 2026, 14:18 UTC
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Oracle CorporationOracle Java SE | Affected
| Fixed in– |
| Oracle CorporationOracle GraalVM for JDK | Affected
| Fixed in– |
| Oracle CorporationOracle GraalVM Enterprise Edition | Affected
| Fixed in– |
Mavencom.oracle/java-sepkg:maven/com.oracle/java-seOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should update to the java-17-openj9-17.0.21.0-1.1 package on openSUSE Tumbleweed to apply the security fixes. No additional mitigation guidance is available from the provided data.
Description
Multiple security issues have been addressed in the java-17-openj9-17.0.21.0-1.1 package for openSUSE Tumbleweed. These fixes are part of the GA media release by the SUSE Product Security Team. No specific vulnerabilities or impacts are detailed in the provided information.
References
- suse.com/support/security/rating/ (opens in a new tab)
- ftp.suse.com/pub/projects/security/csaf/opensuse-su-2026_12434-1.json (opens in a new tab)
- suse.com/security/cve/CVE-2026-101516/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-83374/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-83380/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-83387/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-83400/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-87292/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-87367/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-91334/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-91373/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-91375/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-91380/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-91397/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-91400/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-91415/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-91451/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-91453/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-91462/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-91464/ (opens in a new tab)