Privilege escalation via SSRF when using HTTP auth
FreshRSS is a self-hosted RSS feed aggregator. Prior to version 1.26.2, when the server is using HTTP auth via reverse proxy, it's possible to impersonate any user either via the `Remote-User` header or the `X-WebAuth-User` header by making specially crafted requests via the add feed functionality and obtaining the CSRF token via XPath scraping. The attacker has to know the IP address of the proxied FreshRSS instance and the admin's username, while also having an account on the instance. An attacker can send specially crafted requests in order to gain unauthorized access to internal services. This can also lead to privilege escalation like in the demonstrated scenario, although users that have setup OIDC are not affected by privilege escalation. Version 1.26.2 contains a patch for the issue.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2025-46341
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 8 Nov 2026, 03:07 UTC · Revision 1
Source evidence
Privilege escalation via SSRF when using HTTP auth
core-osv · Original sourcePublished 4 Jun 2025, 20:09 UTC
FreshRSS is a self-hosted RSS feed aggregator. Prior to version 1.26.2, when the server is using HTTP auth via reverse proxy, it's possible to impersonate any user either via the `Remote-User` header or the `X-WebAuth-User` header by making specially crafted requests via the add feed functionality and obtaining the CSRF token via XPath scraping. The attacker has to know the IP address of the proxied FreshRSS instance and the admin's username, while also having an account on the instance. An attacker can send specially crafted requests in order to gain unauthorized access to internal services. This can also lead to privilege escalation like in the demonstrated scenario, although users that have setup OIDC are not affected by privilege escalation. Version 1.26.2 contains a patch for the issue.
osv:CVE-2025-46341
Complete source record
{
"id": "caaf24212259d8a256bffa909f38508f2e0dfc35977123764ac9478eac884b7a",
"url": "https://osv.dev/vulnerability/CVE-2025-46341",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Privilege escalation via SSRF when using HTTP auth",
"summary": "FreshRSS is a self-hosted RSS feed aggregator. Prior to version 1.26.2, when the server is using HTTP auth via reverse proxy, it's possible to impersonate any user either via the `Remote-User` header or the `X-WebAuth-User` header by making specially crafted requests via the add feed functionality and obtaining the CSRF token via XPath scraping. The attacker has to know the IP address of the proxied FreshRSS instance and the admin's username, while also having an account on the instance. An attacker can send specially crafted requests in order to gain unauthorized access to internal services. This can also lead to privilege escalation like in the demonstrated scenario, although users that have setup OIDC are not affected by privilege escalation. Version 1.26.2 contains a patch for the issue.",
"evidence": "osv:CVE-2025-46341",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2025-46341",
"aliases": [
"CVE-2025-46341",
"GHSA-w3m8-wcf4-h8vm"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/freshrss/freshrss",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "4c5e8e77b3bbf5d72f801902198bcb967e5a0358"
},
{
"fixed": "6bb8680ae0051b9a2ff344f17814f4fa5d844628"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:freshrss:freshrss:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "1.26.2"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "6bb8680ae0051b9a2ff344f17814f4fa5d844628"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"1.26.1",
"1.26.0",
"1.25.0",
"1.24.3",
"1.24.2",
"1.24.1",
"1.24.0",
"1.23.1",
"1.23.0",
"1.22.1",
"1.22.0",
"1.21.0",
"1.20.1",
"1.20.0",
"1.19.2",
"1.19.1",
"1.19.0",
"1.18.1",
"1.18.0",
"1.17.0",
"1.16.2",
"1.16.1",
"1.16.0",
"1.15.2",
"1.15.1",
"1.15.0",
"1.14.3",
"1.14.2",
"1.14.1",
"1.14.0",
"1.13.1",
"1.13.0",
"1.12.0",
"1.11.2",
"1.11.1",
"1.11.0",
"1.10.2",
"1.10.1",
"1.10.0",
"1.9.0",
"1.8.0",
"1.6.1",
"1.7.0",
"1.6.3",
"1.6.2",
"0.7.1",
"1.6.0",
"1.5.0",
"1.4.0",
"1.2.0",
"1.0.0",
"0.8.1",
"0.8.0",
"0.7.0",
"0.6.1",
"0.6.0",
"0.5.0",
"0.1.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-46341.json"
}
}
],
"modified": "2026-10-28T02:30:53.507466031Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/46xxx/CVE-2025-46341.json",
"https://github.com/FreshRSS/FreshRSS/security/advisories/GHSA-w3m8-wcf4-h8vm",
"https://nvd.nist.gov/vuln/detail/CVE-2025-46341",
"https://github.com/FreshRSS/FreshRSS/commit/6bb8680ae0051b9a2ff344f17814f4fa5d844628"
],
"provider_metadata": {
"cwe_ids": [
"CWE-918"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/46xxx/CVE-2025-46341.json"
}
},
"related_cves": [
{
"value": "CVE-2025-46341",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 522072,
"published_at": "2025-06-04T20:09:18.479+00:00"
}