Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconAuthenticate to IdP via existing account
-
DeliveryObtain valid SAML assertion from SSO flow
-
ExploitManipulate assertion NameID via signature wrapping
-
InstallSubmit crafted SAML response to Artifactory
-
C2Bypass signature verification
-
ExecuteReceive JWT token for impersonated user
-
ImpactAccess target user's artifacts and permissions
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Signature verification
|
| Exploitation Conditions | Exploitation requires SAML SSO to be configured and enabled in the Artifactory instance - deployments using only local or LDAP authentication are not affected. The attacker must have access to a valid SAML response, implying they either hold a legitimate user account in the federated identity provider or can intercept/capture an assertion in transit (e.g., via a man-in-the-middle position or session hijacking). The CVSS AC:H rating reflects that obtaining a valid SAML response is a non-trivial precondition. PR:L indicates the attacker must already have some authenticated foothold. Exploitation is limited by the requirement for SAML to be the active authentication method and by the need to possess or manipulate a legitimately issued assertion; unauthenticated external attackers with no IdP credentials cannot exploit this vulnerability. |
| Impact | The CVSS 3.1 vector CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H yields a score of 7.5. The High Attack Complexity (AC:H) materially constrains exploitability: the attacker must first obtain a valid SAML response, which requires operating within the SSO authentication flow or intercepting a legitimate assertion. The Low Privileges requirement (PR:L) further restricts exploitation to actors who already hold some form of valid access. Despite these constraints, the impact triad of C:H/I:H/A:H reflects worst-case impersonation of a highly privileged Artifactory user - potentially an admin - which could expose all artifacts, pipeline secrets, and access controls. No EPSS score was supplied, making probabilistic exploitation forecasting impossible. There is no CISA KEV listing and no confirmed public exploit, which lowers urgency compared to the raw CVSS score. The 'JWT Attack' tag implies this may be a known attack class (e.g., SAML assertion manipulation to forge JWTs), which increases the likelihood that skilled threat actors familiar with SAML attacks could reproduce exploitation. Risk is real but not immediate for organizations with network-segmented Artifactory deployments; organizations exposing Artifactory's SAML SSO endpoint to the internet or to broad internal networks face elevated exposure. |
| Exploit ScenarioDerived | An attacker with a valid low-privileged Artifactory account participates in a SAML authentication flow and intercepts or retains their own issued SAML assertion. Using an XML Signature Wrapping technique or similar manipulation, the attacker modifies the assertion's NameID to reference a target user (such as an Artifactory admin) while preserving the valid cryptographic signature on an unrelated element. Artifactory's deficient signature verification accepts the assertion, issues a JWT token for the impersonated user, and grants the attacker full privileges of that account. No publicly available proof-of-concept code has been identified to confirm this specific exploitation path. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 12, 2026
SAML response impersonation in JFrog Artifactory (all tracked versions per CPE) permits an attacker who possesses a valid SAML response to assume the identity of another user under specific conditions. Rooted in CWE-347 (Improper Verification of Cryptographic Signature), the flaw indicates Artifactory fails to adequately validate SAML assertion signatures or cryptographic bindings - a class of weakness commonly exploited via XML Signature Wrapping (XSW) or assertion replay attacks. The 'JWT Attack' tag suggests Artifactory may internally convert SAML assertions to JWT tokens, and the signature verification gap may exist at that translation layer. No public exploit code and no CISA KEV listing have been identified at time of analysis.
RemediationAI
Consult the JFrog security advisory at https://docs.jfrog.com/releases/docs/jfrog-security-advisories and the Artifactory self-managed release notes at https://docs.jfrog.com/releases/docs/artifactory-self-managed-releases for the specific patched version. No exact fix version is confirmed in the available intelligence data, so an upstream-released patched version cannot be cited independently. As an immediate compensating control, organizations should audit and restrict which SAML identity providers are trusted in the Artifactory SAML SSO configuration, enforce short SAML assertion validity windows (reducing the replay window), and enable assertion audience restriction checks if configurable. If Artifactory's SAML endpoint is exposed beyond the minimum required network perimeter, restrict access via firewall rules or reverse proxy allowlists. Note that disabling SAML SSO entirely eliminates this attack surface but may disrupt federated authentication workflows for all SSO users.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
SAML (Security Assertion Markup Language) is an XML-based federated identity protocol used for Single Sign-On (SSO). CWE-347 - Improper Verification of Cryptographic Signature - means the application either skips, weakens, or improperly validates the XML digital signature on a SAML assertion before trusting its identity claims. In practice, this enables attacks such as XML Signature Wrapping (XSW), where a valid signature is retained but the signed element is moved and a malicious payload is substituted, or assertion replay, where a legitimately issued assertion is reused out of context. The 'JWT Attack' tag in the intelligence record is notable: JFrog Artifactory issues JWT access tokens after SAML authentication, and if the SAML-to-JWT conversion step does not re-validate the assertion signature, a manipulated assertion may produce a JWT impersonating a different user. The affected product is confirmed via CPE cpe:2.3:a:jfrog:artifactory:*:*:*:*:*:*:*:*, covering the Artifactory self-managed artifact repository platform - a central component in enterprise DevOps pipelines that controls access to build artifacts, container images, and binary packages.
Know when Jwt Attack gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
AV:N for web-based SAML endpoint; AC:H for the prerequisite of obtaining a valid SAML assertion; PR:L since the attacker must hold some authenticated IdP identity; full C/I/A impact from arbitrary user impersonation.
Primary rating from Vendor (JFROG).
CVSS VectorVendor: JFROG
Lifecycle Timeline
2DescriptionCVE.org
A user with access to a valid SAML response may impersonate another user under specific conditions.
Executive ViewAI
JFrog Artifactory contains a high-severity flaw in SAML assertion signature validation that allows attackers to impersonate other users. No public exploit has been identified at time of analysis, but the vulnerability directly undermines identity and access controls in centralized artifact repositories that serve as critical infrastructure for software supply chains. Organizations using SAML authentication face immediate risk of unauthorized access, artifact tampering, and potential compromise across all dependent applications.
No vendor-released patch identified at time of analysis. Implement interim mitigations: restrict SAML response sources at network and application layers, add cryptographic re-validation of JWT tokens at assertion consumption boundaries, enforce multi-factor authentication for administrative operations, enable comprehensive audit logging of all authentication transitions and sensitive artifact access, and consider temporary migration to certificate-based authentication for critical repositories pending vendor guidance.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Jwt Attack
View allWhy is Microsoft republishing a CVE from 2013? We are republishing CVE-2013-3900 in the Security Update Guide to update
Authentication bypass in SimpleHelp 5.5.15 and prior (plus 6.0 pre-release builds) allows remote unauthenticated attacke
Authentication bypass in WSO2 API Manager and related components (Universal Gateway, Traffic Manager, API Control Plane,
Authentication bypass in Fortinet FortiOS, FortiProxy, and FortiSwitchManager allows unauthenticated remote attackers to
ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Rated critical severity (CVS
Security feature bypass in Microsoft .NET (shipped via Visual Studio 2022 17.12/17.14 and Visual Studio 2026 18.7) lets
ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Rated critical severity (CVS
The package jsrsasign before 10.5.25 are vulnerable to Improper Verification of Cryptographic Signature when JWS or JWT
Authentication and authorization bypass in fast-jwt 6.2.0 through 6.2.4 (npm, NearForm) lets a remote, unauthenticated a
A library injection vulnerability exists in Microsoft Teams (work or school) 24046.2813.2770.1094 for macOS. Rated criti
A library injection vulnerability exists in the WebView.app helper app of Microsoft Teams (work or school) 24046.2813.27
A library injection vulnerability exists in the com.microsoft.teams2.modulehost.app helper app of Microsoft Teams (work
EUVD-2026-57253
GHSA-c4qm-8pgx-8w9v
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB