Feed access denial via proxy-agnostic Retry-After cache
Published Dec 26, 2025 · Updated Dec 26, 2025
Denial of service in FreshRSS 1.27.0 through 1.27.1 allows remote authenticated users to block feed access through a proxy. FreshRSS_http_Util keys persisted Retry-After state only by feed domain, so a proxied HTTP 429 response with an attacker-set delay suppresses direct and other users' fetches. A FreshRSS account with permission to add feeds and configure a proxy is required, and repeating the request across popular domains can interrupt feed updates for most users.
Summary
What happened
Denial of service in FreshRSS 1.27.0 through 1.27.1 allows remote authenticated users to block feed access through a proxy. FreshRSS_http_Util keys persisted Retry-After state only by feed domain, so a proxied HTTP 429 response with an attacker-set delay suppresses direct and other users' fetches. A FreshRSS account with permission to add feeds and configure a proxy is required, and repeating the request across popular domains can interrupt feed updates for most users.
The record
- CVE
- CVE-2025-68148
- Published
- Dec 26, 2025
- Updated
- Dec 26, 2025
- Vendor
- FreshRSS
- Product
- FreshRSS
- Classifications
- CWE-770, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 26, 2025CVE publishedPublication date reported by the CVE source.
- Dec 26, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 1.27.0, < 1.28.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Proxy-modified HTTP 429 Retry-After proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo