CVE-2026-26069
Published: 12 February 2026
Summary
CVE-2026-26069 is a critical-severity Exposure of Sensitive Information to an Unauthorized Actor (CWE-200) vulnerability in Thecfu Scraparr. Its CVSS base score is 9.1 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 21.0th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified are NIST 800-53 AC-22 (Publicly Accessible Content) and SC-7 (Boundary Protection).
Deeper analysis
CVE-2026-26069 is an information disclosure vulnerability in Scraparr, a Prometheus exporter for components of the *arr Suite, affecting versions from 3.0.0-beta up to but not including 3.0.2. When the Readarr integration is enabled without an alias configured, the exporter exposes the configured Readarr API key directly as the value of the alias metric label in its Prometheus metrics. This issue, rated at CVSS 3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) and linked to CWE-200, only impacts users who have enabled Readarr scraping and left the exporter's /metrics endpoint accessible to external or unauthorized parties.
An attacker can exploit this vulnerability by accessing the publicly exposed /metrics endpoint of the Scraparr exporter over the network with no authentication required. By scraping the metrics data, they can directly extract the Readarr API key from the alias label. If the associated Readarr instance is also externally accessible, possession of this key enables further unauthorized API access to Readarr, potentially allowing data exfiltration, configuration changes, or other administrative actions depending on the key's permissions.
The vulnerability is addressed in Scraparr version 3.0.2, as detailed in the project's security advisory (GHSA-hx24-222f-w5cj), release notes, and the fixing commit (194116bb8fb0b6ea26421b3e7a7b326973f56cd0). Security practitioners should upgrade to 3.0.2 or later, ensure /metrics endpoints are not publicly exposed, configure aliases for integrations, and review access controls for Readarr instances.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-6157
Vulnerability details
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Vulnerability exposes Readarr API key via unauthenticated access to public /metrics endpoint (T1190), directly enabling credential access via insecure exposure (T1552) and theft of application access token (T1528) for subsequent Readarr abuse.
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Directly mitigates the vulnerability by identifying, reporting, and applying the patch in Scraparr 3.0.2 that prevents exposure of the Readarr API key in metrics labels.
Prevents exploitation by monitoring and controlling access to the vulnerable /metrics endpoint at system boundaries, ensuring it is not accessible to external or unauthorized users.
Requires review of publicly accessible content such as Prometheus metrics to identify and remediate exposure of sensitive information like the Readarr API key before distribution.