CVE-2026-26069
Prometheus Scraparr exporter leaks Readarr API key via /metrics when exposed.
Is CVE-2026-26069 being exploited?
Not confirmed. CVE-2026-26069 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.31% probability of exploitation in the next 30 days.
How severe is CVE-2026-26069?
CVE-2026-26069 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-26069?
Yes. A fix has been recorded for CVE-2026-26069. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-26069 affect?
CVE-2026-26069 affects Scraparr Prometheus Exporter (Readarr integration) <= 3.0.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-26069?
Upgrade to 3.0.2 or newer
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
API key disclosure via public /metrics allows unauthorized Readarr access and abuse.
Patch when possible
- affected>= 3.0.0-beta and < 3.0.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.