Server-Side Request Forgery (SSRF) Affecting argocd-fips-3.2-compat package, versions <3.2.12-r4


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.38% (32nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-ARGOCDFIPS32COMPAT-19924656
  • published19 Sept 2026
  • disclosed16 Sept 2026

Introduced: 16 Sep 2026

NewCVE-2026-85732  (opens in a new tab)
CWE-918  (opens in a new tab)

How to fix?

Upgrade Minimos:latest argocd-fips-3.2-compat to version 3.2.12-r4 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream argocd-fips-3.2-compat package and not the argocd-fips-3.2-compat package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

oras-go is a Go library for managing OCI artifacts. Prior to 2.6.2, the parseLink function in registry/remote/utils.go accepts an absolute URL from a registry-controlled Link response header without validating its scheme, host, or port. Tags, Referrers, and Repositories pagination operations then issue a GET request to the attacker-selected URL from the victim's network, allowing blind server-side request forgery against internal services. The response body is not returned to the attacker, but timing and error differences can reveal service reachability, and credentials may be attached when the credential store has an entry for the target host. Exploitation requires a victim to perform a pagination-based listing operation against a malicious registry. The maintainer identifies this report as a duplicate of GHSA-3hr5-mjrr-hfjh and states that remediation is consolidated in that earlier advisory. The consolidated issue is fixed in version 2.6.2.