CVE-2026-65696 overseerr vulnerability
Overseerr through 1.35.0 contains an authorization bypass through user-controlled key vulnerability in the push subscription API that allows authenticated users to list, read, and delete any other user's push subscriptions by supplying an arbitrary userId in the path parameters. Attackers can exploit the missing ownership check in the affected handlers to access target user records without the filteredFields filter, leaking sensitive data including email addresses and plexId values.
Browse API Security security risksQuick answer
sct overseerr should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- <= 1.35.0
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
CVE-2026-65696 affects overseerr and involves authorization failure. Successful exploitation may let a lower-privileged user view or change data outside their allowed scope. Prioritize deployments that process untrusted input, expose the affected feature, or hold sensitive data. No confirmed fixed version is recorded for CVE-2026-65696; follow the linked vendor advisory, apply its mitigation, and update overseerr as soon as a supported patched release is available.
- Inventory every deployment, device, package, plugin, container, build, and environment that uses overseerr.
- Compare the installed version with the recorded affected range: <= 1.35.0.
- No confirmed fixed version is recorded for CVE-2026-65696; follow the linked vendor advisory, apply its mitigation, and update overseerr as soon as a supported patched release is available.
- Until patched, restrict the affected API or workflow to trusted administrators and enforce an additional access-control layer at the proxy or network boundary.
- Review configuration, roles, tokens, network paths, and exposed endpoints connected to overseerr; remove access that is not required.
- Review authentication, API, audit, and object-change logs for cross-user access, bypassed checks, or unexpected privileged actions.
- If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2026-65696 in place.
- Use a safe regression test to confirm the affected authorization failure path no longer produces the vulnerable behavior.
- Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
- Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
- Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.
Related categories
Related security risks
More published guidance from the same primary category.
Trusted references
FAQ
What is affected by CVE-2026-65696?
sct overseerr versions listed as affected should be reviewed: <= 1.35.0.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.