How severe is GHSA-44f7-5fj5-h4px?

No CVSS score has been assigned to GHSA-44f7-5fj5-h4px yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-44f7-5fj5-h4px?

GHSA-44f7-5fj5-h4px affects the following packages: github.com/ratify-project/ratify (Go), github.com/ratify-project/ratify (Go), github.com/deislabs/ratify (Go). Ecosystems affected: Go.

How do I fix GHSA-44f7-5fj5-h4px?

Update github.com/ratify-project/ratify to 1.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-44f7-5fj5-h4px is resolved across your whole dependency graph.

How do I detect GHSA-44f7-5fj5-h4px in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/ratify-project/ratify, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-44f7-5fj5-h4px if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-44f7-5fj5-h4px actively exploited in the wild?

No public exploit code has been indexed for GHSA-44f7-5fj5-h4px yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-44f7-5fj5-h4px?

GHSA-44f7-5fj5-h4px has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 38th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-44f7-5fj5-h4px?

GHSA-44f7-5fj5-h4px is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-44f7-5fj5-h4px published, and has it been updated?

GHSA-44f7-5fj5-h4px was published on March 11, 2025 and was last updated on March 14, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-44f7-5fj5-h4px — ratify

Fix: ratify-project/ratify@0ec0c08

GHSA-44f7-5fj5-h4px is a Improper Authentication vulnerability in github.com/ratify-project/ratify. A fix is available for github.com/ratify-project/ratify — see the affected versions and patch details below.

Ratify Azure authentication providers can leak authentication tokens to non-Azure container registries

Also known asCVE-2025-27403GO-2025-3511

Published

Mar 11, 2025

Updated

Mar 14, 2025

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Sep 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-44f7-5fj5-h4px.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

🐹github.com/ratify-project/ratify🐹github.com/ratify-project/ratify🐹github.com/deislabs/ratify

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/ratify-project/ratify`	all versions	1.2.3`go get github.com/ratify-project/ratify@v1.2.3`
🐹Go	`github.com/ratify-project/ratify`	≥ 1.3.0&&< 1.3.2	1.3.2`go get github.com/ratify-project/ratify@v1.3.2`
🐹Go	`github.com/deislabs/ratify`	all versions	1.2.3`go get github.com/deislabs/ratify@v1.2.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/ratify-project/ratify, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/ratify-project/ratify to 1.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-44f7-5fj5-h4px is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### 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 t

O3 Security · Impact-Aware SCA

Is GHSA-44f7-5fj5-h4px in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works