CVE-2026-42151

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.

What this means for your business

It affects Prometheus. It matters if your company, or a supplier that handles your data, runs it.
An attacker can use it remotely, over a network, without a login, and without anyone at your company clicking anything.
FIRST's prediction model gives it a 0.4% chance of attack attempts being seen in the next 30 days, ranking above 28% of all known flaws.

What to do

1Check whether your company or your suppliers run Prometheus, and which version. The affected versions are listed further down this page.
2If you do, apply the vendor's fix. A patch or vendor advisory has been published.

Not sure if your company is exposed?

Fastnexa’s certified penetration testers can check whether attackers could use this flaw, or others like it, against your websites, apps and network. The full test is free for our first 10 founding clients until 31 December 2026.

Check if you’re exposed Book a call

Scoring

CVSS: 7.5 (v3.1)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Weakness: CWE-200
Assigned by: security-advisories@github.com

Dates

Published: 2026-05-04
Last modified: 2026-09-10
Sources: NVD

Affected products

Prometheus Prometheus2.48.0 - 3.5.3, 3.6.0 - 3.11.3

As listed in the NVD configuration data. Not a statement about your estate.