WicketApplication · Apache
CVE-2026-43646
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 · uneditedExposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Wicket. This issue affects Apache Wicket: from 8.0.0 through 8.17.0, from 9.0.0 through 9.22.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 · moderate confidenceApache Wicket contains an information disclosure vulnerability where sensitive information may be exposed to unauthorized actors. This affects multiple version branches (8.x, 9.x, and 10.x) within the specified ranges.
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
>= 8.0.0, <= 8.17.0>= 9.0.0, <= 9.22.0>= 10.0.0, < 10.9.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Apache Wicket version via Maven POMInspect your project's pom.xml file and locate the wicket-core dependency. Run 'mvn dependency:tree | grep wicket' or check the version directly in the <version> tag of the wicket-core dependency.Affected if The wicket-core version falls within 8.0.0 to 8.17.0, 9.0.0 to 9.22.0, or 10.0.0 to 10.8.x (anything below 10.9.0)
-
Check Wicket JAR manifestLocate the wicket-core JAR file in your classpath or WEB-INF/lib directory. Use 'jar tf wicket-core-X.jar | grep MANIFEST.MF' to extract the manifest, or inspect the JAR properties in your IDE or build tool.Affected if The version number in the JAR manifest matches the affected ranges in step 1
-
Verify runtime version programmaticallyIf the application is running, check the version at runtime by inspecting org.apache.wicket.Application.getFrameworkVersion() or by checking the package implementation version via Class.getResource("org/apache/wicket/Application.class").Affected if The runtime-reported version falls within any of the affected version ranges
If the deployed Apache Wicket version is 8.0.0 through 8.17.0, 9.0.0 through 9.22.0, or 10.0.0 through 10.8.x (i.e., any version below 10.9.0 in those branches), the environment is affected by this information disclosure vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.9.0
Upgrade Apache Wicket to version 10.9.0 or later. For users on 8.x and 9.x branches, upgrade to the latest available patched versions in those respective branches.
10.9.0
- 1. Identify the current Apache Wicket version in use by checking project dependencies (e.g., pom.xml for Maven, build.gradle for Gradle, or equivalent
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wicket
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-43646 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-43646 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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