CVE-2026-26069
Awaiting Analysis Awaiting Analysis - Queue
Information Disclosure via Readarr API Key Exposure in Scraparr Exporter

Publication date: 2026-02-12

Last updated on: 2026-02-23

Assigner: GitHub, Inc.

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-12
Last Modified
2026-02-23
Generated
2026-05-27
AI Q&A
2026-02-13
EPSS Evaluated
2026-05-25
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
thecfu scraparr From 3.0.0 (inc) to 3.0.2 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-200 The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, upgrade Scraparr to version 3.0.2 or later where the issue is fixed.

Additionally, ensure that the /metrics endpoint is not accessible to external or unauthorized users.

If the Readarr scraping feature is enabled, consider disabling it or configuring an alias to avoid exposing the Readarr API key.


How can this vulnerability impact me? :

If you are using Scraparr with the Readarr integration enabled and the conditions for this vulnerability are met, an attacker could gain access to your Readarr API key. This could allow unauthorized access to your Readarr instance, potentially leading to data exposure or manipulation. The impact is significant because the API key is sensitive information that grants access to the Readarr service.


Can you explain this vulnerability to me?

This vulnerability affects Scraparr, a Prometheus Exporter for the *arr Suite, specifically versions from 3.0.0-beta to before 3.0.2. When the Readarr integration was enabled without an alias configured, the exporter exposed the configured Readarr API key as the alias metric label value. This means that if the /metrics endpoint was accessible to unauthorized or external users and the Readarr instance was externally accessible, the Readarr API key could be disclosed through the exported metrics data.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

I don't know


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart