CVE-2025-27403: Github.com/ratify project/ratify Ratify Azure Authentication Providers Can Vulnerability

Q: What is CVE-2025-27403?

CVE-2025-27403 is a security vulnerability in Github.com/ratify project/ratify involving Ratify Azure authentication providers can leak authentication tokens to non-Azure container registries under CWE-287: Improper Authentication.

Q: Which Github.com/ratify project/ratify versions are affected?

Affected versions include releases prior to 1.2.3, 1.3.2 across affected packages: github.com/ratify-project/ratify, github.com/deislabs/ratify.

Q: What version fixes CVE-2025-27403?

Upgrading to 1.2.3, 1.3.2 (or the latest patched release for your respective branch) resolves the vulnerability.

Q: Is github.com/ratify-project/ratify affected?

Yes, github.com/ratify-project/ratify is affected in releases prior to 1.2.3, 1.3.2. Upgrade your dependency to 1.2.3, 1.3.2 or later.

Q: Is github.com/deislabs/ratify affected?

Yes, github.com/deislabs/ratify is affected in releases prior to 1.2.3. Upgrade your dependency to 1.2.3 or later.

Q: What CWE is associated with CVE-2025-27403?

CVE-2025-27403 is classified under CWE-287: Improper Authentication (When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.).

Q: How can I check Go dependencies for CVE-2025-27403?

Run the dependency tree command: 'inspect dependencies for github.com/ratify-project/ratify'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.

HIGH

Advisory Identifier: GHSA-44f7-5fj5-h4px

CWE-287 CWE-497

Published 2025-03-11

Advisory Summary

CVE-2025-27403 is a HIGH ratify azure authentication providers can vulnerability (CWE-287: Improper Authentication) affecting Github.com/ratify project/ratify libraries in the Go ecosystem. The issue involves ratify azure authentication providers can leak authentication tokens to non-azure container registries. Remediation is available by upgrading affected packages to version 1.2.3, 1.3.2.

CVE-2025-27403 at a Glance

CVE Identifier CVE-2025-27403

GHSA Identifier GHSA-44f7-5fj5-h4px

Severity HIGH

CVSS v3.1 Base Score N/A

CWE Classification CWE-287: Improper Authentication

Affected Product Github.com/ratify project/ratify

Package Ecosystem Go

Published Date 2025-03-11

Last Updated 2025-03-14

How to Fix CVE-2025-27403

To remediate this vulnerability, upgrade all affected Github.com/ratify project/ratify dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/ratify-project/ratify fixed: 1.2.3

Upgrade github.com/ratify-project/ratify to 1.2.3

github.com/ratify-project/ratify fixed: 1.3.2

Upgrade github.com/ratify-project/ratify to 1.3.2

github.com/deislabs/ratify fixed: 1.2.3

Upgrade github.com/deislabs/ratify to 1.2.3

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/ratify-project/ratify

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-27403, inspect your project dependencies for Github.com/ratify project/ratify:

inspect dependencies for github.com/ratify-project/ratify

Analyze the terminal output to locate any version of Github.com/ratify project/ratify in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.2.3), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-287: Improper Authentication, where when an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. In Github.com/ratify project/ratify, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact 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. 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. ### Patches 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. ### Credits The `ratify` project would like to thank Shiwei Zhang (@shizhMSFT) and Binbin Li (@binbin-li) for responsibly disclosing the issue and thank Binbin Li (@binbin-li) and Akash Singhal (@akashsinghal) for actively mitigating the issue.

CVE-2025-27403 Affected Github.com/ratify project/ratify Versions

3 component(s)

Fixed Versions:

1.2.31.3.2

Product / Package	Ecosystem	Affected Versions	Fixed Version
github.com/ratify-project/ratify golang/github.com/ratify-project/ratify	Go	< 1.2.3	1.2.3
github.com/ratify-project/ratify golang/github.com/ratify-project/ratify	Go	≥ 1.3.0 < 1.3.2	1.3.2
github.com/deislabs/ratify golang/github.com/deislabs/ratify	Go	< 1.2.3	1.2.3

References

GitHub Advisory / Wiki ADVISORY

https://github.com/ratify-project/ratify/security/advisories/GHSA-44f7-5fj5-h4px

