CVE-2026-82705 Apache Software Foundation CVE debrief

Who should care

Defenders responsible for Apache Wicket applications should assess exposure and prioritize upgrading to a fixed version or implementing a workaround to prevent potential security breaches. Defenders need to verify if their Apache Wicket applications are using a custom authorization strategy or @AuthorizeResource annotation and take action to prevent unauthorized access to restricted resources. Defenders should assess exposure and prioritize upgrading to a

Why it matters

The CVE-2026-82705 vulnerability in Apache Wicket allows unauthorized access to restricted resources when a custom authorization strategy or @AuthorizeResource annotation is used. Defenders should prioritize upgrading to a fixed version or implementing a workaround to prevent potential security breaches.

• Defenders need to verify if their Apache Wicket applications are using a custom authorization strategy or @AuthorizeResource annotation and take action to prevent unauthorized access to restricted resources.
• Defenders should assess exposure and prioritize upgrading to a fixed version or implementing a workaround to prevent potential security breaches.
• Defenders need to inventory their Apache Wicket applications and verify if they are using affected versions.

Technical summary

The vulnerability is caused by missing authorization in Apache Wicket. The IAuthorizationStrategy#isResourceAuthorized() method has a single enforcement point in the framework, but components that are handed an org.apache.wicket.request.resource.IResource instance instead call IResource#respond() themselves from their own request listener and never construct that handler. An application is affected where it restricts a resource through IAuthorizationStrategy#isResourceAuthorized() or an @AuthorizeResource annotation and then hands that same resource to one of those components as an IResource.

Defensive priority

Defenders should prioritize upgrading to version 8.20.0, 9.25.0, or 10.12.0. As a workaround, register the resource in the application's shared resources and pass the resulting ResourceReference to the component instead of the IResource.

Recommended defensive actions

• Upgrade to version 8.20.0, 9.25.0, or 10.12.0
• Register the resource in the application's shared resources and pass the resulting ResourceReference to the component instead of the IResource
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• 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.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, affected versions, and potential workarounds. The vulnerability 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. Defenders should verify if their Apache Wicket applications are using a custom authorization strategy or @AuthorizeResource annotation and take action to prevent unauthorized access to restricted resources.

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.