CVE-2026-91417
Description
A flaw was found in the Common Object Request Broker Architecture (CORBA) component of OpenJDK. An unauthenticated remote attacker could exploit this flaw by sending specially crafted data to exposed application programming interfaces (APIs) over the network. A successful attack can result in a partial Denial of Service (DoS), degrading application availability.
Statement
This vulnerability is rated Moderate rather than Important because successful exploitation is restricted to a partial denial of service without compromising confidentiality or data integrity. Within Red Hat environments, the issue primarily concerns legacy Java 8 workloads that expose CORBA or RMI-IIOP services to untrusted networks, while modern OpenJDK versions (11 and later) are not vulnerable due to the complete removal of CORBA modules. Because standard enterprise deployments rarely expose CORBA endpoints directly to untrusted callers, the overall risk and attack surface remain limited.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.3 | N/A | 5.3 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | None | N/A | None |
| Availability Impact | Low | N/A | Low |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)
When allocating resources without limits, an attacker could prevent other systems, applications, or processes from accessing the same type of resource. It can be easy for an attacker to consume many resources by rapidly making many requests or causing larger resources to be used than is needed.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.