Executive brief
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.
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
Timeline
- 2026-05-06: disclosed
- 2026-05-06: advisory
- 2026-05-11: patched: Advisory updated with patch information