{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62166 exists.","fix":"No fix has been published for CVE-2025-62166 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-62166 is a high-severity missing authorization vulnerability in FreshRSS, published on 9 Mar 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-2025-62166 and fix it if it is affected.\n\nWhat it is: CVE-2025-62166 is a high-severity missing authorization vulnerability in FreshRSS, published on 9 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62166 exists.\n\nAffected product: FreshRSS. 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-2025-62166/ (Markdown: https://insights.sbomify.com/CVE-2025-62166/index.md)","id":"CVE-2025-62166","markdown":"https://insights.sbomify.com/CVE-2025-62166/index.md","name":"CVE-2025-62166","record":{"aliases":["GHSA-w743-fg6g-mhwh"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"RSS aggregator","requires_auth":"none","summary":"Attackers can view private feeds and leak tokens of any user by bypassing authentication restrictions in FreshRSS.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"freshrss","vendor":"freshrss"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"},{"id":"CWE-284","name":"Improper Access Control"}],"description":"FreshRSS is a free, self-hostable RSS aggregator. Prior 1.28.0, a bug in the auth logic related to master authentication tokens, this restriction is bypassed. Usually only the default user's feed should be viewable if anonymous viewing is enabled, and feeds of other users should be private. This vulnerability is fixed in 1.28.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"FreshRSS has an IDOR which allows for viewing feeds of any user and leaking tokens","id":"CVE-2025-62166","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Squid vulnerable to information disclosure via authentication credential leakage in error handling","id":"CVE-2025-62168"},"packages":[],"prev":{"headline":"VLLM deserialization vulnerability leading to DoS and potential RCE","id":"CVE-2025-62164"},"products":["FreshRSS"],"published":"2026-03-09","related":[{"cvss_score":9.8,"headline":"FreshRSS: Unauthorized creation of admin user when registration is enabled","id":"CVE-2025-54875","kev_date_added":null,"published":"2025-09-29"},{"cvss_score":8.8,"headline":"FreshRSS has Incomplete Session Termination on Logout","id":"CVE-2025-54592","kev_date_added":null,"published":"2025-09-29"},{"cvss_score":7.5,"headline":"FreshRSS: Unauthenticated users can view default user's information","id":"CVE-2025-54591","kev_date_added":null,"published":"2025-09-29"},{"cvss_score":7.4,"headline":"FreshRSS vulnerable to authenticated RCE via path traversal inside include()","id":"CVE-2025-58173","kev_date_added":null,"published":"2025-12-15"},{"cvss_score":7.2,"headline":"FreshRSS is vulnerable to RCE attacks by authenticated admin","id":"CVE-2025-54593","kev_date_added":null,"published":"2025-08-01"},{"cvss_score":7.1,"headline":"Privilege escalation via SSRF when using HTTP auth","id":"CVE-2025-46341","kev_date_added":null,"published":"2025-06-04"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-09","vendors":["FreshRSS"]},"summary":"Attackers can view private feeds and leak tokens of any user by bypassing authentication restrictions in FreshRSS.","url":"https://insights.sbomify.com/CVE-2025-62166/"}