PatchTheCVEwicket vulnerabilities and fixes
Recent CVEs affecting wicket, with upgrade or downgrade steps. 2 tracked.
wicket has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 2. Most recent: 2026-07-27. Highest priority: CVE-2026-66391 (score 45/100).
- CVE-2026-66391 MEDIUM 6.5 UPGRADE Use of Insufficiently Random Values, Protection Mechanism Failure vulnerability in Apache Wicket. This issue
- CVE-2026-66390 MEDIUM 6.1 UPGRADE Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Apache W
FAQ
How do I fix wicket vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is wicket being exploited right now?
None of the tracked wicket CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which wicket CVE should I patch first?
CVE-2026-66391 currently ranks highest (45/100): Use of Insufficiently Random Values, Protection Mechanism Failure vulnerability in Apache Wicket. This issue .