CVE-2026-97890 · Other
NO FIX YET
The embedded HTTP server does not invalidate the previous session identifier when an application changes the session ID, such as after login. An attacker who can plant a session ID in a victim's browser can take over that victim's authenticated session.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
The sources describe an embedded HTTP server that does not rotate session IDs when an application changes them, such as after login. Teams running applications on that embedded server are exposed if an attacker can plant a session ID in a user's browser. The sources name no affected versions and no product, so the exact scope is unknown.
Not affected if network-access-blocked-from-untrusted-clients
Who cares embedded-http-server, session-management
Unknown from the sources.
Unknown from the sources.
The embedded HTTP server does not invalidate the previous session identifier when an application changes the session id, e.g. after login. An attacker who can plant a session identifier in a victim's browser can hijack the victim's authenticated session. Users are recommended to block network access to the embedded HTTP server from untrusted clients, or to migrate to the Tomcat based TomEE distributions.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.