Public vulnerability disclosure

CVE-2026-87756

Apache TomEE: Missing authorization on internal deployer EJBs in default profile

publishedCWE-306

The internal system EJBs used for remote deployment and configuration did not enforce their administrative role check when the server ran with the default profile. A remote unauthenticated attacker able to reach the remote EJB endpoint could deploy arbitrary applications and execute code. Only installations that enabled the system applications and a remote EJB endpoint are exposed. Users are recommended to upgrade to version 10.3.0 or 11.0.0-M2, which fix the issue.

Technical severityUnscoredNo score in collected sources
Published2026-11-10Source updated 2026-11-10
Collected2026-11-101 attributed source

Fixes and workarounds

No remediation reported in collected sources.

Missing remediation information is not evidence that no patch exists.

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
Apache TomEE
Apache Software Foundation
org.apache.openejb:openejb-core
maven
≥ 4.5.1; ≤ 4.7.5 (affected, semver)
Other versions: unaffected
CNA: apache
Apache TomEE
Apache Software Foundation
org.apache.tomee:openejb-core
maven
≥ 7.0.0-M1; < 10.0.0-M1 (affected, semver)
≥ 10.0.0-M1; < 10.3.0 (affected, semver)
≥ 11.0.0-M1; < 11.0.0-M2 (affected, semver)
Other versions: unaffected
CNA: apache

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

No CVSS assessment reported. An unscored record is not a low-severity determination.

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide