Prometheus OAuth Client Secret Exposure via /-/config (pre 3.5.3/3.11.3)
CVE-2026-42151 Published on May 4, 2026

Prometheus Azure AD remote write OAuth client secret exposed via config API
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.

NVD

Vulnerability Analysis

CVE-2026-42151 can be exploited with network access, and does not require authorization privileges or user interaction. This vulnerability is considered to have a low attack complexity. The potential impact of an exploit of this vulnerability is considered to have a high impact on confidentiality, with no impact on integrity and availability.

Attack Vector:
NETWORK
Attack Complexity:
LOW
Privileges Required:
NONE
User Interaction:
NONE
Scope:
UNCHANGED
Confidentiality Impact:
HIGH
Integrity Impact:
NONE
Availability Impact:
NONE

Weakness Types

What is an Information Disclosure Vulnerability?

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

CVE-2026-42151 has been classified to as an Information Disclosure vulnerability or weakness.

Cleartext Storage of Sensitive Information

The application stores sensitive information in cleartext within a resource that might be accessible to another control sphere. Because the information is stored in cleartext, attackers could potentially read it. Even if the information is encoded in a way that is not human-readable, certain techniques could determine which encoding is being used, then decode the information.

Unprotected Storage of Credentials

Storing a password in plaintext may result in a system compromise. Password management issues occur when a password is stored in plaintext in an application's properties or configuration file. Storing a plaintext password in a configuration file allows anyone who can read the file access to the password-protected resource.


Products Associated with CVE-2026-42151

You can be notified by email with stack.watch whenever vulnerabilities like CVE-2026-42151 are published in these products:

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Affected Versions

prometheus: Red Hat RHEM 1.0 for RHEL 9: Red Hat Enterprise Linux AppStream (v. 10): Red Hat Enterprise Linux AppStream (v. 9): Red Hat Edge Manager 1.0: Red Hat Hardened Images: Red Hat Trusted Artifact Signer 1.4: Custom Metric Autoscaler operator for Red Hat Openshift: Red Hat File Integrity Operator: Logging Subsystem for Red Hat OpenShift: Red Hat Network Observability Operator: Red Hat OpenShift Lightspeed: Red Hat Advanced Cluster Management for Kubernetes 2: Red Hat Ceph Storage 5: Red Hat Ceph Storage 6: Red Hat Ceph Storage 7: Red Hat Ceph Storage 8: Red Hat Ceph Storage 9: Red Hat Edge Manager 1: Red Hat Enterprise Linux 10: Red Hat Enterprise Linux 7: Red Hat Enterprise Linux 8: Red Hat Enterprise Linux 9: Red Hat OpenShift AI (RHOAI): Red Hat OpenShift Container Platform 4: Red Hat OpenShift distributed tracing 3: Red Hat OpenShift GitOps: Red Hat OpenStack Platform 18.0: Red Hat Quay 3: Red Hat Multicluster Global Hub: Red Hat OpenShift Service Mesh 2: Red Hat OpenShift Service Mesh 3:

Exploit Probability

EPSS
0.25%
Percentile
15.95%

EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.