CVE-2026-82840

Apache Wicket: The session id is renewed only on the first sign in, not on re-authentication

Published Nov 1, 2026 CVSS 4.0 · 7.2 High EPSS < 1% KEV · Not listed
Description
Session fixation in Apache Wicket.

org.apache.wicket.authroles.authentication.AuthenticatedWebSession is the authentication base class of Wicket's role-based security module, and its signIn(String, String) method is the entry point through which an application authenticates a session. Renewing the container session id at that point is the standard defence against an attacker who has fixed a session id in a victim's browser, and Wicket provides that renewal as org.apache.wicket.Session#changeSessionId(), whose documentation directs callers to invoke it on login for exactly that reason.

AuthenticatedWebSession#signIn(String, String) calls it inside a guard that succeeds only on the first transition of the session's signed-in flag. The session id is therefore renewed when a session first signs in, and is not renewed when a session that is already signed in authenticates again. signIn(String, String) returns true either way, so neither the caller nor the application can tell that the renewal did not happen.

An application is affected where it authenticates through AuthenticatedWebSession, which AuthenticatedWebApplication requires and which the shipped UsernamePasswordPanel uses, and where a session that is already signed in can authenticate again: a step-up prompt before a sensitive action, an account switch, or simply a sign-in form that stays reachable once the user is signed in. Nothing in the module hides that form from a signed-in session. Reaching the defect also requires an attacker to place a session id of their choosing in the victim's browser. JSESSIONID is set by the servlet container rather than by Wicket, so that needs a position Wicket does not grant, such as control of a host under the same registrable domain or a container configured to carry the session id in the URL, and the planted session has to be one the attacker has already signed in on, because a session that is not yet signed in does have its id renewed by the victim's authentication. An authentication attempt that fails signs the session out and closes the window. Applications that renew the session id in their own code after a successful authentication are not affected.

As a workaround, renew the session id from the application's own code on every successful authentication, by calling Session#changeSessionId() at the end of the authenticate(String, String) implementation.

This issue affects Apache Wicket: from 8.18.0 through 8.19.0, from 9.23.0 through 9.24.0, from 10.9.0 through 10.11.0.

Users are recommended to upgrade to version 8.20.0, 9.25.0 or 10.12.0, which fix the issue.

Analysis

AI-generated

Technical impact

A flaw in Apache Wicket’s authentication module means that when a user who has already signed into a session attempts to authenticate again—such as during a step‑up verification, account switch, or repeated submission of a sign‑in form—the framework will not regenerate the underlying session identifier. The session’s ID is only regenerated on the very first sign‑in. Because the sign‑in method returns true regardless of whether a renewal occurs, applications have no indication that the session ID has not been refreshed, allowing an attacker who can pre‑place a session identifier in a victim’s browser to force the victim to use that attacker‑controlled session and thereby hijack the session.

Affected Systems

The vulnerability affects Apache Wicket releases from 8.18.0 through 8.19.0, from 9.23.0 through 9.24.0, and from 10.9.0 through 10.11.0. Applications that use AuthenticatedWebSession with the default UsernamePasswordPanel and do not implement custom session‑ID renewal logic are vulnerable.

Risk and Exploitability

The CVSS score of 7.2 indicates a high‑severity vulnerability, but exploitation requires the attacker to supply a chosen session identifier in the victim’s browser. This can be achieved only if the attacker controls a host within the same registrable domain or if the servlet container forwards the session ID via the URL, which is not the default configuration. The EPSS score is not publicly available and the vulnerability is not listed in CISA’s KEV catalog, implying that there is currently no known widespread exploitation. Nonetheless, the lack of session renewal on re‑authentication could allow a remote attacker with domain or URL‑based session access to hijack an authenticated session, compromising both confidentiality and integrity of user data.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache Wicket to 8.20.0, 9.25.0 or 10.12.0 where the bug is fixed
  • If upgrading is not possible, modify the application to call Session#changeSessionId() at the end of every successful authentication routine
  • Ensure that the servlet container does not transmit the session identifier in the URL and that it is restricted to secure, HttpOnly cookies

Generated by OpenCVE AI on November 1, 2026 at 23:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Apache
Apache wicket
Vendors & Products Apache
Apache wicket
Type Values Removed Values Added
Description Session fixation in Apache Wicket. org.apache.wicket.authroles.authentication.AuthenticatedWebSession is the authentication base class of Wicket's role-based security module, and its signIn(String, String) method is the entry point through which an application authenticates a session. Renewing the container session id at that point is the standard defence against an attacker who has fixed a session id in a victim's browser, and Wicket provides that renewal as org.apache.wicket.Session#changeSessionId(), whose documentation directs callers to invoke it on login for exactly that reason. AuthenticatedWebSession#signIn(String, String) calls it inside a guard that succeeds only on the first transition of the session's signed-in flag. The session id is therefore renewed when a session first signs in, and is not renewed when a session that is already signed in authenticates again. signIn(String, String) returns true either way, so neither the caller nor the application can tell that the renewal did not happen. An application is affected where it authenticates through AuthenticatedWebSession, which AuthenticatedWebApplication requires and which the shipped UsernamePasswordPanel uses, and where a session that is already signed in can authenticate again: a step-up prompt before a sensitive action, an account switch, or simply a sign-in form that stays reachable once the user is signed in. Nothing in the module hides that form from a signed-in session. Reaching the defect also requires an attacker to place a session id of their choosing in the victim's browser. JSESSIONID is set by the servlet container rather than by Wicket, so that needs a position Wicket does not grant, such as control of a host under the same registrable domain or a container configured to carry the session id in the URL, and the planted session has to be one the attacker has already signed in on, because a session that is not yet signed in does have its id renewed by the victim's authentication. An authentication attempt that fails signs the session out and closes the window. Applications that renew the session id in their own code after a successful authentication are not affected. As a workaround, renew the session id from the application's own code on every successful authentication, by calling Session#changeSessionId() at the end of the authenticate(String, String) implementation. This issue affects Apache Wicket: from 8.18.0 through 8.19.0, from 9.23.0 through 9.24.0, from 10.9.0 through 10.11.0. Users are recommended to upgrade to version 8.20.0, 9.25.0 or 10.12.0, which fix the issue.
Title Apache Wicket: The session id is renewed only on the first sign in, not on re-authentication
Weaknesses CWE-384
References
Metrics cvssV4_0

{'score': 7.2, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Nov 6, 2026, 2:51 PM
Reserved
Aug 31, 2026, 8:07 AM
Status
Deferred
Published
Nov 1, 2026, 10:17 PM
Modified
Nov 6, 2026, 3:17 PM