Live › vulnerability › CVE-2026-84172
When wicket-core runs in a class loader that cannot see the application's component classes, Wicket's package resource guard fails to recognise component markup templates and serves them as static files. An attacker who names a component class in the package resource URL can read that template, exposing developer comments, markup, inline script and endpoints, but not user data or credentials.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-01 23:22 UTC. All times on this page are UTC.
Only applications where wicket-core is loaded by a class loader that cannot see the application's component classes, such as a shared servlet container library, an EAR library with the application in the WAR, an application server global module, or an OSGi bundle. Standard WAR deployments with wicket-core in WEB-INF/lib are not affected. An attacker must name a component class in the package resource URL, which Wicket writes into rendered pages.
No product ranges from the sources yet.
wicket-core in pom.xml or build.gradle; affected versions are 8.0.0 through 8.19.0, 9.0.0 through 9.24.0, and 10.0.0 through 10.11.0.wicket-core is placed in a servlet container shared library directory, an EAR library directory with the application in the WAR, an application server global module, or an OSGi bundle; the exposure applies only to these layouts.wicket-core in WEB-INF/lib are not affected according to the sources.8.20.09.25.010.12.0Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Files accessible to external parties in Apache Wicket.
org.apache.wicket.markup.html.PackageResourceGuard decides whether a file on the classpath may be streamed to a client as a package resource. HTML is on the default allow list, so the only thing that separates a static HTML file, which may be served, from a component's markup template, which may not, is a check for a class file of the same name beside it. That check calls getResource() on the class loader that loaded wicket-core. The resource itself is reached through different class loaders: the scope class is resolved through the application's IClassResolver, which uses the thread context class loader, and org.apache.wicket.core.util.resource.ClassPathResourceFinder#find() then tries the scope class' own loader, the context class loader, and the wicket-core loader last.
Where wicket-core is loaded by a class loader that cannot see the application's classes, the check finds no class file, concludes the file is not a component markup template, and serves it. A request for the package resource URL of a component class then returns that component's markup template with status 200. What is disclosed is developer-authored template content: component structure, developer comments, markup that is rendered only under some conditions, inline script, and the endpoints a template names. Access is read-only, and no user data, credential or session material is reachable this way.
Such a deployment is rare. The ordinary packaging, a web archive with wicket-core in WEB-INF/lib, puts the framework and the application in one class loader, so the check finds the class file and the template is refused; those deployments are not affected. The exposure is confined to deployments that give wicket-core a class loader which cannot see the application's component classes: wicket-core placed in a servlet container's shared library directory, in an enterprise archive library directory with the application in the web archive, as an application server global module, or as an OSGi bundle, where wicket-core's bundle cannot resolve a class held by an application bundle. Markup shipped by Wicket's own modules, and by any other code sharing a class loader with wicket-core, remains protected. An attacker has to name a component class, and Wicket writes fully qualified class names into the URL of every package resource it renders.
This issue affects Apache Wicket: from 8.0.0 through 8.19.0, from 9.0.0 through 9.24.0, from 10.0.0 through 10.11.0. 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.
This page as .md · .json · in your agent: get_signal("CVE-2026-84172")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.