Overview 7 matches · 0 in Waratek scope · 0 protected · 4 exploited · 3 CISA KEV · 2 EPSS ≥ 0.5
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
0
0.0%
Not applicable
7
100.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
7
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
4
57.1%
Working exploit published
2
28.6%
Proof of concept only
1
14.3%
Forecast only
0
0.0%
No public exploit
0
0.0%
split by
peak 3 / year
20181
Not applicable1
Critical1
not blocked1
Working exploit published1
20191
Not applicable1
Critical1
not blocked1
Exploited1
20202
Not applicable2
Critical1
High1
not blocked2
Working exploit published1
Proof of concept only1
20210
20220
20230
20240
20250
20263
Not applicable3
Critical1
High2
not blocked3
Exploited3
201820192020202120222023202420252026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-82329 | Critical | 2026-08-28 | Not applicable | Exploited | JFrog Artifactory contains an authentication weakness that, under default configuration, may allow an unauthenticated attacker with network access to obtain administrative privileges. |
| CVE-2026-42018 | High | 2026-08-12 | Not applicable | Exploited | JFrog Artifactory could return an internal anonymous-user token to an unauthenticated caller when anonymous access is disabled, potentially exposing sensitive resources. |
| CVE-2026-42016 | High | 2026-07-27 | Not applicable | Exploited | JFrog Artifactory (Self Hosted) versions before 7.133.11 are vulnerable to a privilege escalation attack due to a validation check of the token signature/issuer and not the token’s scope. |
| CVE-2019-17444 | Critical | 2020-10-12 | Not applicable | Working exploit published | Jfrog Artifactory uses default passwords (such as "password") for administrative accounts and does not require users to change them. This may allow unauthorized network-based attackers to completely compromise of Jfrog Artifactory. This issue affects Jfrog Artifactory versions prior to 6.17.0. |
| CVE-2020-7931 | High | 2020-01-23 | Not applicable | Proof of concept only | In JFrog Artifactory 5.x and 6.x, insecure FreeMarker template processing leads to remote code execution, e.g., by modifying a .ssh/authorized_keys file. Patches are available for various versions between 5.11.8 and 6.16.0. The issue exists because use of the DefaultObjectWrapper class makes certain Java functions accessible to a template. |
| CVE-2019-9733 | Critical | 2019-04-11 | Not applicable | Exploited | An issue was discovered in JFrog Artifactory 6.7.3. By default, the access-admin account is used to reset the password of the admin account in case an administrator gets locked out from the Artifactory console. This is only allowable from a connection directly from localhost, but providing a X-Forwarded-For HTTP header to the request allows an unauthenticated user to login with the default credentials of the access-admin account while bypassing the whitelist of allowed IP addresses. The access-admin account can use Artifactory's API to request authentication tokens for all users including the admin account and, in turn, assume full control of all artifacts and repositories managed by Artifactory. |
| CVE-2016-10036 | Critical | 2018-05-01 | Not applicable | Working exploit published | Unrestricted file upload vulnerability in ui/artifact/upload in JFrog Artifactory before 4.16 allows remote attackers to (1) deploy an arbitrary servlet application and execute arbitrary code by uploading a war file or (2) possibly write to arbitrary files and cause a denial of service by uploading an HTML file. |