cve.bz

CVE-2026-97891 eclipse foundation eclipse kura: Uncontrolled Resource Consumption

8.8 highEPSS 0.3%

High (8.8) in eclipse foundation eclipse kura. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
In Eclipse Kura version 5.0.0 to 5.6.2, the Web Console allocates a new HTTP session for every request to its built-in authentication endpoints (/admin/auth, /admin/login/password, /admin/login/cert) before checking the HTTP method, parsing the request, or validating any submitted credentials, and does not limit how many such sessions can be allocated. An unauthenticated client that sends requests to these endpoints without honoring the returned session cookie can cause the server to allocate an unbounded number of sessions, exhausting the JVM heap and crashing the Kura process.

Severity

CVSS 4.0

8.8 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:L/SA:N
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 25th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-400 Uncontrolled Resource Consumption
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
Assigned by
eclipse (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-97891 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-97891?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-97891?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-97891 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-97891

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-97891](https://cve.bz/cve/badge/CVE-2026-97891.svg)](https://cve.bz/cve/CVE-2026-97891)

HTML:

<a href="https://cve.bz/cve/CVE-2026-97891"><img src="https://cve.bz/cve/badge/CVE-2026-97891.svg" alt="CVE-2026-97891"></a>

Affected

  • eclipse foundation:eclipse kura

Versions

From the CNA's record in the CVE List.

ProductAffected
Eclipse Foundation Eclipse Kurafrom 5.0.0 through 5.6.2

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON