# CVE-2026-55160: Authenticated Server-Side Request Forgery (SSRF) via feed URL in Stringer

> Authenticated users can exploit SSRF in Stringer to access internal networks and cloud metadata, potentially stealing credentials.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L`)
- **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:** 28 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-496x-437q-h35q

## What is CVE-2026-55160?

CVE-2026-55160 is a high-severity server-side request forgery vulnerability in stringer-rss stringer, published on 28 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Stringer is a self-hosted, anti-social RSS reader. Prior to commit 75cb095, an unrestricted Server-Side Request Forgery (SSRF) vulnerability allows any authenticated user to force the Stringer server to send arbitrary HTTP/HTTPS requests to internal networks, localhost services, and cloud metadata endpoints (e.g. AWS IMDS 169.254.169.254). When self-service signup is enabled (Setting::UserSignup), even a low-privileged registered user can exploit this to scan internal services or steal cloud IAM credentials. This issue has been patched via commit 75cb095.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-55160?


## How do I fix CVE-2026-55160?

No fix has been published for CVE-2026-55160 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-55160 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55160 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-55160 and fix it if it is affected.

What it is: CVE-2026-55160 is a high-severity server-side request forgery vulnerability in stringer-rss stringer, published on 28 Sep 2026. 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-2026-55160 exists.

Affected product: stringer-rss stringer. 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-2026-55160/ (Markdown: https://insights.sbomify.com/CVE-2026-55160/index.md)
```

## Sources

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

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