Vendor
80 published CVES affecting jfrog, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
Newest publication first · page 1 of 4
Potential arbitrary code execution under specific configurations. Updated October 22, 2026: Affected versions now include JFrog CLI v2.127.0. For remediation, update to v2.128.0 or later.
JFrog Artifactory contains an authentication weakness that, under default configuration, may allow an unauthenticated attacker with network access to obtain administrative privileges.
An authorization weakness in JFrog Artifactory Composer repository handling may allow an authenticated user, under specific conditions, to read package metadata from repositories they are not authorized to read. The issue affects confidentiality and has been addressed in fixed Ar...
Under specific circumstances, low-level user can run request to remote CocoaPods repos via JFrog Artifactory External Dependency.
An authenticated user may initiate repository migration operations without required repository permissions, potentially causing information disclosure, unauthorized state changes, and service disruption. Fixed versions address the issue.
A user who can read an existing remote VCS repository can replace its configured origin or supply an absolute VCS data URL.
A low-privileged user may poison cached artifact metadata under specific conditions, potentially causing consumers to retrieve untrusted content.
JFrog Artifactory could return an internal anonymous-user token to an unauthenticated caller when anonymous access is disabled, potentially exposing sensitive resources.
An unauthenticated user may access restricted artifacts in JFrog Artifactory under specific conditions.
An unauthenticated attacker may cause untrusted package content to be cached under specific conditions, potentially affecting artifact integrity and availability.
An authenticated user without repository read permission may access package metadata under specific conditions.
Under specific self-hosted Helm configurations, generated TLS private keys may be retained in rendered manifests accessible to highly privileged local users.
A holder of a valid integration credential may impersonate other users under specific conditions.
An anonymous caller when anonymous access is enabled, or a low-privilege authenticated user, may learn private Release Bundle names and versions when the bundle name is known.
An authenticated user may write data outside the intended Docker cache path under specific remote-repository conditions.
A low-privileged authenticated user may access restricted support information under specific conditions.
A low-privilege authenticated user may permanently remove protected internal metadata across repositories under specific conditions.
A user with access to a valid SAML response may impersonate another user under specific conditions.
A party with write access to stored session data may affect JFrog Artifactory under specific conditions.
An authenticated user may write files outside the intended Artifactory work directory under specific conditions.
A repository reader with cache-deploy permission may access content outside a configured upstream path under specific conditions.
An unauthenticated user may bypass authentication under specific cache conditions.
An authenticated user may view private Puppet module metadata without repository read access.
An authenticated user without repository read permission may access private NuGet metadata under specific conditions.
An unauthenticated user may access restricted repository information under specific conditions.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.