CVE-2026-111240: Apache TomEE: Authentication bypass for accounts without a stored password in SQL login module
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
- Fixed version: Apache Software Foundation Apache TomEE 10.0.0-M1, 10.3.0, 11.0.0-M2.
Low priority for now. Upgrade to Apache Software Foundation Apache TomEE 10.0.0-M1, 10.3.0, 11.0.0-M2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Nov 10, 2026
- Updated
- Nov 12, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-287
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.
Apache Software Foundation Apache TomEE
- 4.0.0-beta-1 and later · up to and including 4.7.5affected · semver
- 7.0.0-M1 and later · before 10.0.0-M1affected · semver
- 10.0.0-M1 and later · before 10.3.0affected · semver
- 11.0.0-M1 and later · before 11.0.0-M2affected · semver
Same product
apache software foundation: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-97890Apache TomEE: Session fixation in embedded HTTP server0Monitor
- CVE-2026-97888Apache TomEE: Caller identity leaks across requests in embedded HTTP server0Monitor
- CVE-2026-97881Apache TomEE: Path traversal in embedded HTTP server static resource handling0Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-87756Nov 10, 2026 · Apache TomEE: Missing authorization on internal deployer EJBs in default profile0Monitor
- ← EarlierCVE-2026-111239Nov 10, 2026 · Apache TomEE: Code execution by any authenticated user via the SSH administration shell0Monitor
- Later →CVE-2026-111241Nov 10, 2026 · Apache TomEE: Local code execution via predictable passivation files in the shared temporary directory0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Apache Software Foundation Apache TomEE | 10.0.0-M1 | Vendor (CNA) |
| Apache Software Foundation Apache TomEE | 10.3.0 | Vendor (CNA) |
| Apache Software Foundation Apache TomEE | 11.0.0-M2 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 13, 2026+3 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- The Apache Software Foundationfinder
- Claude Securitytool
- Richard Zowallaremediation developer
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-1112500 days apartApache TomEE: Authentication bypass via programmatic authentication in embedded HTTP server0Monitor
- CVE-2026-1112610 days apartApache TomEE: Authentication bypass with empty password in LDAP identity store0Monitor
- CVE-2026-978740 days apartApache TomEE: Authentication bypass for Hessian endpoints in non-root web applications0Monitor
- CVE-2026-978800 days apartApache TomEE: Authentication bypass in the embedded HTTP server for endpoints protected by HTTP Basic authentication0Monitor
Not on record for this CVE: patch commit or PR link · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
CWE-287 · Improper AuthenticationRoot cause
Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middleware
app.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();
admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);
app.use("/admin", admin);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
Change log (2)
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.