7.2

CVE-2025-27403: Ratify Azure authentication providers can leak authentication tokens to non-Azure container registries

Deferred
AliasesGHSA-44f7-5fj5-h4pxGO-2025-3511
Published 11-03-2025Last modified 11-03-2025

Vulnerability summary

CVE-2025-27403 is a high (CVSS 7.2) Improper Authentication vulnerability in ratify-project ratify. EPSS estimates a 0.48% chance of exploitation in the next 30 days, higher than 40.5% of scored vulnerabilities.

Overall risk
29/100
0100
Medium · default modelHow is this calculated?
CVSS score
7.2/10
010
High · v4.0 (CVE.org)
EPSS score
0.48%
0%100%
Low · +0.01 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 1 · Related 1
OPENSUSE-SU-2025:14893-1

Timeline

  1. 11-03-2025
    PublishedVulnerability first disclosed.
  2. 11-03-2025
    Last modifiedVulnerability information updated.

Description

Ratify is a verification engine as a binary executable and on Kubernetes which enables verification of artifact security metadata and admits for deployment only those that comply with policies the user creates. In a Kubernetes environment, Ratify can be configured to authenticate to a private Azure Container Registry (ACR). The Azure workload identity and Azure managed identity authentication providers are configured in this setup. Users that configure a private ACR to be used with the Azure authentication providers may be impacted by a vulnerability that exists in versions prior to 1.2.3 and 1.3.2. Both Azure authentication providers attempt to exchange an Entra ID (EID) token for an ACR refresh token. However, Ratify’s Azure authentication providers did not verify that the target registry is an ACR. This could have led to the EID token being presented to a non-ACR registry during token exchange. EID tokens with ACR access can potentially be extracted and abused if a user workload contains an image reference to a malicious registry. As of versions 1.2.3 and 1.3.2, the Azure workload identity and Azure managed identity authentication providers are updated to add new validation prior to EID token exchange. Validation relies upon registry domain validation against a pre-configured list of well-known ACR endpoints. EID token exchange will be executed only if at least one of the configured well-known domain suffixes (wildcard support included) matches the registry domain of the image reference.

CVSS metrics

3 scores · 3 sources · 1 version

EPSS trend

Probability

0.48%

Chance of exploitation in the next 30 days

Percentile

41%

Versus all other CVEs

30-day change

Increase +0.01 pp

From 0.47% on 22-09-2026

22-09-202622-10-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Github.com/deislabs1 product
  • ratify< 1.2.3
Github.com/ratify-project1 product
  • ratify< 1.2.3 | ≥ 1.3.0, < 1.3.2
Ratify-project1 product
  • ratify< 1.2.3 | ≥ 1.3.0, < 1.3.2

3 vendors · 3 products

References

6 links