What is the CVSS score of CVE-2026-26069?

CVE-2026-26069 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.0%.

Which versions of Prometheus are affected by CVE-2026-26069?

Scraparr versions 3.0.0-beta through 3.0.1 unintentionally exposed Readarr API credentials in monitoring metrics when the Readarr integration was enabled, creating a credential disclosure…. A patch is available.

How to fix or mitigate CVE-2026-26069?

Within 24 hours: Identify all Scraparr instances running versions 3.0.0-beta to 3.0.1 with Readarr integration enabled and immediately rotate all exposed Readarr API keys. Within 7 days: Apply vendor patch to upgrade all affected Scraparr instances to version 3.0.2 or later. Within 30 days: Conduct a security audit to identify any unauthorized access to exposed metrics endpoints and review access logs for the Prometheus environment.

Prometheus CVE-2026-26069

HIGH

Information Exposure (CWE-200)

2026-02-12 security-advisories@github.com

Prometheus Industrial Scraparr

7.5

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

7.5 HIGH

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

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Generated

Mar 12, 2026 - 22:02 vuln.today

Patch released

Feb 23, 2026 - 16:58 nvd

Patch available

CVE Published

Feb 12, 2026 - 22:16 nvd

HIGH 7.5

DescriptionGitHub Advisory

Scraparr is a Prometheus Exporter for various components of the *arr Suite. From 3.0.0-beta to before 3.0.2, when the Readarr integration was enabled, the exporter exposed the configured Readarr API key as the alias metric label value. Users were affected only if all of the following conditions are met, Readarr scraping feature was enabled and no alias configured, the exporter’s /metrics endpoint was accessible to external or unauthorized users, and the Readarr instance is externally accessible. If the /metrics endpoint was publicly accessible, the Readarr API key could have been disclosed via exported metrics data. This vulnerability is fixed in 3.0.2.

AnalysisAI

Scraparr versions 3.0.0-beta through 3.0.1 expose Readarr API keys in plaintext through the /metrics endpoint when the Readarr integration is enabled without a custom alias configured. An attacker with access to the publicly exposed /metrics endpoint can harvest valid API credentials to compromise an externally accessible Readarr instance. This vulnerability affects only deployments where Readarr scraping is enabled, no alias is set, and the metrics endpoint is accessible to untrusted users.

Technical ContextAI

Classified as CWE-200 (Information Exposure). Affects Scraparr. Scraparr is a Prometheus Exporter for various components of the *arr Suite. From 3.0.0-beta to before 3.0.2, when the Readarr integration was enabled, the exporter exposed the configured Readarr API key as the alias metric label value. Users were affected only if all of the following conditions are met, Readarr scraping feature was enabled and no alias configured, the exporter’s /metrics endpoint was accessible to external or unauthorized users, and the Readarr instance is externally accessible.