Skip to main content
Menu
CVEs

Apache TomEE Web Services authentication bypass in EJB web service endpoints

CVE-2026-111264Published November 10, 2026, updated

9.8CriticalCISA-ADP
Exploited
No known exploitation
Fix
Fixed in 10.0.0-M1, 10.3.0, 11.0.0-M2
Who is exposed
Not reported

Summary

The Apache TomEE server's handling of EJB JAX-WS web service endpoints with configured authentication can be bypassed, because the security constraint only covers some HTTP methods. A remote attacker who does not need to log in can gain access to these endpoints by sending requests with a different HTTP method.

Written by a model

Original description

The security constraint generated for EJB JAX-WS endpoints with configured authentication protects only some HTTP methods. A remote unauthenticated attacker can bypass authentication by sending requests with another HTTP method. Users are recommended to upgrade to version 10.3.0 or 11.0.0-M2, which fix the issue.

What to do

Upgrade to a fixed version: 10.0.0-M1, 10.3.0, 11.0.0-M2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-111264 (Apache TomEE: Authentication bypass on EJB web service endpoints via HTTP method), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-111264 (entry last updated 2026-11-16):
Affected:
- Maven package org.apache.openejb:tomee-webservices: from 4.0.0-beta-1, through 4.0.0; from 1.5.0, through 1.7.5
- Maven package org.apache.tomee:tomee-webservices: from 7.0.0-M1, fixed in 10.0.0-M1; from 10.0.0-M1, fixed in 10.3.0; from 11.0.0-M1, fixed in 11.0.0-M2
Fixed versions: 10.0.0-M1, 10.3.0, 11.0.0-M2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-111264 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-111264 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Maven): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread.html/tldxh492p71z2rlw7g4l1vplrxo5n116
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-111264
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-111264"}.

Affected versions

cve.now Index

40of 100 · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach10/20Affects Maven packages
  • Severity10/10CVSS 9.8, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 85 if added to CISA KEV
  • Would score about 80 if CISA's SSVC rates exploitation active
  • Would score about 45 if advisories confirm default setups are exposed

Impact

Timeline

  1. CVE published
  2. First seen by cve.now6 days
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

  4. Record last updated
  5. Posted on X by cve.now

Public exploit activity

100%0Posted on X by cve.nowNov 10Nov 22
  • EPSS: 0.68%
  • Posted on X by cve.now Nov 16

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Advisorylists.apache.org · thread.html/tldxh492p71z2rlw7g4l1vplrxo5n116
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-111264
RecordNVD · CVE-2026-111264

Questions about CVE-2026-111264

Is CVE-2026-111264 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-111264?

org.apache.openejb:tomee-webservices (Maven): from 4.0.0-beta-1 through 4.0.0; from 1.5.0 through 1.7.5. org.apache.tomee:tomee-webservices (Maven): from 7.0.0-M1 before 10.0.0-M1; from 10.0.0-M1 before 10.3.0; from 11.0.0-M1 before 11.0.0-M2.

Source: cve.now feed data

How do I fix CVE-2026-111264?

Upgrade to a fixed version: 10.0.0-M1, 10.3.0, 11.0.0-M2.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.