WaratekVRT Sign in
Reset
More filters (1)
Columns
Including CVEs outside Waratek scope✕Product ivy✕
Overview 9 matches · 5 in Waratek scope · 2 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
9matches 5in Waratek scope55.6% 2protected22.2% 0exploited0.0% 0CISA KEV0.0% 0public PoC0.0% 0EPSS ≥ 0.50.0%
Protected by Waratek 2 22.2% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 3 33.3% Outside Waratek scope 0 0.0% Not applicable 4 44.4% Withdrawn CVE 0 0.0%
Critical 0 0.0% High 0 0.0% Medium 9 100.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 2 22.2% partly blocked 0 0.0% not blocked 7 77.8% not established 0 0.0% unrecorded 0 0.0%
Exploited 0 0.0% Working exploit published 0 0.0% Proof of concept only 1 11.1% Forecast only 0 0.0% No public exploit 8 88.9%
split by peak 4 / year
Not applicable: 4No exploit published: 3Protected by Waratek: 2 Medium: 9 not blocked: 7blocked by ARMR today: 2 No public exploit: 8Proof of concept only: 1
20141 Not applicable1 Medium1 not blocked1 No public exploit1 20150 20160 20170 20180 20190 20200 20212 No exploit published1 Not applicable1 Medium2 not blocked2 No public exploit2 20221 Not applicable1 Medium1 not blocked1 No public exploit1 20231 No exploit published1 Medium1 not blocked1 No public exploit1 20240 20250 20264 Protected by Waratek2 No exploit published1 Not applicable1 Medium4 blocked by ARMR today2 not blocked2 Proof of concept only1 No public exploit3
2014201620182020202220242026
9 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed.
CVE Severity Published▾ Status Exploitation Description
CVE-2026-26032 Medium 2026-07-15 Protected by Waratek No public exploit The PackagerResolver of Apache Ivy is able to download online artifacts and to (re)package them in a format defined by a packager.xml file. This repackaging is done by an Ant script, which is stored in a subdirectory of the configured "buildRoot" directory. This subdirectory is calculated based on modules coordinates, like the organisation, name or version. If one of the coordinates contains "../" sequences - which are valid characters for Ivy coordinates in general- it is possible to break out of the configured "buildRoot" directory where other files can be overwritten. In order to exploit this vulnerability an attacker needs to have access to a packager repository and add or modify the coordinates in ivy.xml files to have such "../" sequences. Users of Apache Ivy 2.0.0 to 2.5.3 (inclusive) should upgrade to Ivy 2.6.0.
CVE-2026-54448 Medium 2026-06-25 Not applicable Proof of concept only Trivy is a security scanner. Prior to 0.71.0, when Trivy scans a Helm chart archive (.tgz), its custom tar unpacker reads each entry with io.ReadAll(tr) and no size limit. An attacker who can place a malicious .tgz file in the scanned path can craft a small compressed archive that decompresses to gigabytes, causing the Trivy process to be killed by the OS OOM killer. This vulnerability is fixed in 0.71.0.
CVE-2025-66249 Medium 2026-03-13 Protected by Waratek No public exploit Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache Livy. This issue affects Apache Livy: from 0.3.0 before 0.9.0. The vulnerability can only be exploited with non-default Apache Livy Server settings. If the configuration value "livy.file.local-dir-whitelist" is set to a non-default value, the directory checking can be bypassed. Users are recommended to upgrade to version 0.9.0, which fixes the issue.
CVE-2025-60012 Medium 2026-03-13 No exploit published No public exploit Malicious configuration can lead to unauthorized file access in Apache Livy. This issue affects Apache Livy 0.7.0 and 0.8.0 when connecting to Apache Spark 3.1 or later. A request that includes a Spark configuration value supported from Apache Spark version 3.1 can lead to users gaining access to files they do not have permissions to. For the vulnerability to be exploitable, the user needs to have access to Apache Livy's REST or JDBC interface and be able to send requests with arbitrary Spark configuration values. Users are recommended to upgrade to version 0.9.0 or later, which fixes the issue.
CVE-2023-41938 Medium 2023-09-06 No exploit published No public exploit A cross-site request forgery (CSRF) vulnerability in Jenkins Ivy Plugin 2.5 and earlier allows attackers to delete disabled modules.
CVE-2022-0697 Medium 2022-03-06 Not applicable No public exploit Open Redirect in GitHub repository archivy/archivy prior to 1.7.0.
CVE-2021-4162 Medium 2021-12-25 Not applicable No public exploit archivy is vulnerable to Cross-Site Request Forgery (CSRF)
CVE-2021-26544 Medium 2021-02-20 No exploit published No public exploit Livy server version 0.7.0-incubating (only) is vulnerable to a cross site scripting issue in the session name. A malicious user could use this flaw to access logs and results of other users' sessions and run jobs with their privileges. This issue is fixed in Livy 0.7.1-incubating.
CVE-2014-5886 Medium 2014-09-12 Not applicable No public exploit The iVysilani ceske televize (aka cz.motion.ivysilani) application 1.6 for Android does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate.