dbcve.org
WicketApplication · Apache

CVE-2026-40010

CRITICAL · 9.1 CVSS v3.1 Published 2026-05-06
Fix available
A fix is available. Upgrade to 10.9.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Missing invocation of Servlet http web request method changeSessionId after session binding can be exploited for a session fixation attack in Apache Wicket. This issue affects Apache Wicket: from 8.0.0 through 8.17.0, 9.0.0, from 10.0.0 through 10.8.0. Users are recommended to upgrade to version 10.9.0, which fixes the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Wicket fails to invoke HttpServletRequest.changeSessionId() after session binding during authentication, allowing attackers to pre-set session IDs and hijack authenticated sessions (session fixation).

MitigationUpgrade Apache Wicket to version 10.9.0 or later which implements the required changeSessionId() call after session binding.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WicketApplication
Affected:>= 8.0.0, <= 8.17.0>= 9.0.0, <= 9.22.0>= 10.0.0, < 10.9.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Wicket version
    Locate the wicket-core JAR file in your application dependencies (Maven pom.xml, Gradle build.gradle, or the deployed lib directory) and note the version number
    Affected if The installed version falls within 8.0.0-8.17.0, 9.0.0-9.22.0, or 10.0.0-10.8.x (any version below 10.9.0)
  2. Confirm session-based authentication is in use
    Review your application code to determine if user authentication creates or binds to an HTTP session (look for session.setAttribute() calls after login, or Session.get() usage in authentication handlers)
    Affected if Your application creates and binds user authentication state to an HTTP session after login
  3. Check for session ID regeneration after authentication
    Search codebase for explicit calls to request.changeSessionId() or HttpServletRequest.changeSessionId() occurring after login/authentication logic
    Affected if No such calls exist - the session ID is not being regenerated after user authentication
  4. Review session configuration
    Inspect your application's web.xml or servlet container configuration for session settings, and check if SessionFixationProtectionSessionStore is configured in your Wicket application
    Affected if Session fixation protection is not explicitly enabled in Wicket configuration

Your environment is affected if you run Apache Wicket below version 10.9.0 and your application uses session-based authentication without explicit session ID regeneration after login.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.9.0 or later
Fixed in 10.9.0
Interim mitigation

Upgrade Apache Wicket to version 10.9.0 or later which implements the required changeSessionId() call after session binding.

Recommended fix High confidence

Upgrade to Apache Wicket 10.9.0 (for 10.x branch) or latest 8.17.x/9.22.x stable release for respective branches

  1. Identify your current Apache Wicket version from your project's pom.xml or build.gradle dependency declaration
  2. Update the Wicket dependency version to 10.9.0 (for 10.x branch users) or to the latest 8.x/9.x stable release that includes the fix
  3. Run mvn clean compile or gradle build to verify the upgrade compiles successfully
  4. Review release notes for any migration considerations between your current and target version
  5. Test application functionality, particularly session handling and authentication flows, to ensure no regressions
  6. Deploy to staging environment and perform security validation before production release
Caveat Review Wicket 10.x migration guide as there may be API changes from 8.x/9.x branches; minor version upgrades within same branch typically have lower risk

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wicket Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,900
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,640.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40010 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40010 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data