Apache authentication bypass in SQL login module
- Exploited
- No known exploitation
- Fix
- Fixed in 10.0.0-M1, 10.3.0, 11.0.0-M2
- Who is exposed
- Not reported
Summary
Apache TomEE's JDBC-based JAAS login module accepts logins without a password for accounts whose stored password is NULL, so an attacker who knows such an account's username can authenticate as that user and obtain its roles. Only deployments that use this login module with NULL passwords in the user table are affected.
Written by a model
Original description
The JDBC based JAAS login module accepts a login without a password for accounts whose stored password is NULL. A remote attacker who knows the user name of such an account can authenticate as that user and obtain its roles. Only deployments using this login module with NULL passwords in the user table are affected. 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-111240 (Apache TomEE: Authentication bypass for accounts without a stored password in SQL login module), 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-111240 (entry last updated 2026-11-16):
Affected:
- Maven package org.apache.openejb:openejb-core: from 4.0.0-beta-1, through 4.7.5
- Maven package org.apache.tomee:openejb-core: 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-111240 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-111240 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/1w1olwsbzpsj7mnv8v3vj30ohq0t0c52
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-111240
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-111240"}.Affected versions
- org.apache.openejb:openejb-coreFrom 4.0.0-beta-1 · through 4.7.5No fix released. The latest release, 4.7.5, is still affected.
- org.apache.tomee:openejb-coreFrom 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-M2Fixed in 10.3.0 (released Nov 11, 2026, 1 day after disclosure) and 11.0.0-M2 (released Nov 11, 2026, 1 day after disclosure).The latest release, 10.3.0, is not affected.
cve.now Index
- 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
- Widely used115 packages depend on org.apache.openejb:openejb-core. deps.dev
Timeline
- CVE published
- First seen by cve.now6 days
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
- Posted on X by cve.now
Public exploit activity
- EPSS: 0.53%
- Posted on X by cve.now Nov 16
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | lists.apache.org · thread/1w1olwsbzpsj7mnv8v3vj30ohq0t0c52 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-111240 |
| Record | NVD · CVE-2026-111240 |
Questions about CVE-2026-111240
Is CVE-2026-111240 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-111240?
org.apache.openejb:openejb-core (Maven): from 4.0.0-beta-1 through 4.7.5. org.apache.tomee:openejb-core (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-111240?
Upgrade to a fixed version: 10.0.0-M1, 10.3.0, 11.0.0-M2.
Source: cve.now feed data
Related
- CVE-2026-87756Apache TomEE: Missing authorization on internal deployer EJBs in default profile
- CVE-2026-86336Apache TomEE: EJB method authorization is silently skipped on JDK 21+
- CVE-2026-111241Apache TomEE: Local code execution via predictable passivation files in the shared temporary directory
- CVE-2026-87755Apache TomEE: Stateful session bean hijacking via predictable session identifiers
- CVE-2026-86811Apache TomEE: Path traversal via stateful EJB passivation
- CVE-2026-86532Apache TomEE: Username enumeration and timing side channel in JAAS login modules
No corrections so far. Something wrong on this page? Report an error.