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

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

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jun 2025
- **Updated:** 4 Jun 2025
- **Also known as:** GHSA-8f79-3q3w-43c4

## 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 (Acceptance of Extraneous Untrusted Data With Trusted Data)

## Which versions are affected by CVE-2025-46339?

It affects 1 product.


Products: 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.

## Other vulnerabilities in FreshRSS

- [CVE-2025-54875](https://insights.sbomify.com/CVE-2025-54875/): FreshRSS: Unauthorized creation of admin user when registration is enabled (critical 9.8)
- [CVE-2025-54592](https://insights.sbomify.com/CVE-2025-54592/): FreshRSS has Incomplete Session Termination on Logout (high 8.8)
- [CVE-2025-62166](https://insights.sbomify.com/CVE-2025-62166/): FreshRSS has an IDOR which allows for viewing feeds of any user and leaking tokens (high 7.5)
- [CVE-2025-54591](https://insights.sbomify.com/CVE-2025-54591/): FreshRSS: Unauthenticated users can view default user's information (high 7.5)
- [CVE-2025-58173](https://insights.sbomify.com/CVE-2025-58173/): FreshRSS vulnerable to authenticated RCE via path traversal inside include() (high 7.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-46339 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46339 exists.

Affected product: FreshRSS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-46339/ (Markdown: https://insights.sbomify.com/CVE-2025-46339/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-46339
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-46339
- OSV: https://osv.dev/vulnerability/CVE-2025-46339

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-46339/
Summaries are generated and may contain mistakes; the official description above is the record.