Security readout for executives and security teams
Plain-English summary
Seerr before 3.1.0 can expose users’ third-party notification credentials to any logged-in user. The exposed data may include Pushover, Pushbullet, and Telegram credentials. This is mainly a confidentiality issue, but the impact increases if paired with CVE-2026-27707, which could allow credential leakage without prior access.
Executive priority
Prioritize remediation for internet-facing Seerr instances or environments with untrusted users. The business risk is leakage of third-party notification credentials, including administrator credentials. Upgrade is available in version 3.1.0, which also fixes the related account creation issue.
Technical view
CVE-2026-27793 is a broken object-level authorization issue in GET /api/v1/user/:id. Before Seerr 3.1.0, the endpoint returned a full settings object for any user to any authenticated requester, regardless of privilege. The CVSS 3.1 score is 6.5, with high confidentiality impact and no integrity or availability impact stated.
Likely exposure
Organizations running seerr-team Seerr versions earlier than 3.1.0 are affected. Exposure is higher where Seerr is internet-accessible or where untrusted users can authenticate. The advisory states this can be combined with CVE-2026-27707 for a zero-prior-access chain.
Exploitation context
Public sources describe the vulnerability and its chainability with CVE-2026-27707. The provided sources do not state active exploitation, and the CVE is not marked as CISA KEV. Treat exploitation as plausible where attackers can authenticate or create accounts through the paired issue.
Researcher notes
This is CWE-639, broken object-level authorization. The key research focus is whether the user profile endpoint returned complete settings across user IDs before 3.1.0. Avoid assuming broader Seerr data exposure beyond the credentials named in the advisory.
Mitigation direction
- Upgrade Seerr to version 3.1.0 or later.
- Review vendor advisory and release notes for any additional operational guidance.
- Rotate exposed Pushover, Pushbullet, and Telegram credentials if compromise is possible.
- Restrict Seerr access to trusted users and networks where feasible.
Validation and detection
- Inventory Seerr instances and identify versions older than 3.1.0.
- Confirm whether user self-registration or unauthenticated account creation is possible.
- Review logs for unusual user profile access patterns.
- Verify third-party notification tokens were rotated where exposure may have occurred.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-27793 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/seerr-team/seerr/security/advisories/GHSA-f7xw-jcqr-57hpCVE reference · x_refsource_CONFIRM
- https://github.com/seerr-team/seerr/commit/4f089b29d0bb41d382168b17aa152eb5b8a25303CVE reference · x_refsource_MISC
- https://github.com/seerr-team/seerr/releases/tag/v3.1.0CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.