# CVE-2026-27793: Seerr has Broken Object-Level Authorization in User Profile Endpoint that Exposes Third-Party Notification Credentials

> Authenticated users can access other users' third-party notification credentials via an unprotected API endpoint, potentially leading to account takeover.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 27 Feb 2026
- **Updated:** 2 Mar 2026
- **Also known as:** GHSA-f7xw-jcqr-57hp

## What is CVE-2026-27793?

CVE-2026-27793 is a medium-severity missing authorization vulnerability in seerr-team seerr, published on 27 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Seerr is an open-source media request and discovery manager for Jellyfin, Plex, and Emby. Prior to version 3.1.0, the `GET /api/v1/user/:id` endpoint returns the full settings object for any user, including Pushover, Pushbullet, and Telegram credentials, to any authenticated requester regardless of their privilege level. This vulnerability can be exploited alone or combined with the reported unauthenticated account creation vulnerability, CVE-2026-27707. When combined, the two vulnerabilities create a zero-prior-access chain that leaks third-party API credentials for all users, including administrators. Version 3.1.0 contains a fix for both this vulnerability and for CVE-2026-27707.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: Seerr Seerr.

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

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

## Is CVE-2026-27793 being exploited?

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

## Other vulnerabilities in seerr-team seerr

- [CVE-2026-27707](https://insights.sbomify.com/CVE-2026-27707/): Plex-configured Seerr instances vulnerable to unauthenticated account registration via Jellyfin authentication endpoint (high 7.3)
- [CVE-2026-27792](https://insights.sbomify.com/CVE-2026-27792/): Seerr missing authentication on pushSubscription endpoints (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-27793 is a medium-severity missing authorization vulnerability in seerr-team seerr, published on 27 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-27793 in the wild and no public exploit code.

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

## Sources

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

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