High CWE-22 CVEs with a working exploit
7 CVEs, 6 protected by Waratek
Overview 7 matches · 6 protected · 0 exploited · 0 CISA KEV · 2 EPSS ≥ 0.5
Protected by Waratek
6
85.7%
Rule in development
0
0.0%
Mitigation candidate
1
14.3%
No exploit published
0
0.0%
blocked by ARMR today
6
85.7%
partly blocked
0
0.0%
not blocked
1
14.3%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
7
100.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
0
0.0%
split by
peak 2 / year
20091
Protected by Waratek1
High1
blocked by ARMR today1
Working exploit published1
20100
20110
20120
20130
20140
20150
20161
Protected by Waratek1
High1
blocked by ARMR today1
Working exploit published1
20170
20180
20190
20200
20210
20222
Protected by Waratek2
High2
blocked by ARMR today2
Working exploit published2
20230
20241
Protected by Waratek1
High1
blocked by ARMR today1
Working exploit published1
20250
20262
Protected by Waratek1
Mitigation candidate1
High2
blocked by ARMR today1
not blocked1
Working exploit published2
201020122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-55552 | High | 2026-08-28 | Protected by Waratek | Working exploit published | Yamcs is a mission control framework. Prior to 5.11.13, Yamcs StaticFileHandler.locateFile resolves an unauthenticated request path without using Path.normalize and Path.toAbsolutePath to confirm that the absolute path remains within the configured staticRoots. A path containing traversal segments can escape the intended web root and return an arbitrary readable host file. The flaw is in yamcs-core/src/main/java/org/yamcs/http/StaticFileHandler.java and can disclose sensitive operating-system and application data. This issue is fixed in version 5.11.13, and the 5.12 line is fixed from version 5.12.0. |
| CVE-2026-22739 | High | 2026-03-24 | Mitigation candidate | Working exploit published | Vulnerability in Spring Cloud when substituting the profile parameter from a request made to the Spring Cloud Config Server configured to the native file system as a backend, because it was possible to access files outside of the configured search directories.This issue affects Spring Cloud: from 3.1.X before 3.1.13, from 4.1.X before 4.1.9, from 4.2.X before 4.2.3, from 4.3.X before 4.3.2, from 5.0.X before 5.0.2. |
| CVE-2024-38819 | High | 2024-12-19 | Protected by Waratek | Working exploit published | Applications serving static resources through the functional web frameworks WebMvc.fn or WebFlux.fn are vulnerable to path traversal attacks. An attacker can craft malicious HTTP requests and obtain any file on the file system that is also accessible to the process in which the Spring application is running. |
| CVE-2022-31268 | High | 2022-05-21 | Protected by Waratek | Working exploit published | A Path Traversal vulnerability in Gitblit 1.9.3 can lead to reading website files via /resources//../ (e.g., followed by a WEB-INF or META-INF pathname). |
| CVE-2021-44138 | High | 2022-04-04 | Protected by Waratek | Working exploit published | There is a Directory traversal vulnerability in Caucho Resin, as distributed in Resin 4.0.52 - 4.0.56, which allows remote attackers to read files in arbitrary directories via a ; in a pathname within an HTTP request. |
| CVE-2016-0709 | High | 2016-04-11 | Protected by Waratek | Working exploit published | Directory traversal vulnerability in the Import/Export function in the Portal Site Manager in Apache Jetspeed before 2.3.1 allows remote authenticated administrators to write to arbitrary files, and consequently execute arbitrary code, via a .. (dot dot) in a ZIP archive entry, as demonstrated by "../../webapps/x.jsp." |
| CVE-2008-5518 | High | 2009-04-17 | Protected by Waratek | Working exploit published | Multiple directory traversal vulnerabilities in the web administration console in Apache Geronimo Application Server 2.1 through 2.1.3 on Windows allow remote attackers to upload files to arbitrary directories via directory traversal sequences in the (1) group, (2) artifact, (3) version, or (4) fileType parameter to console/portal//Services/Repository (aka the Services/Repository portlet); the (5) createDB parameter to console/portal/Embedded DB/DB Manager (aka the Embedded DB/DB Manager portlet); or the (6) filename parameter to the createKeystore script in the Security/Keystores portlet. |