Quick answers
- Is CVE-2026-97891 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-97891 being exploited in the wild.
- How severe is CVE-2026-97891?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Eclipse Kura 5.0.0 to 5.6.2.
- Is there a fix for CVE-2026-97891?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-97891 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-97891?
- Check whether you run Eclipse Kura at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the Web Console's authentication endpoints (/admin/auth, /admin/login/password, /admin/login/cert) which allocate HTTP sessions before validating HTTP methods, parsing requests, or checking credentials. An unauthenticated attacker can send rapid requests without honoring session cookies to trigger unbounded session allocation, causing JVM heap exhaustion (CWE-770, CWE-400). This is a network-accessible denial of service requiring no authentication or user interaction.
Affected products
- Eclipse Kura 5.0.0 to 5.6.2
Timeline
- 2026-11-10: disclosed