CVE-2026-84172
Publiée le 2026-11-01 · Dernière modification le 2026-11-02
Apache Wicket (versions 8.0.0–8.19.0, 9.0.0–9.24.0 et 10.0.0–10.11.0) est un framework Java utilisé pour créer des applications web. Une faille existe dans la manière dont le framework détermine quels fichiers internes peuvent être envoyés en toute sécurité au navigateur d'un utilisateur. Dans certaines configurations de serveur — par exemple, lorsque le framework est placé dans un répertoire de bibliothèque partagée — le système ne reconnaît pas certains modèles de balisage internes comme étant protégés, permettant ainsi qu'ils soient servis comme des fichiers statiques.
Un attaquant non authentifié disposant d'un accès réseau peut télécharger ces fichiers de modèles pour consulter la structure interne de l'application, les commentaires des développeurs et les points de terminaison d'API. Cela impacte la confidentialité en exposant le « schéma » du site, bien que cela ne donne pas accès aux données des utilisateurs, aux mots de passe ou aux jetons de session. L'exploitation est relativement facile à exécuter, à condition que le serveur utilise l'une des architectures de déploiement rares et affectées.
DÉTAIL DU VECTEUR CVSS
RÉFÉRENCES
Description officielle du NVD (en anglais)
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.