Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2026-42151: Prometheus Azure AD remote write OAuth client secret exposed via config API

Noroxi assessment

Priority: Monitor (action score 30/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.35% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: azl3 telegraf 1.31.0-22 on Azure Linux 3.0 1.31.0-22.

Low priority for now. Upgrade to azl3 telegraf 1.31.0-22 on Azure Linux 3.0 1.31.0-22 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
May 4, 2026
Updated
Sep 10, 2026
EPSS
0.3% · 28th percentile

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
7.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-42151

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
prometheusprometheus

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • prometheus prometheus2.48.0 and later · before 3.5.3
  • prometheus prometheus3.6.0 and later · before 3.11.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • prometheus prometheus

    • < 3.5.3, >= 3.6.0, < 3.11.3affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10opentelemetry-collectorbefore 0.152.1-1.el10_20.152.1-1.el10_2
AlmaLinux:9opentelemetry-collectorbefore 0.152.1-1.el9_80.152.1-1.el9_8
Debian:13prometheusfrom 0—
Debian:14prometheusbefore 3.5.3+ds1-13.5.3+ds1-1
Gogithub.com/prometheus/prometheusfrom 0.45.2 · before 0.311.30.311.3
openSUSE:Tumbleweedgolang-github-prometheus-prometheusbefore 3.11.3-1.13.11.3-1.1
Red Hat:edge_manager:1.0::el9flightctlbefore 0:1.0.3-1.el9em0:1.0.3-1.el9em
Red Hat:edge_manager:1.0::el9flightctl-agentbefore 0:1.0.3-1.el9em0:1.0.3-1.el9em
Red Hat:edge_manager:1.0::el9flightctl-clibefore 0:1.0.3-1.el9em0:1.0.3-1.el9em
Red Hat:edge_manager:1.0::el9flightctl-selinuxbefore 0:1.0.3-1.el9em0:1.0.3-1.el9em
Red Hat:edge_manager:1.1::el10flightctlbefore 0:1.1.3-1.el10em0:1.1.3-1.el10em
Red Hat:edge_manager:1.1::el10flightctl-agentbefore 0:1.1.3-1.el10em0:1.1.3-1.el10em
Red Hat:edge_manager:1.1::el10flightctl-clibefore 0:1.1.3-1.el10em0:1.1.3-1.el10em
Red Hat:edge_manager:1.1::el9flightctlbefore 0:1.1.3-1.el9em0:1.1.3-1.el9em
Red Hat:edge_manager:1.1::el9flightctl-agentbefore 0:1.1.3-1.el9em0:1.1.3-1.el9em
Red Hat:edge_manager:1.1::el9flightctl-clibefore 0:1.1.3-1.el9em0:1.1.3-1.el9em
Red Hat:enterprise_linux_eus:10.0opentelemetry-collectorbefore 0:0.152.1-1.el10_00:0.152.1-1.el10_0
Red Hat:enterprise_linux:10.2opentelemetry-collectorbefore 0:0.152.1-1.el10_20:0.152.1-1.el10_2
Red Hat:enterprise_linux:9::appstreamopentelemetry-collectorbefore 0:0.152.1-1.el9_80:0.152.1-1.el9_8
Red Hat:hummingbird:1jaegerbefore 0:2.19.0-1.hum10:2.19.0-1.hum1
Red Hat:hummingbird:1opentelemetry-collectorbefore 0:0.153.0-1.hum10:0.153.0-1.hum1
Red Hat:hummingbird:1opentelemetry-collector-contribbefore 0:0.153.0-1.hum10:0.153.0-1.hum1
Red Hat:rhel_e4s:9.4::appstreamopentelemetry-collectorbefore 0:0.152.1-1.el9_40:0.152.1-1.el9_4
Red Hat:rhel_eus:9.6::appstreamopentelemetry-collectorbefore 0:0.152.1-1.el9_60:0.152.1-1.el9_6

+66

Other highest-scoring records for the same primary product.

  • CVE-2026-42154Prometheus: remote read endpoint allows denial of service via crafted snappy payload
    30Monitor
  • CVE-2021-29622Arbitrary redirects under /new endpoint
    30Monitor
  • CVE-2019-3826A stored, DOM based, cross-site scripting (XSS) flaw was found in Prometheus before version 2.7.1.
    25Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-40179Apr 15, 2026 · Prometheus: Stored XSS via metric names and label values in web UI tooltips and metrics explorer
    21Monitor
  • Later →CVE-2026-44903May 26, 2026 · Prometheus: Stored XSS via crafted histogram bucket label values in the heatmap display of the old Prometheus web UI
    20Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
azl3 telegraf 1.31.0-22 on Azure Linux 3.01.31.0-22 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:opentelemetry-collector0.152.1-1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:prometheus3.5.3+ds1-1 · Debian:14Package registry (OSV)
Go:github.com/prometheus/prometheus0.311.3Package registry (OSV)
opensuse:golang-github-prometheus-prometheus3.11.3-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:flightctl0:1.0.3-1.el9em · Red Hat:edge_manager:1.0::el9Package registry (OSV)
red hat:flightctl-agent0:1.0.3-1.el9em · Red Hat:edge_manager:1.0::el9Package registry (OSV)
red hat:flightctl-cli0:1.0.3-1.el9em · Red Hat:edge_manager:1.0::el9Package registry (OSV)
red hat:flightctl-selinux0:1.0.3-1.el9em · Red Hat:edge_manager:1.0::el9Package registry (OSV)
red hat:jaeger0:2.19.0-1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:opentelemetry-collector0:0.153.0-1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:opentelemetry-collector-contrib0:0.153.0-1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
rocky linux:opentelemetry-collector0:0.152.1-1.el10_2 · Rocky Linux:10Package registry (OSV)
suse:dracut-saltboot1.2.1-150002.3.9.1 · SUSE:Multi Linux Manager Tools SLE-15Package registry (OSV)
suse:golang-github-boynux-squid_exporter1.13.0-150002.3.6.2 · SUSE:Multi Linux Manager Tools SLE-15Package registry (OSV)
suse:golang-github-lusitaniae-apache_exporter1.0.10-150002.3.9.2 · SUSE:Multi Linux Manager Tools SLE-15Package registry (OSV)
suse:golang-github-prometheus-alertmanager0.28.1-150002.4.11.1 · SUSE:Multi Linux Manager Tools SLE-15Package registry (OSV)
suse:golang-github-prometheus-node_exporter1.10.2-150002.3.6.2 · SUSE:Multi Linux Manager Tools SLE-15Package registry (OSV)
suse:golang-github-prometheus-prometheus3.5.3-150002.3.13.1 · SUSE:Multi Linux Manager Tools SLE-15Package registry (OSV)
suse:golang-github-QubitProducts-exporter_exporter0.4.0-150002.3.6.2 · SUSE:Multi Linux Manager Tools SLE-15Package registry (OSV)
suse:grafana11.6.14+security04-150002.4.21.1 · SUSE:Multi Linux Manager Tools SLE-15Package registry (OSV)
suse:mgr-push5.2.4-150002.3.9.1 · SUSE:Multi Linux Manager Tools SLE-15Package registry (OSV)
suse:prometheus-blackbox_exporter0.26.0-150002.3.11.1 · SUSE:Multi Linux Manager Tools SLE-15Package registry (OSV)
suse:prometheus-postgres_exporter0.10.1-150002.3.3.2 · SUSE:Multi Linux Manager Tools SLE-15Package registry (OSV)
suse:python-defusedxml-sle150.7.1-150002.1.3.1 · SUSE:Multi Linux Manager Tools SLE-15Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-secondary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records