External risk intelligence

Remote Unauthenticated Code Execution via EJBs

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-87756

The vulnerability affects remote EJB endpoints used for deployment and configuration. While these are typically administrative interfaces, they are network-reachable endpoints often exposed in application server environments to facilitate remote management and deployment, making them common targets for network-based access in many deployment patterns.

Missing Authentication

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This CVE describes a critical security vulnerability in internal system EJBs related to remote deployment and configuration. If enabled, an unauthenticated remote attacker could exploit this by deploying arbitrary applications and executing code on affected servers. The main concern is confirming relevance and exposure within your environment.

  • Unsecured remote deployment allows code execution.
  • Critical issue impacts remote server configuration.
  • Confirm if your systems are exposed.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by reaching a remote EJB endpoint on a system that uses the default server profile. This would allow them to deploy their own applications and run malicious code on the affected system. The issue is only present in installations where system applications and a remote EJB endpoint are enabled.

  • Remote unauthenticated access required.
  • Triggered by reaching the EJB endpoint.
  • Allows arbitrary application deployment.

Live Threat

Current exploitation, exposure, and threat context

When remote EJB endpoints are enabled and running with the default profile, an unauthenticated attacker could deploy arbitrary applications and execute code. This could impact the integrity and availability of the system.

  • Arbitrary application deployment and code execution.
  • Remote unauthenticated attacker reaches EJB endpoint.
  • System integrity and availability compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability impacts systems using EJBs for remote deployment and configuration, particularly those running with default profiles. The primary responsibility for addressing this likely falls to application owners and platform teams who manage these EJB endpoints. The first practical step is to identify all instances of the affected technology, confirm their network reachability and business criticality, and then locate the accountable owner to plan remediation based on risk.

  • Identify affected systems and owners.
  • Verify remote EJB endpoint exposure.
  • Plan risk-based remediation actions.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the affected software in CVE-2026-87756?

This CVE concerns internal system EJBs (Enterprise JavaBeans) used within application servers to handle remote software deployment and system configuration. These components are designed to allow administrators to push updates or modify server settings over a network, acting as a bridge between management tools and the runtime environment.

How does CVE-2026-87756 work?

This vulnerability is classified as CWE-306, which refers to a missing authentication for critical function. Essentially, the software fails to check if a user has the required administrative rights before allowing them to use the EJB deployment features. Because this check is skipped, anyone who can reach the endpoint can run commands or install new applications as if they were a trusted administrator.

Do I need a specific configuration to be vulnerable?

Yes. This bug is only active if your server is running with the default profile while also having both system applications and the remote EJB endpoint enabled. If these specific management interfaces are disabled or if the server is configured with a custom profile that restricts these functions, the vulnerability cannot be triggered.

How do I know if my systems are at risk?

According to Halo Surface Signal, this vulnerability is classified as external because it impacts network-reachable EJB endpoints. You should prioritize checking any servers that allow management traffic from the network, as these interfaces are common targets for remote access. Internal-only systems with no network path for attackers are less likely to be immediate targets.

When should I take action for this vulnerability?

Your first step is to locate all servers running the affected software and confirm if the remote EJB endpoint is enabled. Once you have identified these instances, determine who owns the system and evaluate the network access to these endpoints. Prioritize remediation for internet-facing systems, and consult the provided upgrade paths to version 10.3.0 or 11.0.0-M2 to permanently resolve the issue.

References