CVE-2026-65696: Authorization Bypass Through User-Controlled Key in sct overseerr
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.
AI Analysis
Technical Summary
CVE-2026-65696 describes an authorization bypass vulnerability in Overseerr through version 1.35.0. The issue exists in the push subscription API where authenticated users can manipulate the userId path parameter to access or delete push subscriptions belonging to other users. The root cause is the absence of ownership verification in the affected API handlers, which leads to unauthorized access to sensitive user information including email addresses and plexId values. This vulnerability is classified with a medium severity and a CVSS 4.0 base score of 5.3. There is no vendor advisory or patch available at this time, and the product is not a cloud service, so remediation depends on vendor updates or user mitigation.
Potential Impact
Exploitation of this vulnerability allows authenticated users to bypass authorization controls and access or delete push subscription data of other users. This results in unauthorized disclosure of sensitive personal information such as email addresses and plexId identifiers. The impact is limited to authenticated users and does not require user interaction. The vulnerability does not escalate privileges beyond the authenticated user context but compromises user privacy and data integrity within the application.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, restrict access to the push subscription API to trusted users only and monitor for suspicious activity involving userId parameters. Consider implementing custom access controls or temporary workarounds to enforce ownership verification on push subscription operations.
CVE-2026-65696: Authorization Bypass Through User-Controlled Key in sct overseerr
Description
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.
CVSS v4.0
Score 5.3medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-65696 describes an authorization bypass vulnerability in Overseerr through version 1.35.0. The issue exists in the push subscription API where authenticated users can manipulate the userId path parameter to access or delete push subscriptions belonging to other users. The root cause is the absence of ownership verification in the affected API handlers, which leads to unauthorized access to sensitive user information including email addresses and plexId values. This vulnerability is classified with a medium severity and a CVSS 4.0 base score of 5.3. There is no vendor advisory or patch available at this time, and the product is not a cloud service, so remediation depends on vendor updates or user mitigation.
Potential Impact
Exploitation of this vulnerability allows authenticated users to bypass authorization controls and access or delete push subscription data of other users. This results in unauthorized disclosure of sensitive personal information such as email addresses and plexId identifiers. The impact is limited to authenticated users and does not require user interaction. The vulnerability does not escalate privileges beyond the authenticated user context but compromises user privacy and data integrity within the application.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, restrict access to the push subscription API to trusted users only and monitor for suspicious activity involving userId parameters. Consider implementing custom access controls or temporary workarounds to enforce ownership verification on push subscription operations.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-22T20:26:09.979Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a6246fe9c2644c7f8644e72
Added to database: 07/23/2026, 16:53:18 UTC
Last enriched: 07/23/2026, 17:07:57 UTC
Last updated: 07/23/2026, 21:44:08 UTC
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.