Homepage

Information Exposure Affecting loki-fips-3.5-promtail package, versions *

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.01% (2nd 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 Learn

Learn about Information Exposure vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-MINIMOSLATEST-LOKIFIPS35PROMTAIL-16439769
  • published7 May 2026
  • disclosed4 May 2026
Report a new vulnerability Found a mistake?

Introduced: 4 May 2026

NewCVE-2026-42151  (opens in a new tab)
CWE-200  (opens in a new tab)
CWE-312  (opens in a new tab)

How to fix?

There is no fixed version for Minimos:latest loki-fips-3.5-promtail.

NVD Description

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

Prometheus is an open-source monitoring system and time series database. Prior to versions 3.5.3 and 3.11.3, the client_secret field in the Azure AD remote write OAuth configuration (storage/remote/azuread) was typed as string instead of Secret. Prometheus redacts fields of type Secret when serving the configuration via the /-/config HTTP API endpoint. Because the field was a plain string, the Azure OAuth client secret was exposed in plaintext to any user or process with access to that endpoint. This issue has been patched in versions 3.5.3 and 3.11.3.