---
id: CVE-2026-87718
title: >-
  Apache Wicket: CSP headers silently omitted for pages served through nested
  request handler delegates
summary: >-
  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 …
severity: low
cvss: 2.3
cvssVector: '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'
cvssSource: cna
cwe:
  - CWE-693
vendor: Apache Software Foundation
product: 'org.apache.wicket:wicket-core'
affected:
  - 'org.apache.wicket:wicket-core 9.24.0'
  - 'org.apache.wicket:wicket-core >= 10.10.0 <= 10.11.0'
published: '2026-11-01'
updated: '2026-11-01'
sourceUpdated: '2026-11-01T22:28:35.032Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-87718'
references:
  - url: 'https://lists.apache.org/thread.html/fjq8v35zpkbtjwpzwkkpzocwtdgokp1m'
tags:
  - cve.org
epss: 0.0029
epssPercentile: 0.21727
ingestedAt: '2026-11-05T19:30:42.614Z'
---

## Overview

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.

## Affected

- `org.apache.wicket:wicket-core 9.24.0`
- `org.apache.wicket:wicket-core >= 10.10.0 <= 10.11.0`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.