Reported exploits and new Apache Wicket flaws
Vulnerability roundup ·
In this episode
- GitLab bug under attack: what's new on the fix
- CVE-2026-82956: Apache Wicket
- CVE-2026-83594: Apache Wicket
- CVE-2026-84170: Apache Wicket
- CVE-2026-111089: Apache Wicket
- CVE-2026-95863: Apache Wicket
The facts
- Attackers are exploiting CVE-2026-97229, according to CISA, which added it to its Known Exploited Vulnerabilities catalog.
- Attackers are exploiting CVE-2026-111357, according to CISA.
- CVE-2026-82956 is a flaw in Apache Wicket.
- CVE-2026-83594 is a flaw in Apache Wicket.
- CVE-2026-84170 is a flaw in Apache Wicket.
- CVE-2026-111089 is a flaw in Apache Wicket.
- CVE-2026-95863 is a flaw in Apache Wicket.
- CVE-2026-82956 is classed as cross-site scripting (CWE-79).
- CVE-2026-83594 is classed as CWE-789 in MITRE's weakness list.
- CVE-2026-84170 is classed as resource allocation without limits (CWE-770).
- CVE-2026-111089 is classed as cross-site scripting (CWE-79).
- CVE-2026-95863 is classed as cross-site scripting (CWE-79).
Sources
The panel
Jordan Pike AI host
CISA says attackers are exploiting CVE-2026-97229, which it added to its Known Exploited Vulnerabilities catalog, and also CVE-2026-111357.
Dex Moreno AI analyst
Any internet-facing instance of the vulnerable software is now a prime target. Exploitation could let an attacker gain a foothold on the server.
Dex Moreno AI analyst
Looks like they’re treating the vulnerable service like an all-you-can-eat buffet.
Sam Kowalski AI analyst
Pull recent authentication and job logs, hunt for unexpected shell sessions, and isolate any compromised processes. Even if you don’t see a breach yet, assume the foothold could be present until you verify log retention.
Jordan Pike AI host
CVE-2026-83594 is a flaw in Apache Wicket and is classed as CWE-789.
Dex Moreno AI analyst
The flaw is linked to uncontrolled memory allocation, which may affect service stability on affected components.
Sam Kowalski AI analyst
Monitor for abnormal resource usage on affected servers and enable rate-limiting. If you can’t patch immediately, add a temporary resource cap as a compensating control.
Jordan Pike AI host
CVE-2026-84170 is a flaw in Apache Wicket and is classed as CWE-770, resource allocation without limits.
Dex Moreno AI analyst
The issue involves resource allocation without limits, which may impact the reliability of the service.
Sam Kowalski AI analyst
Correlate error logs with any abnormal activity. Deploy a watchdog to restart the service if it exceeds safe thresholds.
Jordan Pike AI host
CVE-2026-111089 is a flaw in Apache Wicket and is classed as cross-site scripting, CWE-79.
Dex Moreno AI analyst
An XSS bug lets a malicious user inject scripts into pages, potentially stealing session data.
Sam Kowalski AI analyst
Enable a web-application firewall rule that blocks script tags in user input and audit any recent admin sessions for suspicious activity.
Jordan Pike AI host
CVE-2026-95863 is a flaw in Apache Wicket and is classed as cross-site scripting, CWE-79.
Dex Moreno AI analyst
Another XSS vector, meaning any user-input field could be used to deliver malicious scripts.
Sam Kowalski AI analyst
Run a scanner for reflected script payloads and tighten content-security-policy headers to mitigate impact until a patch lands.
Jordan Pike AI host
CVE-2026-82956 is a flaw in Apache Wicket and is classed as cross-site scripting, CWE-79.
Dex Moreno AI analyst
Yet another XSS issue, reinforcing that Wicket deployments need a coordinated response: prioritize patching the most exposed instances first.
Sam Kowalski AI analyst
Check for any recent user-generated content that could have been used to deliver malicious scripts and rotate session keys as a precaution.
Jordan Pike AI host
So, for everyone whose Monday just got worse: here’s the version you can say out loud.
Jordan Pike AI host
Patch the exploited vulnerabilities immediately, schedule the Apache Wicket fixes according to exposure, and keep your logs and security controls tight.