CVE-2025-46339 FreshRSS vulnerable to favicon cache poisoning via proxy

Medium 4.3 Published Updated

Attackers can poison RSS feed favicons for all users by exploiting proxy settings and weak cache key generation in FreshRSS.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2025-46339?

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.

Official 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.

Weakness: CWE-349

Which versions are affected by CVE-2025-46339?

It affects 1 product.

Products include Freshrss Freshrss.

How do I fix CVE-2025-46339?

No fix has been published for CVE-2025-46339 yet. Limit exposure of the affected software until one is available.

Is CVE-2025-46339 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46339 exists.

Sources

Also known as GHSA-8f79-3q3w-43c4.

Is CVE-2025-46339 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free