High [CVE-2026-95863] Improper neutralization of input during web page generation in Apache Wicket
This high-severity Apache Software Foundation advisory covers CVE-2026-95863 affecting Apache Wicket.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Get an email when Apache Software Foundation publishes the next one.
See Apache Software Foundation's last 90 days of advisories first. Then choose the free weekly digest, or a free month of real-time alerts with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
Summary
Improper neutralization of input during web page generation in Apache Wicket.
Apache Wicket generates JavaScript that refers to the elements it renders, writes into that JavaScript two values it derives itself: a component's markup
id, and the input name of a form component, which is built from component ids. Both are placed inside single-quoted JavaScript string literals without being
escaped for that context, so a value containing a single quote or a backslash ends the literal, and what follows is parsed as script and runs in the
application's origin when the page loads.
A markup id is the value passed to org.apache.wicket. Component#setMarkupId(String),
or the id attribute written in the component's markup, or an id Wicket generates, in that order.
The first two are supplied by the application in an HTML context, where both characters are legal and where Wicket escapes them
correctly when it writes the same value into the id attribute of the element; a generated id cannot contain either.
components between the form and the form component, and a component id was rejected only for ':' and '~'.
In org.apache.wicket:wicket-core on 9.x and 10.x, org.apache.wicket.markup.head.OnEventHeaderItem#forMarkupId(String, String,
CharSequence) quotes the id it is given into a Wicket. Event.add call,
components in both wicket-core and wicket-extensions reach it through
- 8.0.0 through 8.19.0
- 9.0.0 through 9.24.0
- 10.0.0 through 10.11.0.
- through 10.11.0
Official advisory · high-confidence parse· fetched 6 hours ago·verify at source
- 8.20.0
- 9.25.0
- 10.12.0
Official advisory · high-confidence parse· fetched 6 hours ago·verify at source
Mitigation checklist
- Users of Apache Wicket 7.x or older, which are no longer supported, should upgrade to a supported version.
- Users are recommended to upgrade to version 8.20.0, 9.25.0 or 10.12.0, which fix the issue.
Official advisory · high-confidence parse· fetched 6 hours ago·verify at source
More Apache Software Foundation advisories
- CVE-2026-111089Nov 1, 2026Apache Wicket reads texts from the application's resource bundles — a localized label
- CVE-2026-87718Nov 1, 2026Apache Wicket 10.10.0, 10.11.0 and 9.24.0 do not set the Content-Security-Policy headers
- CVE-2026-84231Nov 1, 2026Apache Wicket cross-site scripting (XSS)
- CVE-2026-84177Nov 1, 2026Incorrect behavior order in Apache Wicket: a file path is validated before the framework
- CVE-2026-84172Nov 1, 2026Files accessible to external parties in Apache Wicket
- CVE-2026-84170Nov 1, 2026Allocation of resources without limits or throttling in Apache Wicket
Android app · Google Play
Monitor future Apache Software Foundation CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.