Skip to content
Sign in
CVE-2025-463394.3MediumCWE-349

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

FreshRSS

Affected: FreshRSS · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.2%probability of exploitation in the next 30 days
7th percentile
050100

Higher than 7% of scored CVEs

4.3MediumCVSS 3.1
LowMedium

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • FreshRSS · FreshRSS< 1.26.2

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Vendor
FreshRSS
Published
June 2025

CoverageNo articles yet

No CyberSIXT article names CVE-2025-46339 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

Updated AboutDevelopersSign in