CyberSecBulletin
CVE-2026-15563NVD status: Awaiting Analysis

Red Hat JBoss Enterprise Application Platform…: Missing Authentication for Critical Functionality

Published Updated By the CyberSecBulletin desk

CVE-2026-15563 is a high-severity missing authentication for critical functionality vulnerability in Red Hat JBoss Enterprise Application Platform 7.4.25 from Red Hat, with a CVSS 3.1 base score of 7.4 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 0.66% chance of exploitation within 30 days, higher than 52% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of Red Hat JBoss Enterprise Application Platform 7.4.25 you run against the affected versions below, and install the vendor's latest release.
  2. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
Red HatRed Hat JBoss Enterprise Application Platform 7.4.25Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 7Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 8.1.8.GANot specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 8.1 for RHEL 10Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 8.1 for RHEL 8Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 8.1 for RHEL 9Not specified in the recordNot stated
Red HatRed Hat Single Sign-On 7.6.13Not specified in the recordNot stated
Red HatRed Hat Single Sign-On 7.6 for RHEL 7Not specified in the recordNot stated
Red HatRed Hat Single Sign-On 7.6 for RHEL 8Not specified in the recordNot stated
Red HatRed Hat Single Sign-On 7.6 for RHEL 9Not specified in the recordNot stated
Red HatRHEL-8 based Middleware ContainersNot specified in the recordNot stated
Red HatRed Hat Fuse 7Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 7Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform Expansion PackNot specified in the recordNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
HighSuccess depends on conditions outside the attacker's control.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N. Scored by CNA (redhat.com).

Official description

A flaw was found in EAP's IIOP. The listener's NameService would accept bind operations without authentication, allowing an attacker to hijack JNDI lookups and binding them to a malicious ORB, achieving MITM or DoS on further invocations.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Missing Authentication for Critical Functionality

The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

How developers prevent this class of flaw

  • For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator.
  • When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to require strong authentication for users who should be allowed to access the data.

More Missing Authentication for Critical Functionality vulnerabilities (CWE-306)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Red Hat JBoss Enterprise Application Platform 7.4.25

All Red Hat JBoss Enterprise Application Platform 7.4.25 vulnerabilities

Recent Missing Authentication for Critical Functionality vulnerabilities

Spotted an error? Tell us.