Information Exposure Affecting argo-rollouts-fips package, versions <1.9.1-r1


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.19% (9th 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-ARGOROLLOUTSFIPS-19926287
  • published19 Sept 2026
  • disclosed16 Sept 2026

Introduced: 16 Sep 2026

NewCVE-2026-81870  (opens in a new tab)
CWE-200  (opens in a new tab)
CWE-532  (opens in a new tab)

How to fix?

Upgrade Minimos:latest argo-rollouts-fips to version 1.9.1-r1 or higher.

NVD Description

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

OpenTelemetry-Go is the Go implementation of OpenTelemetry. From version 1.5.0 to 1.44.0, sdk/trace.NewTracerProvider emits a TracerProvider created internal Info-level diagnostic event whose MarshalLog implementations recursively include span processor, exporter, and client configuration. Applications that call otel.SetLogger to enable OpenTelemetry internal Info logging can therefore record OTLP gRPC and HTTP collector endpoints, the OTLP HTTP Insecure flag, and complete Zipkin collector URLs. A person or system with access to those logs can learn internal collector topology and can recover credentials or tokens embedded in Zipkin URL user information or query strings. The default OpenTelemetry logger does not emit the event, and this path does not log OTLP authentication headers, TLS key material, or span payloads. This issue is fixed in version 1.45.0.