Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA apache

CVE-2026-86811: Apache TomEE: Path traversal via stateful EJB passivation

—No exploit Fix available

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.20% (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 stateful session bean passivation mechanism derives the on-disk file name from a client-supplied identifier without validating it. A remote attacker with access to the remote EJB service can cause session state to be read from or written to files outside the passivation directory. 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.2% · 11th percentile

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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.

Follow CVE-2026-86811

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi 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 help

Affected 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

Other highest-scoring records for the same primary product.

  • CVE-2026-97890Apache TomEE: Session fixation in embedded HTTP server
    0Monitor
  • CVE-2026-97888Apache TomEE: Caller identity leaks across requests in embedded HTTP server
    0Monitor
  • CVE-2026-97881Apache TomEE: Path traversal in embedded HTTP server static resource handling
    0Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-111264Nov 10, 2026 · Apache TomEE: Authentication bypass on EJB web service endpoints via HTTP method
    0Monitor
  • ← EarlierCVE-2026-86532Nov 10, 2026 · Apache TomEE: Username enumeration and timing side channel in JAAS login modules
    0Monitor
  • Later →CVE-2026-87755Nov 10, 2026 · Apache TomEE: Stateful session bean hijacking via predictable session identifiers
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Apache Software Foundation Apache TomEE10.0.0-M1Vendor (CNA)
Apache Software Foundation Apache TomEE10.3.0Vendor (CNA)
Apache Software Foundation Apache TomEE11.0.0-M2Vendor (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.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 13, 2026+3 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-978810 days apartApache TomEE: Path traversal in embedded HTTP server static resource handling
    0Monitor

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.

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records