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…
Affects Eclipse Kura 5.0.0 through 5.6.2 where the Web Console's built-in authentication endpoints are in use. CVSS rates it High (8.8), and the checked facts list no vendor rating or fixed version.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The checked facts do not list a workaround or fix. Consult the Eclipse Kura advisory for mitigation guidance until a patched release is available.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 31/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Eclipse Kura's Web Console, in versions 5.0.0 through 5.6.2, can be made to crash by an attacker who sends unauthenticated requests over the network to its login endpoints, which causes it to allocate an unlimited number of HTTP sessions and exhaust the JVM heap. The attack requires no login and no user action.
Read the original description
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.8/10CVSS 8.8
- No patch5/5No patch listed yet
What would change the score
- Would score about 76 if added to CISA KEV
- Would score about 71 if CISA's SSVC rates exploitation active
- Would score about 36 if advisories confirm default setups are exposed
What to do
Workaround: The checked facts do not list a workaround or fix. Consult the Eclipse Kura advisory for mitigation guidance until a patched release is available.
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-97891 (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…), 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-97891 (entry last updated 2026-11-10): Affected: - Eclipse Foundation Eclipse Kura: from 5.0.0, through 5.6.2 Fixed versions: none listed yet. Conditions (all must be true for the bug to be hit): - Eclipse Kura version 5.0.0 to 5.6.2 (source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/325) - Uses the Web Console built-in authentication endpoints (/admin/auth, /admin/login/password, /admin/login/cert) (source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/325) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: network access, no login, no user action. CISA KEV: CVE-2026-97891 is not listed as of cve.now's last read. This KEV status is for CVE-2026-97891 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://github.com/eclipse-kura/kura/security/advisories/GHSA-4pwp-99h8-c44j - https://gitlab.eclipse.org/security/cve-assignment/-/work_items/325 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-97891 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-97891.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Eclipse Foundation Eclipse Kura
From 5.0.0 · through 5.6.2
Evidence 4
Vendor advisory · 2
Establishes: Affected and fixed versions.
- Advisory
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-97891
Is CVE-2026-97891 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
What does this mean?
The Web Console creates a new HTTP session for every request to its built-in authentication endpoints without limit. This can exhaust the JVM heap and crash the Kura process, causing a denial of service.Source: gitlab.eclipse.org
Which versions are affected by CVE-2026-97891?
Eclipse Kura: from 5.0.0 through 5.6.2.Source: cve.now feed data
Am I affected, and how do I check?
Eclipse Kura versions 5.0.0 through 5.6.2 are listed as affected. To check a installation, confirm the Kura version and whether the Web Console built-in authentication endpoints (/admin/auth, /admin/login/password, /admin/login/cert) are in use.Source: gitlab.eclipse.org
How do I fix CVE-2026-97891?
The checked facts do not name a fixed version, so no specific upgrade target is available from them. Check the Eclipse Kura advisory for a fixed release and any updated guidance.Source: gitlab.eclipse.org
What if there's no patch?
The checked facts do not list a workaround or fix. Consult the Eclipse Kura advisory for mitigation guidance until a patched release is available.Source: gitlab.eclipse.org