CVE-2026-55160: stringer · Server-Side Request Forgery (SSRF)
Affects stringerSource CVE Database V5
Not known to be exploited · CVSS 7.6 High · patch available : patch stringer soon.
Data as of 12 Nov 2026, 23:24 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 28 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| stringer-rssstringer | Affected
| Fixed in– |
AI-suggested
A patch is available and has been applied in commit 75cb095. Users should update their Stringer installations to include this fix. Since this is a self-hosted application, administrators must apply the patch manually. No additional mitigation is indicated by the vendor advisory.
Description
CVE-2026-55160 is a Server-Side Request Forgery (SSRF) vulnerability in the stringer-rss Stringer application, a self-hosted RSS reader. Before a specific patch commit, authenticated users could make the server send arbitrary HTTP/HTTPS requests to internal networks, localhost, and cloud metadata endpoints such as AWS IMDS. This vulnerability allows low-privileged users, especially when self-service signup is enabled, to scan internal services or potentially steal cloud IAM credentials. The issue has been patched in commit 75cb095.