CVE-2026-40010: Apache Wicket session fixation in AuthenticatedWebSession

CVE-2026-40010 · Severity: critical · CVSS 9.1 · Published 2026-05-06

Apache Wicket, a popular framework for building Java-based web applications, contains a security flaw that could allow an attacker to hijack a user's session. By fixing a session ID before a user logs in, an attacker can gain unauthorized access to the user's account and sensitive data once they authenticate. This could lead to full account takeover and the exposure of private customer information.

Technologies: Apache Wicket, Apache Software Foundation Wicket. Vendors: Apache, Apache Software Foundation, Maven.

Quick answers

Is CVE-2026-40010 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-40010 being exploited in the wild.
How severe is CVE-2026-40010?
Critical severity, with a CVSS score of 9.1, published 6 May 2026.
Which products and versions are affected?
Apache Software Foundation Wicket 8.0.0 through 8.17.0, 9.0.0 through 9.22.0, 10.0.0 through 10.8.0; org.apache.wicket:wicket-auth-roles (Maven) ECOSYSTEM:introduced=8.0.0-M1,last_affected=8.17.0.
Is there a fix for CVE-2026-40010?
A patch was published on 2026-05-11: Advisory updated with patch information Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-40010 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-40010?
Check whether you run Apache Wicket, Apache Software Foundation Wicket or org.apache.wicket:wicket-auth-roles (Maven) 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

A session fixation vulnerability exists in Apache Wicket's session management, specifically within the wicket-auth-roles component. The framework fails to invoke the Servlet 'changeSessionId' method after session binding occurs during the authentication process. An attacker can provide a known session identifier to a victim's browser; if the victim subsequently authenticates, the application continues to use the pre-existing session ID rather than generating a new one. This allows the attacker to use the known ID to impersonate the authenticated user. The issue is resolved in version 10.9.0.

Affected products

  • Apache Wicket 8.0.0 through 8.17.0, 9.0.0 through 9.22.0, 10.0.0 through 10.8.0

Identifiers

  • CVE-2026-40010
  • GHSA-qpjw-p3jg-59j6

Timeline

  • 2026-05-06: disclosed
  • 2026-05-06: advisory
  • 2026-05-11: patched: Advisory updated with patch information

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.