# CVE-2023-27161: Server-side request forgery in n/a

> Attackers can exploit an SSRF vulnerability in Jellyfin to access internal network resources and sensitive information via crafted requests.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Mar 2023
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-cw4m-8qhc-m96h

## What is CVE-2023-27161?

CVE-2023-27161 is a high-severity server-side request forgery vulnerability in n/a, published on 10 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jellyfin up to v10.7.7 was discovered to contain a Server-Side Request Forgery (SSRF) via the component /Repositories. This vulnerability allows attackers to access network resources and sensitive information via a crafted POST request.

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

## Which versions are affected by CVE-2023-27161?

It affects 1 product.


Products: Jellyfin Jellyfin.

## How do I fix CVE-2023-27161?

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

## Is CVE-2023-27161 being exploited?

There is no known exploitation of CVE-2023-27161 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2026-35031](https://insights.sbomify.com/CVE-2026-35031/): Jellyfin: Potential RCE via subtitle upload path traversal + .strm chain (critical 10.0)
- [CVE-2026-31852](https://insights.sbomify.com/CVE-2026-31852/): Jellyfin Possible Organization/Secret Compromise from dangerous CI implementation (critical 10.0)
- [CVE-2026-35033](https://insights.sbomify.com/CVE-2026-35033/): Jellyfin: Potential SSRF + Arbitrary file read via stream argument injection (critical 9.3)
- [CVE-2023-30627](https://insights.sbomify.com/CVE-2023-30627/): jellyfin-web has a stored cross-site scripting vulnerability in devices.js (critical 9.1)
- [CVE-2023-30626](https://insights.sbomify.com/CVE-2023-30626/): Jellyfin vulnerable to directory traversal and file write causing arbitrary code execution (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-27161 and fix it if it is affected.

What it is: CVE-2023-27161 is a high-severity server-side request forgery vulnerability in n/a, published on 10 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-27161 in the wild and no public exploit code.

Affected product: n/a. 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-2023-27161/ (Markdown: https://insights.sbomify.com/CVE-2023-27161/index.md)
```

## Sources

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

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