CVE-2026-82840 Apache Software Foundation CVE debrief

Who should care

Defenders responsible for Apache Wicket applications should assess exposure and prioritize upgrading to a fixed version. They should verify if their applications are affected and take necessary actions to mitigate the vulnerability. This includes renewing the session ID from the application's own code on every successful authentication or upgrading to a fixed version of Apache Wicket. Defenders should also review compensating controls for exposed systems,

Why it matters

A session fixation vulnerability in Apache Wicket's role-based security module allows an attacker to fixate a session ID in a victim's browser, potentially leading to unauthorized access. Defenders responsible for Apache Wicket applications should assess exposure and prioritize upgrading to a fixed version.

• An attacker can fixate a session ID in a victim's browser, potentially leading to unauthorized access
• Defenders must verify if their applications are affected and prioritize upgrading to a fixed version

Technical summary

The AuthenticatedWebSession class's signIn method does not renew the session ID when a user re-authenticates, allowing an attacker to fixate a session ID in a victim's browser. This issue affects Apache Wicket versions 8.18.0 through 8.19.0, 9.23.0 through 9.24.0, and 10.9.0 through 10.11.0. The vulnerability can be mitigated by renewing the session ID from the application's own code on every successful authentication or by upgrading to a fixed version of Apache Wicket. Defenders should prioritize upgrading to a fixed version of Apache Wicket, as this vulnerability can allow for session fixation attacks.

Defensive priority

Defenders should prioritize upgrading to a fixed version of Apache Wicket, as this vulnerability can allow for session fixation attacks.

Recommended defensive actions

• Upgrade to Apache Wicket version 8.20.0, 9.25.0, or 10.12.0
• Renew the session ID from the application's own code on every successful authentication
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance

Evidence notes

The CVE record and NVD vulnerability detail page provide information on the vulnerability, its impact, and affected versions. The AuthenticatedWebSession class's signIn method does not renew the session ID when a user re-authenticates, allowing an attacker to fixate a session ID in a victim's browser. This issue affects Apache Wicket versions 8.18.0 through 8.19.0, 9.23.0 through 9.24.0, and 10.9.0 through 10.11.0. Defenders should verify if their applications are affected and prioritize upgrading to a fixed version. Evidence limits:

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.