{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46339 exists.","fix":"No fix has been published for CVE-2025-46339 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-46339 is a medium-severity vulnerability in FreshRSS, published on 4 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-46339 and fix it if it is affected.\n\nWhat it is: CVE-2025-46339 is a medium-severity vulnerability in FreshRSS, published on 4 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46339 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-46339/ (Markdown: https://insights.sbomify.com/CVE-2025-46339/index.md)","id":"CVE-2025-46339","markdown":"https://insights.sbomify.com/CVE-2025-46339/index.md","name":"CVE-2025-46339","record":{"aliases":["GHSA-8f79-3q3w-43c4"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"RSS feed aggregator","requires_auth":"low_privilege","summary":"Attackers can poison RSS feed favicons for all users by exploiting proxy settings and weak cache key generation in FreshRSS.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"freshrss","vendor":"freshrss"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-349","name":"Acceptance of Extraneous Untrusted Data With Trusted Data"}],"description":"FreshRSS is a self-hosted RSS feed aggregator. Prior to version 1.26.2, it's possible to poison feed favicons by adding a given URL as a feed with the proxy set to an attacker-controlled one and disabled SSL verifying. The favicon hash is computed by hashing the feed URL and the salt, whilst not including the following variables: proxy address, proxy protocol, and whether SSL should be verified. Therefore it's possible to poison a favicon of a given feed by simply intercepting the response of the feed, and changing the website URL to one where a threat actor controls the feed favicon. Feed favicons can be replaced for all users by anyone. Version 1.26.2 fixes the issue.","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 vulnerable to favicon cache poisoning via proxy","id":"CVE-2025-46339","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Misskey CSS Style Injection Vulnerability In `MkUrlPreview`","id":"CVE-2025-46340"},"packages":[],"prev":{"headline":"Audiobookshelf Vulnerable to Cross-Site-Scripting Reflected via POST Request in /api/upload","id":"CVE-2025-46338"},"products":["FreshRSS"],"published":"2025-06-04","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 has an IDOR which allows for viewing feeds of any user and leaking tokens","id":"CVE-2025-62166","kev_date_added":null,"published":"2026-03-09"},{"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-04","vendors":["FreshRSS"]},"summary":"Attackers can poison RSS feed favicons for all users by exploiting proxy settings and weak cache key generation in FreshRSS.","url":"https://insights.sbomify.com/CVE-2025-46339/"}