USN-9004-2
Vulnerability from osv_ubuntu – Published: 2026-11-17 03:57 – Updated: 2026-11-17 03:57 – Source websiteUSN-9004-1 fixed vulnerabilities in OpenJDK 25. Unfortunately, the fix included an unnecessary debuginfo file. This update fixes the problem.
We apologize for the inconvenience.
Original advisory details:
It was discovered that the 2D component of OpenJDK 25 did not correctly authenticate users. A remote attacker could possibly use this issue to cause a denial of service or to read or modify sensitive data. (CVE-2026-91415)
It was discovered that the Networking component of OpenJDK 25 did not correctly authenticate users. A remote attacker could possibly use this issue to modify sensitive data. (CVE-2026-91398)
It was discovered that the 2D component of OpenJDK 25 did not correctly authenticate users. A remote attacker could possibly use this issue to cause a denial of service or to modify sensitive data. (CVE-2026-91382)
It was discovered that the JGSS component of OpenJDK 25 did not correctly authenticate users. A remote attacker could possibly use this issue to cause a denial of service or to modify sensitive data. (CVE-2026-91411)
It was discovered that the Networking component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to cause a denial of service or to modify sensitive data. (CVE-2026-83395)
It was discovered that the Security component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-83381, CVE-2026-87294)
It was discovered that the JAXP component of OpenJDK 25 did not correctly authenticate users. A remote attacker could possibly use this issue to read sensitive data. (CVE-2026-87290)
It was discovered that the JDBC component of OpenJDK 25 did not correctly authenticate users. A remote attacker could possibly use this issue to read sensitive data. (CVE-2026-83387)
It was discovered that the JGSS component of OpenJDK 25 did not correctly authenticate users. A remote attacker could possibly use this issue to modify sensitive data. (CVE-2026-91462)
It was discovered that the Security component of OpenJDK 25 did not correctly authenticate users. A remote attacker could possibly use this issue to modify sensitive data. (CVE-2026-83374)
It was discovered that the Libraries component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to cause a denial of service. (CVE-2026-91410)
It was discovered that the Networking component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to modify sensitive data. (CVE-2026-87292, CVE-2026-91332, CVE-2026-91451, CVE-2026-91452)
It was discovered that the JSSE component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to cause a denial of service. (CVE-2026-91373)
It was discovered that the JAAS component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to read sensitive data. (CVE-2026-83380)
It was discovered that the JAXP component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to cause a denial of service. (CVE-2026-83400)
It was discovered that the JGSS component of OpenJDK 25 did not correctly authenticate users. A remote attacker could possibly use this issue to read sensitive data. (CVE-2026-91463, CVE-2026-91464)
It was discovered that the Lightweight HTTP Server component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to modify sensitive data. (CVE-2026-91453)
It was discovered that the ImageIO component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to cause a denial of service. (CVE-2026-91418)
It was discovered that the Compiler component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-91487)
It was discovered that the Serviceability component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-91374)
It was discovered that the Libraries component of OpenJDK 25 did not correctly authenticate users. A local attacker could possibly use this issue to modify sensitive data. (CVE-2026-91375)
It was discovered that the JDK tools component of OpenJDK 25 did not correctly authenticate users. A local attacker could possibly use this issue to modify sensitive data. (CVE-2026-91379)
It was discovered that the Utility component of OpenJDK 25 did not correctly authorize users. A local attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-91380)
It was discovered that the ImageIO component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to read sensitive data. (CVE-2026-91334)
It was discovered that the JAXP component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to modify sensitive data. (CVE-2026-87367)
It was discovered that the JSSE component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to modify sensitive data. (CVE-2026-83376, CVE-2026-91461)
It was discovered that the Serviceability component of OpenJDK 25 did not correctly authorize users. A local attacker could possibly use this issue to cause a denial of service or to modify sensitive data. (CVE-2026-91397)
It was discovered that the Sound component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to cause a denial of service. (CVE-2026-91400)
It was discovered that the AWT component of OpenJDK 25 did not correctly authorize users. A remote attacker could possibly use this issue to read sensitive data. (CVE-2026-91335)
It was discovered that the Networking component of OpenJDK 25 did not correctly authenticate users. A remote attacker could possibly use this issue to read sensitive data. (CVE-2026-91394)
It was discovered that the Networking component of OpenJDK 25 did not correctly authorize users. An unauthenticated remote attacker could possibly use this issue to read sensitive data. (CVE-2026-87291)
It was discovered that the Compiler component of OpenJDK 25 did not correctly authorize users. An unauthenticated remote attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-83378)
It was discovered that the Compiler component of OpenJDK 25 did not correctly authorize users. An unauthenticated remote attacker could possibly use this issue to read sensitive data. (CVE-2026-87255)
It was discovered that the Security component of OpenJDK 25 did not correctly authorize users. An unauthenticated remote attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-91333)
It was discovered that the JSSE component of OpenJDK 25 did not correctly authenticate users. A remote attacker could possibly use this issue to read or modify sensitive data. (CVE-2026-91403)
In addition to security fixes, the updated packages contain bug fixes, new features, and possibly incompatible changes.
Please see the following for more information: https://openjdk.org/groups/vulnerability/advisories/2026-10-20 https://openjdk.org/groups/vulnerability/advisories/2026-10-21 https://openjdk.org/groups/vulnerability/advisories/2026-10-24
| URL | Type | |
|---|---|---|
{
"affected": [
{
"database_specific": {
"cves_map": {
"cves": [],
"ecosystem": "Ubuntu:22.04:LTS"
}
},
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "openjdk-25-demo",
"binary_version": "25.0.5.0.3+1-3~22.04.1"
},
{
"binary_name": "openjdk-25-jdk",
"binary_version": "25.0.5.0.3+1-3~22.04.1"
},
{
"binary_name": "openjdk-25-jdk-headless",
"binary_version": "25.0.5.0.3+1-3~22.04.1"
},
{
"binary_name": "openjdk-25-jre",
"binary_version": "25.0.5.0.3+1-3~22.04.1"
},
{
"binary_name": "openjdk-25-jre-headless",
"binary_version": "25.0.5.0.3+1-3~22.04.1"
},
{
"binary_name": "openjdk-25-jre-zero",
"binary_version": "25.0.5.0.3+1-3~22.04.1"
},
{
"binary_name": "openjdk-25-source",
"binary_version": "25.0.5.0.3+1-3~22.04.1"
},
{
"binary_name": "openjdk-25-testsupport",
"binary_version": "25.0.5.0.3+1-3~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "openjdk-25",
"purl": "pkg:deb/ubuntu/openjdk-25@25.0.5.0.3+1-3~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "25.0.5.0.3+1-3~22.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"25+36-1~22.04.2",
"25.0.1+8-1~22.04",
"25.0.2+10-1~22.04",
"25.0.3+9-2~22.04.2",
"25.0.4+7-1~22.04",
"25.0.4.1+1-1~22.04.4",
"25.0.5.0.3+1-1~22.04.1"
]
},
{
"database_specific": {
"cves_map": {
"cves": [],
"ecosystem": "Ubuntu:24.04:LTS"
}
},
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "openjdk-25-demo",
"binary_version": "25.0.5.0.3+1-3~24.04.1"
},
{
"binary_name": "openjdk-25-jdk",
"binary_version": "25.0.5.0.3+1-3~24.04.1"
},
{
"binary_name": "openjdk-25-jdk-headless",
"binary_version": "25.0.5.0.3+1-3~24.04.1"
},
{
"binary_name": "openjdk-25-jre",
"binary_version": "25.0.5.0.3+1-3~24.04.1"
},
{
"binary_name": "openjdk-25-jre-headless",
"binary_version": "25.0.5.0.3+1-3~24.04.1"
},
{
"binary_name": "openjdk-25-jre-zero",
"binary_version": "25.0.5.0.3+1-3~24.04.1"
},
{
"binary_name": "openjdk-25-source",
"binary_version": "25.0.5.0.3+1-3~24.04.1"
},
{
"binary_name": "openjdk-25-testsupport",
"binary_version": "25.0.5.0.3+1-3~24.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "openjdk-25",
"purl": "pkg:deb/ubuntu/openjdk-25@25.0.5.0.3+1-3~24.04.1?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "25.0.5.0.3+1-3~24.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"25+36-1~24.04.2",
"25.0.1+8-1~24.04",
"25.0.2+10-1~24.04",
"25.0.3+9-2~24.04.2",
"25.0.4+7-1~24.04",
"25.0.4.1+1-1~24.04.4",
"25.0.5.0.3+1-1~24.04.1"
]
},
{
"database_specific": {
"cves_map": {
"cves": [],
"ecosystem": "Ubuntu:26.10"
}
},
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "openjdk-25-demo",
"binary_version": "25.0.5.0.3+1-3~26.10.1"
},
{
"binary_name": "openjdk-25-jdk",
"binary_version": "25.0.5.0.3+1-3~26.10.1"
},
{
"binary_name": "openjdk-25-jdk-headless",
"binary_version": "25.0.5.0.3+1-3~26.10.1"
},
{
"binary_name": "openjdk-25-jre",
"binary_version": "25.0.5.0.3+1-3~26.10.1"
},
{
"binary_name": "openjdk-25-jre-headless",
"binary_version": "25.0.5.0.3+1-3~26.10.1"
},
{
"binary_name": "openjdk-25-jre-zero",
"binary_version": "25.0.5.0.3+1-3~26.10.1"
},
{
"binary_name": "openjdk-25-source",
"binary_version": "25.0.5.0.3+1-3~26.10.1"
},
{
"binary_name": "openjdk-25-testsupport",
"binary_version": "25.0.5.0.3+1-3~26.10.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.10",
"name": "openjdk-25",
"purl": "pkg:deb/ubuntu/openjdk-25@25.0.5.0.3+1-3~26.10.1?arch=source\u0026distro=stonking"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "25.0.5.0.3+1-3~26.10.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"25.0.3~7ea-2",
"25.0.3+9-2",
"25.0.4~4ea-1",
"25.0.4+7-1",
"25.0.4.1+1-1",
"25.0.5.0.3+1-1~26.10.1"
]
},
{
"database_specific": {
"cves_map": {
"cves": [],
"ecosystem": "Ubuntu:26.04:LTS"
}
},
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "openjdk-25-demo",
"binary_version": "25.0.5.0.3+1-3~26.04.1"
},
{
"binary_name": "openjdk-25-jdk",
"binary_version": "25.0.5.0.3+1-3~26.04.1"
},
{
"binary_name": "openjdk-25-jdk-headless",
"binary_version": "25.0.5.0.3+1-3~26.04.1"
},
{
"binary_name": "openjdk-25-jre",
"binary_version": "25.0.5.0.3+1-3~26.04.1"
},
{
"binary_name": "openjdk-25-jre-headless",
"binary_version": "25.0.5.0.3+1-3~26.04.1"
},
{
"binary_name": "openjdk-25-jre-zero",
"binary_version": "25.0.5.0.3+1-3~26.04.1"
},
{
"binary_name": "openjdk-25-source",
"binary_version": "25.0.5.0.3+1-3~26.04.1"
},
{
"binary_name": "openjdk-25-testsupport",
"binary_version": "25.0.5.0.3+1-3~26.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "openjdk-25",
"purl": "pkg:deb/ubuntu/openjdk-25@25.0.5.0.3+1-3~26.04.1?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "25.0.5.0.3+1-3~26.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"25+36-1",
"25.0.1+8-1",
"25.0.1+8-2",
"25.0.1+8-3",
"25.0.2+10-1",
"25.0.3~5ea-2",
"25.0.3~7ea-2",
"25.0.3+9-2~26.04.2",
"25.0.4+7-1~26.04",
"25.0.4.1+1-1~26.04.4",
"25.0.5.0.3+1-1~26.04.1"
]
}
],
"aliases": [],
"details": "USN-9004-1 fixed vulnerabilities in OpenJDK 25. Unfortunately, the fix\nincluded an unnecessary debuginfo file. This update fixes the problem.\n\nWe apologize for the inconvenience.\n\nOriginal advisory details:\n\n It was discovered that the 2D component of OpenJDK 25 did not correctly\n authenticate users. A remote attacker could possibly use this issue to\n cause a denial of service or to read or modify sensitive data.\n (CVE-2026-91415)\n\n It was discovered that the Networking component of OpenJDK 25 did not\n correctly authenticate users. A remote attacker could possibly use this\n issue to modify sensitive data. (CVE-2026-91398)\n\n It was discovered that the 2D component of OpenJDK 25 did not correctly\n authenticate users. A remote attacker could possibly use this issue to\n cause a denial of service or to modify sensitive data. (CVE-2026-91382)\n\n It was discovered that the JGSS component of OpenJDK 25 did not correctly\n authenticate users. A remote attacker could possibly use this issue to\n cause a denial of service or to modify sensitive data. (CVE-2026-91411)\n\n It was discovered that the Networking component of OpenJDK 25 did not\n correctly authorize users. A remote attacker could possibly use this issue\n to cause a denial of service or to modify sensitive data. (CVE-2026-83395)\n\n It was discovered that the Security component of OpenJDK 25 did not\n correctly authorize users. A remote attacker could possibly use this issue\n to read or modify sensitive data. (CVE-2026-83381, CVE-2026-87294)\n\n It was discovered that the JAXP component of OpenJDK 25 did not correctly\n authenticate users. A remote attacker could possibly use this issue to read\n sensitive data. (CVE-2026-87290)\n\n It was discovered that the JDBC component of OpenJDK 25 did not correctly\n authenticate users. A remote attacker could possibly use this issue to read\n sensitive data. (CVE-2026-83387)\n\n It was discovered that the JGSS component of OpenJDK 25 did not correctly\n authenticate users. A remote attacker could possibly use this issue to\n modify sensitive data. (CVE-2026-91462)\n\n It was discovered that the Security component of OpenJDK 25 did not\n correctly authenticate users. A remote attacker could possibly use this\n issue to modify sensitive data. (CVE-2026-83374)\n\n It was discovered that the Libraries component of OpenJDK 25 did not\n correctly authorize users. A remote attacker could possibly use this issue\n to cause a denial of service. (CVE-2026-91410)\n\n It was discovered that the Networking component of OpenJDK 25 did not\n correctly authorize users. A remote attacker could possibly use this issue\n to modify sensitive data. (CVE-2026-87292, CVE-2026-91332, CVE-2026-91451,\n CVE-2026-91452)\n\n It was discovered that the JSSE component of OpenJDK 25 did not correctly\n authorize users. A remote attacker could possibly use this issue to cause a\n denial of service. (CVE-2026-91373)\n\n It was discovered that the JAAS component of OpenJDK 25 did not correctly\n authorize users. A remote attacker could possibly use this issue to read\n sensitive data. (CVE-2026-83380)\n\n It was discovered that the JAXP component of OpenJDK 25 did not correctly\n authorize users. A remote attacker could possibly use this issue to cause a\n denial of service. (CVE-2026-83400)\n\n It was discovered that the JGSS component of OpenJDK 25 did not correctly\n authenticate users. A remote attacker could possibly use this issue to read\n sensitive data. (CVE-2026-91463, CVE-2026-91464)\n\n It was discovered that the Lightweight HTTP Server component of OpenJDK 25\n did not correctly authorize users. A remote attacker could possibly use\n this issue to modify sensitive data. (CVE-2026-91453)\n\n It was discovered that the ImageIO component of OpenJDK 25 did not\n correctly authorize users. A remote attacker could possibly use this issue\n to cause a denial of service. (CVE-2026-91418)\n\n It was discovered that the Compiler component of OpenJDK 25 did not\n correctly authorize users. A remote attacker could possibly use this issue\n to read or modify sensitive data. (CVE-2026-91487)\n\n It was discovered that the Serviceability component of OpenJDK 25 did not\n correctly authorize users. A remote attacker could possibly use this issue\n to read or modify sensitive data. (CVE-2026-91374)\n\n It was discovered that the Libraries component of OpenJDK 25 did not\n correctly authenticate users. A local attacker could possibly use this\n issue to modify sensitive data. (CVE-2026-91375)\n\n It was discovered that the JDK tools component of OpenJDK 25 did not\n correctly authenticate users. A local attacker could possibly use this\n issue to modify sensitive data. (CVE-2026-91379)\n\n It was discovered that the Utility component of OpenJDK 25 did not\n correctly authorize users. A local attacker could possibly use this issue\n to read or modify sensitive data. (CVE-2026-91380)\n\n It was discovered that the ImageIO component of OpenJDK 25 did not\n correctly authorize users. A remote attacker could possibly use this issue\n to read sensitive data. (CVE-2026-91334)\n\n It was discovered that the JAXP component of OpenJDK 25 did not correctly\n authorize users. A remote attacker could possibly use this issue to modify\n sensitive data. (CVE-2026-87367)\n\n It was discovered that the JSSE component of OpenJDK 25 did not correctly\n authorize users. A remote attacker could possibly use this issue to modify\n sensitive data. (CVE-2026-83376, CVE-2026-91461)\n\n It was discovered that the Serviceability component of OpenJDK 25 did not\n correctly authorize users. A local attacker could possibly use this issue\n to cause a denial of service or to modify sensitive data. (CVE-2026-91397)\n\n It was discovered that the Sound component of OpenJDK 25 did not correctly\n authorize users. A remote attacker could possibly use this issue to cause a\n denial of service. (CVE-2026-91400)\n\n It was discovered that the AWT component of OpenJDK 25 did not correctly\n authorize users. A remote attacker could possibly use this issue to read\n sensitive data. (CVE-2026-91335)\n\n It was discovered that the Networking component of OpenJDK 25 did not\n correctly authenticate users. A remote attacker could possibly use this\n issue to read sensitive data. (CVE-2026-91394)\n\n It was discovered that the Networking component of OpenJDK 25 did not\n correctly authorize users. An unauthenticated remote attacker could\n possibly use this issue to read sensitive data. (CVE-2026-87291)\n\n It was discovered that the Compiler component of OpenJDK 25 did not\n correctly authorize users. An unauthenticated remote attacker could\n possibly use this issue to read or modify sensitive data. (CVE-2026-83378)\n\n It was discovered that the Compiler component of OpenJDK 25 did not\n correctly authorize users. An unauthenticated remote attacker could\n possibly use this issue to read sensitive data. (CVE-2026-87255)\n\n It was discovered that the Security component of OpenJDK 25 did not\n correctly authorize users. An unauthenticated remote attacker could\n possibly use this issue to read or modify sensitive data. (CVE-2026-91333)\n\n It was discovered that the JSSE component of OpenJDK 25 did not correctly\n authenticate users. A remote attacker could possibly use this issue to read\n or modify sensitive data. (CVE-2026-91403)\n\n In addition to security fixes, the updated packages contain bug fixes, new\n features, and possibly incompatible changes.\n\n Please see the following for more information:\n https://openjdk.org/groups/vulnerability/advisories/2026-10-20\n https://openjdk.org/groups/vulnerability/advisories/2026-10-21\n https://openjdk.org/groups/vulnerability/advisories/2026-10-24",
"id": "USN-9004-2",
"modified": "2026-11-17T03:57:30Z",
"published": "2026-11-17T03:57:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-9004-2"
},
{
"type": "REPORT",
"url": "https://launchpad.net/bugs/2173935"
}
],
"related": [],
"schema_version": "1.7.0",
"summary": "openjdk-25 regression",
"upstream": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.