{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-26069 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-26069 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-26069 is a critical vulnerability in thecfu scraparr, published on 12 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-26069 and fix it if it is affected.\n\nWhat it is: CVE-2026-26069 is a critical vulnerability in thecfu scraparr, published on 12 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-26069 in the wild and no public exploit code.\n\nAffected product: thecfu scraparr. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-26069/ (Markdown: https://insights.sbomify.com/CVE-2026-26069/index.md)","id":"CVE-2026-26069","markdown":"https://insights.sbomify.com/CVE-2026-26069/index.md","name":"CVE-2026-26069","record":{"aliases":["GHSA-hx24-222f-w5cj"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Prometheus exporter","requires_auth":"none","summary":"Attackers can read the Readarr API key if the metrics endpoint is public and specific integration settings are active.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"scraparr","vendor":"thecfu"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:L","version":"4.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Scraparr Readarr Integration exposes sensitive values as metric labels.","id":"CVE-2026-26069","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"EVerest: OCPP 2.0.1 EV SoC Update Race Causes Charge Point Crash","id":"CVE-2026-26070"},"packages":[],"prev":{"headline":"emp3r0r Agent-Controlled Metadata to Operator RCE (tmux Command Injection)","id":"CVE-2026-26068"},"products":["scraparr"],"published":"2026-02-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-13","vendors":["thecfu"]},"summary":"Attackers can read the Readarr API key if the metrics endpoint is public and specific integration settings are active.","url":"https://insights.sbomify.com/CVE-2026-26069/"}