Overview 102 matches · 101 protected · 5 exploited · 2 CISA KEV · 6 public PoC · 3 EPSS ≥ 0.5
Protected by Waratek
102
100.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
blocked by ARMR today
101
99.0%
partly blocked
1
1.0%
not blocked
0
0.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 19 / month
Apr 2619
Protected by Waratek19
Critical6
High11
Medium2
blocked by ARMR today19
Exploited2
Working exploit published1
Proof of concept only1
No public exploit15
May 268
Protected by Waratek8
Critical4
High1
Medium2
Low1
blocked by ARMR today8
Proof of concept only2
No public exploit6
Jun 2614
Protected by Waratek14
Critical5
High7
Medium1
Low1
blocked by ARMR today14
Exploited1
No public exploit13
Jul 2617
Protected by Waratek17
Critical6
High11
blocked by ARMR today17
Exploited1
No public exploit16
Aug 2614
Protected by Waratek14
Critical5
High6
Medium2
Low1
blocked by ARMR today14
No public exploit14
Sep 2610
Protected by Waratek10
Critical3
High6
Medium1
blocked by ARMR today10
No public exploit10
Oct 2614
Protected by Waratek14
Critical5
High5
Medium4
blocked by ARMR today14
Proof of concept only3
No public exploit11
Nov 266
Protected by Waratek6
Critical1
High3
Unknown2
blocked by ARMR today5
partly blocked1
Exploited1
No public exploit5
Apr 26May 26Jun 26Jul 26Aug 26Sep 26Oct 26Nov 26
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-34197 | High | 2026-04-07 | Protected by Waratek | Exploited | Improper Input Validation, Improper Control of Generation of Code ('Code Injection') vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ. Apache ActiveMQ Classic exposes the Jolokia JMX-HTTP bridge at /api/jolokia/ on the web console. The default Jolokia access policy permits exec operations on all ActiveMQ MBeans (org.apache.activemq:*), including BrokerService.addNetworkConnector(String) and BrokerService.addConnector(String). An authenticated attacker can invoke these operations with a crafted discovery URI that triggers the VM transport's brokerConfig parameter to load a remote Spring XML application context using ResourceXmlApplicationContext. Because Spring's ResourceXmlApplicationContext instantiates all singleton beans before the BrokerService validates the configuration, arbitrary code execution occurs on the broker's JVM through bean factory methods such as Runtime.exec(). This issue affects Apache ActiveMQ Broker: before 5.19.4, from 6.0.0 before 6.2.3; Apache ActiveMQ All: before 5.19.4, from 6.0.0 before 6.2.3; Apache ActiveMQ: before 5.19.4, from 6.0.0 before 6.2.3. Users are recommended to upgrade to version 5.19.4 or 6.2.3, which fixes the issue |
| CVE-2026-33439 | Critical | 2026-04-07 | Protected by Waratek | Working exploit published | Open Access Management (OpenAM) is an access management solution. Prior to 16.0.6, OpenIdentityPlatform OpenAM is vulnerable to pre-authentication Remote Code Execution (RCE) via unsafe Java deserialization of the jato.clientSession HTTP parameter. This bypasses the WhitelistObjectInputStream mitigation that was applied to the jato.pageSession parameter after CVE-2021-35464. An unauthenticated attacker can achieve arbitrary command execution on the server by sending a crafted serialized Java object as the jato.clientSession GET/POST parameter to any JATO ViewBean endpoint whose JSP contains <jato:form> tags (e.g., the Password Reset pages). This vulnerability is fixed in 16.0.6. |