# CVE-2026-83594 — Apache Wicket

> As of 2026-11-01, CVE-2026-83594 is a High-severity (band derived from the CVSS v4.0 score, not stated by the CNA) vulnerability in Apache Wicket, CVSS v4.0 8.3. No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-83594 as of 2026-11-01; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-11-01

## What is CVE-2026-83594?

Memory allocation with an excessive size value in Apache Wicket. org.apache.wicket.markup.html.form.upload.resource.FileUploadToResourceField uploads files to a separately mounted resource rather than through a form, and is told the outcome afterwards over its own Ajax callback. That callback reads the request parameter filesInfo, a JSON array carrying a client file name, a size and a content type for each file, and turns it into the list of FileUploadToResourceField.UploadInfo that onUploadSuccess() receives. Nothing binds that JSON to an upload the resource performed and nothing re-derives it from the stored files, so the number of entries and every value in them are whatever the request supplied. The callback URL is rendered into the page, no prior upload is required, and both GET and POST reach it, so any client that can load the page can have the component report files that were never uploaded, without authenticating beyond whatever the page itself requires and without any user interaction. UploadInfo#get(), which the class offers as the way to obtain the bytes of an upload, allocates a byte array from UploadInfo#getSize() before it opens the file. The array is therefore sized by the number the request supplied, and the allocation happens even for a file that was never stored. One small request can cost the server close to two gigabytes of heap, and the request is trivially repeatable, so a few of them exhaust the heap for every request the Java virtual machine is serving. A size that the conversion to int turns negative instead throws NegativeArraySizeException, which the exception handler inside that method does not cover, so it escapes into the application. An application is affected where it uses FileUploadToResourceField, which is not the ordinary upload path through FileUploadField and Form and has to be extended and mounted deliberately. The allocation additionally requires the application to call UploadInfo#get() rather than reading UploadInfo#getFile() itself. Where the application denies the ENABLE action on the field through its authorization strategy, the callback is refused like any other listener. The 8.x line does not contain this component and is not affected. This issue affects Apache Wicket: from 9.14.0 through 9.24.0, from 10.0.0 through 10.11.0. Users are recommended to upgrade to version 9.25.0 or 10.12.0, which fix the issue.

The record classifies CVE-2026-83594 under weakness class [CWE-789](https://cwe.mitre.org/data/definitions/789.html). 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 18 days ago.

## Severity and exploitation probability

- **CVSS v4.0 base score:** 8.3 — High (derived from score) (`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`)
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 4.2/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-11-01

## Is CVE-2026-83594 being exploited?

It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

## Affected products and versions

- [Apache Software Foundation](https://intel.threadlinqs.com/vendors/apache-software-foundation): Apache Wicket

## How to fix CVE-2026-83594

Vendor advisory: [https://lists.apache.org/thread.html/h5lxspxg746pzjd437n3n7mq5t3sfbcb](https://lists.apache.org/thread.html/h5lxspxg746pzjd437n3n7mq5t3sfbcb). Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

## Threat activity tracking CVE-2026-83594

No threat campaign in the Threadlinqs corpus currently references CVE-2026-83594, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, GitHub Security Advisories. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [lists.apache.org — vendor advisory](https://lists.apache.org/thread.html/h5lxspxg746pzjd437n3n7mq5t3sfbcb)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-83594
No Threadlinqs detection currently covers CVE-2026-83594; it is re-checked on every ingest.
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
