EUVD-2026-27089
GHSA-wg65-39gg-5wfj
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDiscover exposed Prometheus instance
-
DeliveryAccess /-/config endpoint unauthenticated
-
ExploitExtract Azure client_secret from JSON response
-
ExecutionAuthenticate to Azure AD with stolen credentials
-
PersistAccess Azure resources as service principal
-
ImpactExfiltrate data or poison metrics
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the Prometheus instance to be configured with Azure AD OAuth remote write (azuread authentication method in remote_write configuration block), which is not enabled by default. The /-/config HTTP API endpoint must be network-accessible to the attacker, meaning either the Prometheus server is directly exposed to the internet, or the attacker has gained internal network access. Exploitation is unauthenticated (CVSS PR:N), so no credentials are required to access the configuration endpoint if reachable. Limiting factors include: many production deployments place Prometheus behind VPNs, internal networks, or reverse proxies with authentication; the vulnerability only leaks credentials if Azure AD remote write is explicitly configured (specific feature required); organizations using Azure Managed Identity authentication instead of client secrets are not affected. Default Prometheus installations without Azure integration have zero risk from this vulnerability. |
| Impact | Real-world risk is HIGH for organizations using Prometheus with Azure AD remote write configurations. The CVSS 7.5 severity with vector AV:N/AC:L/PR:N/UI:N indicates remote unauthenticated exploitation with low complexity, representing a true critical exposure. However, actual risk depends heavily on deployment context: exploitation requires (1) the /-/config endpoint to be network-accessible, and (2) Azure AD OAuth remote write to be configured (not default). Many production deployments restrict Prometheus API access to internal networks or authenticated users via reverse proxies, significantly reducing exposure surface. The CVSS score reflects worst-case public exposure. Without EPSS data, we cannot quantify exploitation probability, but the absence of CISA KEV listing suggests no widespread exploitation campaigns detected as of vendor disclosure. The high confidentiality impact (C:H) is accurate - stolen Azure OAuth client secrets grant attackers the full permissions of the configured service principal, potentially including write access to Azure Monitor, Log Analytics, or custom remote write endpoints. This could enable data exfiltration, metric poisoning, or lateral movement into Azure environments. The GitHub advisory and merged PRs confirm both the vulnerability details and fix implementation. Priority should be IMMEDIATE for internet-exposed Prometheus instances with Azure remote write, MEDIUM for internal deployments with defense-in-depth controls. |
| Exploit ScenarioDerived | An attacker scans for internet-exposed Prometheus instances on common ports (9090/tcp) using automated tools like Shodan or Censys. Upon discovering a target, the attacker requests the publicly accessible /-/config endpoint without authentication (CVSS PR:N). The returned JSON configuration reveals the Azure AD client_secret in plaintext within the azuread remote_write block. Using the stolen client_id, client_secret, and tenant_id triple, the attacker authenticates to Azure AD as the Prometheus service principal, obtaining OAuth tokens with whatever permissions were granted to that identity. This could enable writing malicious metrics to Azure Monitor to trigger false alerts, exfiltrating existing monitoring data, or using the identity as a pivot point for further Azure resource compromise depending on the service principal's role assignments. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 04, 2026
Prometheus monitoring system exposes Azure AD OAuth client secrets in plaintext via its /-/config HTTP API endpoint. Versions prior to 3.5.3 and 3.11.3 incorrectly type the client_secret field as a plain string instead of Prometheus's redacted Secret type, allowing remote unauthenticated attackers to retrieve sensitive Azure credentials from any exposed Prometheus instance configured for Azure AD remote write. The vulnerability has low exploitation complexity (CVSS AV:N/AC:L/PR:N) with 7.5 severity. Vendor-confirmed patches available in versions 3.5.3 and 3.11.3 (GitHub releases confirmed). EPSS data not provided; no CISA KEV listing indicating targeted exploitation campaigns at time of analysis.
RemediationAI
Upgrade immediately to Prometheus version 3.5.3 (for 3.5.x users) or 3.11.3 (for 3.11.x users) as documented in vendor releases at https://github.com/prometheus/prometheus/releases. The patches implement type change from string to config_util.Secret for client_secret fields per PR #18587 and #18590. After patching, rotate all Azure AD OAuth client secrets exposed via the /-/config endpoint, as credentials should be considered compromised if the endpoint was accessible during the vulnerable period. Rotation procedure: (1) create new client secret in Azure AD app registration, (2) update Prometheus configuration with new secret, (3) restart Prometheus, (4) delete old secret in Azure portal. If immediate patching is not feasible, implement compensating controls: restrict network access to Prometheus /-/config endpoint via firewall rules or reverse proxy authentication (note: this adds operational complexity for legitimate debugging workflows), or disable Azure AD remote write temporarily and use alternative authentication methods like managed identities where supported (requires infrastructure changes). Monitor Azure AD sign-in logs for suspicious OAuth token requests using the exposed client ID during the exposure window. No workaround provides complete protection; patching is the only full remediation.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in go, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Prometheus is a widely-deployed open-source monitoring system with time series database capabilities, commonly used for Kubernetes and cloud infrastructure observability. The vulnerability lies in the storage/remote/azuread module responsible for Azure AD OAuth authentication in remote write configurations. The root cause (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) stems from using Go's native string type instead of Prometheus's config_util.Secret type from the prometheus/common/config library. The Secret type implements redaction mechanisms that automatically mask sensitive values when configuration is serialized and served via HTTP endpoints. The /-/config endpoint is a standard Prometheus API path that serves the running configuration, intended for debugging and operational visibility. Without proper Secret typing, the Azure OAuth client_secret field was serialized as plaintext JSON, exposing credentials with the same privileges as the Prometheus service's remote write identity. The affected CPE cpe:2.3:a:prometheus:prometheus indicates impact to the core Prometheus server component across vulnerable version ranges.
Know when Prometheus gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
1DescriptionCVE.org
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.
Executive ViewAI
Prometheus versions prior to 3.5.3 and 3.11.3 expose Azure AD OAuth client secrets in plaintext through an unauthenticated API endpoint, allowing attackers to extract cloud identity credentials from any internet-accessible monitoring instance. Organizations using Prometheus with Azure AD remote write are at immediate risk of credential compromise, which could enable unauthorized access to Azure resources and downstream systems.
Vendor-released patch: versions 3.5.3 and 3.11.3. If immediate patching is not feasible, restrict network access to the /-/config endpoint using firewall rules or reverse proxy authentication, rotate Azure AD client secrets immediately, and monitor Azure AD audit logs for anomalous credential usage. Disable remote write functionality temporarily if Azure AD integration is not critical.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Prometheus
View allPrometheus Exporter Toolkit is a utility package to build exporters. Rated high severity (CVSS 8.8), this vulnerability
Unsafe PHP deserialization in openITCOCKPIT Community Edition 5.3.1 and earlier allows authenticated attackers to inject
Remote code execution in openITCOCKPIT 5.3.1 and earlier via unsafe deserialization in the Gearman worker component, whi
Memory exhaustion in Prometheus remote read endpoint allows unauthenticated attackers to crash the monitoring server via
Prometheus is an open-source monitoring system and time series database. Rated medium severity (CVSS 6.1), this vulnerab
Prometheus Blackbox Exporter through 0.17.0 allows /probe?target= SSRF. Rated medium severity (CVSS 5.8), this vulnerabi
blackbox_exporter v0.23.0 was discovered to contain an access control issue in its probe interface. Rated high severity
Scraparr versions 3.0.0-beta through 3.0.1 expose Readarr API keys in plaintext through the /metrics endpoint when the R
Denial of Service in Prometheus and Kibana metricsets can be triggered by sending specially crafted malformed payloads t
Prometheus through 3.15.1 can expose Azure AD or Google IAM bearer tokens when remote_write follows an HTTP 3xx redirect
A stored, DOM based, cross-site scripting (XSS) flaw was found in Prometheus before version 2.7.1. Rated medium severity
Alertmanager handles alerts sent by client applications such as the Prometheus server. Rated medium severity (CVSS 5.4),
Same weakness CWE-200 – Information Exposure
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: High| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
| SUSE Linux Enterprise Module for Package Hub 15 SP7 | Fixed |
| SUSE Linux Enterprise Server 16.0 | Fixed |
| SUSE Linux Enterprise Server for SAP applications 16.0 | Fixed |
| SUSE Manager Client Tools 15 | Fixed |
| SUSE Manager Client Tools for SLE 15 | Fixed |
| SUSE Multi-Linux Manager Client Tools for SLE 15 | Fixed |
| SUSE Manager Proxy LTS 4.3 | Fixed |
| SUSE Manager Proxy Module 4.3 | Fixed |
| SUSE Enterprise Storage 6 | Fixed |
| SUSE Linux Enterprise Module for Package Hub 15 SP5 | Fixed |
| SUSE Linux Enterprise Module for Package Hub 15 SP6 | Fixed |
| SUSE Manager Proxy Module 4.1 | Fixed |
| SUSE Manager Proxy Module 4.2 | Fixed |
| openSUSE Leap 15.3 | Fixed |
| openSUSE Leap 15.4 | Fixed |
| openSUSE Leap 15.5 | Fixed |
| openSUSE Leap 15.6 | Fixed |
| SUSE Multi Linux Manager Tools SLE-15 | Fixed |
Exploit-DB