CVE-2026-84172 Apache Software Foundation CVE debrief

Who should care

Defenders responsible for Apache Wicket deployments, especially those with custom class loaders or shared library directories, should assess exposure and prioritize verification and remediation.

Why it matters

Defenders should care about CVE-2026-84172 because it allows disclosure of sensitive template content in certain Apache Wicket deployments, particularly those with custom class loaders. The vulnerability requires verification of exposure and remediation priority. Evidence is limited to a single source reference, and the CVE record has not been modified since publication.

• Read-only access to developer-authored template content
• Potential disclosure of component structure and developer comments
• Possible exposure of inline script and endpoints

Technical summary

The org.apache.wicket.markup.html.PackageResourceGuard in Apache Wicket incorrectly checks if a file on the classpath can be streamed to a client as a package resource. This leads to the disclosure of developer-authored template content in certain deployment configurations. The vulnerability is particularly relevant in deployments with custom class loaders or shared library directories. The issue affects Apache Wicket versions from 8.0.0 through 8.19.0, from 9.0.0 through 9.24.0, and from 10.0.0 through 10.11.0. Users are recommended to upgrade to version 8.20.0, 9.25.0, or 10.12.0, which fix the issue.

Defensive priority

Defenders should prioritize verifying exposure in Apache Wicket deployments, especially those with custom class loaders.

Recommended defensive actions

• Verify Apache Wicket version and deployment configuration
• Check for custom class loaders and shared library directories
• Upgrade to version 8.20.0, 9.25.0, or 10.12.0 if vulnerable
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, with evidence limited to a single source reference from [email protected]. The disclosure allows read-only access to developer-authored template content, including component structure, developer comments, markup rendered under certain conditions, inline script, and endpoints a template names. The issue requires verification of exposure and remediation priority, especially in deployments with custom class loaders or shared library directories.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.