CVE-2026-84170

Apache Wicket: Configured upload limits are not enforced by the standalone file upload resource

Published Nov 1, 2026 CVSS 4.0 · 8.3 High EPSS < 1% KEV · Not listed
Description
Allocation of resources without limits or throttling in Apache Wicket.

org.apache.wicket.markup.html.form.upload.resource.AbstractFileUploadResource is the server side of the form-less upload offered by FileUploadToResourceField, which posts the selected files to a separately mounted resource rather than through a Form. The resource is an application-wide singleton with no component to consult, so newResourceResponse() takes the three limits that bound the upload - the total request size, the maximum size of a single part and the maximum number of parts - from the request parameters maxSize, fileMaxSize and fileCountMax, and hands them to the multipart parser as they arrive. Nothing binds those numbers to the field that is supposed to be uploading. A request naming a very large maxSize is therefore parsed with no effective ceiling on the total size, and omitting fileMaxSize and fileCountMax leaves the per-part and part-count limits unset as well. The values the application configured through FileUploadToResourceField#setMaxSize(), #setFileMaxSize() and #setFileCountMax() are consulted only when the client omits the corresponding parameter, so against a client that supplies one they have no effect at all.

Parts above the parser's in-memory threshold are spooled to the container's temporary directory, and the file parts are then copied into the folder the application's IUploadsFileManager owns, under a sub-folder the request names, where they remain. A part that is not a file is read into the heap in full while the request is parsed. One request, repeatable, can therefore consume as much disk or as much heap as the client chooses to send. The resource carries no authorization annotation and the default authorization strategy permits every resource request, so unless the application authorizes the resource itself the request needs no authentication, no session, no prior page view and no user interaction.

An application is affected where it uses FileUploadToResourceField, or mounts FileUploadResourceReference itself. This is not the ordinary upload path: the resource is a singleton that has to be created and mounted deliberately. An application that configures no upload limit at all loses nothing, because Wicket applies no total-size limit of its own by default; what the defect removes is a limit the application set. Uploads through Form with FileUploadField, and through AjaxFileDropBehavior, are not affected, because both read their limits from the component rather than from the request. The upload resource does not exist in the 8.x line.

This issue affects Apache Wicket: from 9.14.0 through 9.24.0, from 10.0.0 through 10.9.1. Users are recommended to upgrade to version 9.25.0 or 10.12.0, which fix the issue.

Analysis

AI-generated

Technical impact

Apache Wicket’s form‑less upload resource fails to honour limits configured in the application, allowing an attacker to supply arbitrarily large maxSize, fileMaxSize, or fileCountMax values. The server accepts the request without any ceiling, spooling data above the in‑memory threshold to the container’s temporary directory and finally copying file parts to the application’s upload folder. Because the parser accepts all data, a single request can consume unlimited disk or heap space, leading to performance degradation, crashes, or denial of service.

Affected Systems

The flaw exists in Apache Wicket versions 9.14.0 through 9.24.0 and 10.0.0 through 10.9.1. Those applications that use FileUploadToResourceField or mount FileUploadResourceReference are vulnerable. The issue does not impact the upload mechanisms that use FileUploadField or AjaxFileDropBehavior, nor does it affect the 8.x series.

Risk and Exploitability

The vulnerability has a CVSS score of 8.3 and no EPSS data is available. It is not listed in the CISA Known Exploited Vulnerabilities catalog. The resource is publicly accessible and carries no authorization annotation, so an unauthenticated attacker can reach the endpoint via HTTP. By sending a crafted payload that sets a very large maxSize (and omitting fileMaxSize and fileCountMax), the attacker can make the server allocate as much memory and disk space as desired, causing an availability loss.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache Wicket to version 9.25.0 or later 10.12.0 or later, which enforces the configured limits.
  • If the upload resource is not required, remove or disable the mounting of FileUploadResourceReference in the application configuration.
  • Implement a defensive check in your application to reject requests that contain large maxSize, fileMaxSize, or fileCountMax values, or override the upload size limits at the servlet level to enforce hard caps on memory and disk usage.

Generated by OpenCVE AI on November 1, 2026 at 23:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Apache
Apache wicket
Vendors & Products Apache
Apache wicket
Type Values Removed Values Added
Description Allocation of resources without limits or throttling in Apache Wicket. org.apache.wicket.markup.html.form.upload.resource.AbstractFileUploadResource is the server side of the form-less upload offered by FileUploadToResourceField, which posts the selected files to a separately mounted resource rather than through a Form. The resource is an application-wide singleton with no component to consult, so newResourceResponse() takes the three limits that bound the upload - the total request size, the maximum size of a single part and the maximum number of parts - from the request parameters maxSize, fileMaxSize and fileCountMax, and hands them to the multipart parser as they arrive. Nothing binds those numbers to the field that is supposed to be uploading. A request naming a very large maxSize is therefore parsed with no effective ceiling on the total size, and omitting fileMaxSize and fileCountMax leaves the per-part and part-count limits unset as well. The values the application configured through FileUploadToResourceField#setMaxSize(), #setFileMaxSize() and #setFileCountMax() are consulted only when the client omits the corresponding parameter, so against a client that supplies one they have no effect at all. Parts above the parser's in-memory threshold are spooled to the container's temporary directory, and the file parts are then copied into the folder the application's IUploadsFileManager owns, under a sub-folder the request names, where they remain. A part that is not a file is read into the heap in full while the request is parsed. One request, repeatable, can therefore consume as much disk or as much heap as the client chooses to send. The resource carries no authorization annotation and the default authorization strategy permits every resource request, so unless the application authorizes the resource itself the request needs no authentication, no session, no prior page view and no user interaction. An application is affected where it uses FileUploadToResourceField, or mounts FileUploadResourceReference itself. This is not the ordinary upload path: the resource is a singleton that has to be created and mounted deliberately. An application that configures no upload limit at all loses nothing, because Wicket applies no total-size limit of its own by default; what the defect removes is a limit the application set. Uploads through Form with FileUploadField, and through AjaxFileDropBehavior, are not affected, because both read their limits from the component rather than from the request. The upload resource does not exist in the 8.x line. This issue affects Apache Wicket: from 9.14.0 through 9.24.0, from 10.0.0 through 10.9.1. Users are recommended to upgrade to version 9.25.0 or 10.12.0, which fix the issue.
Title Apache Wicket: Configured upload limits are not enforced by the standalone file upload resource
Weaknesses CWE-770
References
Metrics cvssV4_0

{'score': 8.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Nov 6, 2026, 2:44 PM
Reserved
Sep 1, 2026, 8:20 AM
Status
Deferred
Published
Nov 1, 2026, 11:17 PM
Modified
Nov 6, 2026, 3:17 PM