Skip to main content
VulnerabilityPublished

CVE-2026-82557: Apache Wicket · Missing Authorization

Affects Apache WicketSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.9 Medium · fixed in 10.12.0 : update Apache Wicket when convenient.

Data as of 1 Nov 2026, 22:28 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (apache)CVSS 4.06.9
Patch
Available – fixed in 10.12.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Apache Wicketorg.apache.wicket:wicket-coreAffected
  • >=10.3.0 <=10.11.0
Fixed in–
Mavenorg.apache.wicket/wicket-corepkg:maven/org.apache.wicket/wicket-coreOther threatsAffected
  • >=10.3.0 <=10.11.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Apache Wicket to version 10.12.0 or later, where this issue is fixed. No other mitigation or workaround is indicated in the advisory.

Description

CVE-2026-82557 is a missing authorization vulnerability in Apache Wicket versions 10.3.0 through 10.11.0. It allows a form submitting component that is supposed to be unavailable (e.g., hidden or disabled) to be invoked by a crafted request, bypassing visibility and enablement checks. This can lead to unauthorized execution of the component's submit handlers without proper validation. The issue was introduced in version 10.3.0 and fixed in 10.12.0.

References

Community reviews

Loading reviews…