NVD — CVE-2025-27403 NVD

https://nvd.nist.gov/vuln/detail/CVE-2025-27403

Security Fix Commit FIX COMMIT

https://github.com/ratify-project/ratify/commit/0ec0c08490e3d672ae64b1a220c90d5484f1c93f

Security Fix Commit FIX COMMIT

https://github.com/ratify-project/ratify/commit/84c7c48fa76bb9a1c9583635d1e90bc25b1a546c

Github.com/ratify project/ratify Source Repository REPOSITORY

https://github.com/ratify-project/ratify

pkg.go.dev/vuln/go-2025-3511 WEB

https://pkg.go.dev/vuln/GO-2025-3511

Frequently Asked Questions

What is CVE-2025-27403?

CVE-2025-27403 is a security vulnerability in Github.com/ratify project/ratify involving Ratify Azure authentication providers can leak authentication tokens to non-Azure container registries under CWE-287: Improper Authentication.

Which Github.com/ratify project/ratify versions are affected?

Affected versions include releases prior to 1.2.3, 1.3.2 across affected packages: github.com/ratify-project/ratify, github.com/deislabs/ratify.

What version fixes CVE-2025-27403?

Upgrading to 1.2.3, 1.3.2 (or the latest patched release for your respective branch) resolves the vulnerability.

Is github.com/ratify-project/ratify affected?

Yes, github.com/ratify-project/ratify is affected in releases prior to 1.2.3, 1.3.2. Upgrade your dependency to 1.2.3, 1.3.2 or later.

Is github.com/deislabs/ratify affected?

Yes, github.com/deislabs/ratify is affected in releases prior to 1.2.3. Upgrade your dependency to 1.2.3 or later.

What CWE is associated with CVE-2025-27403?

CVE-2025-27403 is classified under CWE-287: Improper Authentication (When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.).

How can I check Go dependencies for CVE-2025-27403?

Run the dependency tree command: 'inspect dependencies for github.com/ratify-project/ratify'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.

Machine-readable OSV JSON OSV v1.5 Schema

Normalized schema output

View Raw JSON

{
  "schema_version" : "1.4.0",
  "id" : "GHSA-44f7-5fj5-h4px",
  "modified" : "2025-03-14T20:00:47Z",
  "published" : "2025-03-11T15:27:16Z",
  "aliases" : [ "CVE-2025-27403" ],
  "summary" : "Ratify Azure authentication providers can leak authentication tokens to non-Azure container registries",
  "details" : "### Impact\n\nIn 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.\nBoth 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.\n\n### Patches\n\nThe 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.\n\n### Credits\n\nThe `ratify` project would like to thank Shiwei Zhang (@shizhMSFT) and Binbin Li (@binbin-li) for responsibly disclosing the issue and thank Binbin Li (@binbin-li) and Akash Singhal (@akashsinghal) for actively mitigating the issue.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:H/SA:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/ratify-project/ratify"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.2.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/ratify-project/ratify"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.3.0"
      }, {
        "fixed" : "1.3.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/deislabs/ratify"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.2.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/ratify-project/ratify/security/advisories/GHSA-44f7-5fj5-h4px"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-27403"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/ratify-project/ratify/commit/0ec0c08490e3d672ae64b1a220c90d5484f1c93f"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/ratify-project/ratify/commit/84c7c48fa76bb9a1c9583635d1e90bc25b1a546c"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/ratify-project/ratify"
  }, {
    "type" : "WEB",
    "url" : "https://pkg.go.dev/vuln/GO-2025-3511"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-287", "CWE-497" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-03-11T15:27:16Z",
    "nvd_published_at" : "2025-03-11T15:15:45Z"
  }
}

CVSS V4

N/A HIGH

Attack Vector N/A

Attack Complexity N/A

Privileges Required N/A

User Interaction N/A

Scope N/A

Confidentiality N/A

Integrity N/A

Availability N/A

Vector String

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:H/SA:L

Advisory Metadata

Source ID: GHSA-44f7-5fj5-h4px
Schema Version: 1.4.0
Published: 2025-03-11 15:27
Last Modified: 2025-03-14 20:00
Database Record File: advisories/github-reviewed/2025/03/GHSA-44f7-5fj5-h4px/GHSA-44f7-5fj5-h4px.json