Prometheus up to 3.15.1 Remote Write azuread.go information disclosure

Summaryinfo

A vulnerability was found in Prometheus up to 3.15.1. It has been classified as problematic. This affects an unknown part of the file storage/remote/azuread/azuread.go of the component Remote Write. The manipulation leads to information disclosure. This vulnerability is referenced as CVE-2026-119566. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in Prometheus up to 3.15.1 and classified as problematic. This issue affects an unknown code block of the file storage/remote/azuread/azuread.go of the component Remote Write. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:

Prometheus through 3.15.1 contains a credential leak vulnerability that allows attackers to capture Azure AD or Google IAM bearer tokens by redirecting remote_write requests to another host. Attackers controlling the remote-write endpoint or a redirecting server can return a 3xx to their host and replay the token, for example to write metrics to the victim's backend.

It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-119566 since 10/30/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/30/2026). The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• Prometheus

Version

• 3.15.0
• 3.15.1

Website

• Product: https://github.com/prometheus/prometheus/

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion