Skip to content
Threat Feed
Subscribe
high advisory

CVE-2026-65709 - sysPass JSON-RPC API Missing Object-Level Authorization

sysPass versions up to 3.2.11 are affected by a missing object-level authorization vulnerability in the JSON-RPC API. Attackers holding an API token can exploit this flaw by invoking AccountController methods (e.g., viewAction, editAction, deleteAction, editPassAction) without proper AccountFilterUser checks, allowing them to enumerate account metadata, overwrite passwords, and delete user accounts across the entire vault, bypassing per-account access control defined by their token permissions.

What's new

  • l2 added CVE-2026-65710 +1 Jul 24, 17:19 via nvd
  • l2 merged source coverage: sysPass Missing Authorization Vulnerability Allows Credential Disclosure Jul 24, 17:19 via nvd

sysPass, an open-source password manager, through version 3.2.11 is vulnerable to a critical missing object-level authorization flaw (CVE-2026-65709) in its JSON-RPC API. This vulnerability allows an attacker who has acquired any API token, even one with limited permissions, to bypass intended access controls. By directly invoking AccountController methods such as viewAction, editAction, deleteAction, and editPassAction, the attacker can perform unauthorized actions across the entire sysPass vault. This includes enumerating metadata for all accounts, overwriting any user's password, and deleting any account, completely disregarding the AccountFilterUser checks that should enforce per-account permissions. This vulnerability significantly impacts the confidentiality, integrity, and availability of sensitive credentials managed by sysPass instances.

Attack Chain

  1. Initial Access - API Token Acquisition: An attacker obtains a legitimate, but potentially low-privileged, API token for a sysPass instance through various means (e.g., compromise of a less critical user account, sniffing network traffic, misconfiguration).
  2. JSON-RPC API Interaction: The attacker sends specially crafted JSON-RPC requests to the sysPass API endpoint, targeting the AccountController.
  3. Targeting Unauthorized Methods: The requests specifically invoke AccountController methods like viewAction, editAction, deleteAction, or editPassAction.
  4. Authorization Bypass: Due to CVE-2026-65709, the sysPass application fails to enforce AccountFilterUser checks, allowing the API token to operate outside its assigned scope.
  5. Account Enumeration: By successfully invoking viewAction without proper authorization, the attacker can enumerate metadata for any account in the sysPass vault, performing unauthorized reconnaissance.
  6. Password Overwrite: Leveraging the editPassAction method, the attacker can overwrite passwords for any user account within the vault, gaining unauthorized access to those accounts.
  7. Account Modification/Deletion: The attacker can use editAction to modify account details or deleteAction to remove accounts entirely, leading to data manipulation or denial of service.
  8. Full Vault Compromise: Through these actions, the attacker achieves a full compromise of user accounts and sensitive information stored within the sysPass vault, bypassing all intended access controls.

Impact

Successful exploitation of CVE-2026-65709 leads to a complete compromise of the sysPass vault. Attackers can enumerate all account metadata, gain unauthorized access to any user account by overwriting passwords, and disrupt operations by deleting accounts. This results in severe data breaches, loss of critical credentials, and potential denial of service, affecting all users and systems whose credentials are managed by the vulnerable sysPass instance. The vulnerability bypasses fine-grained access controls, rendering existing token permissions ineffective against a determined attacker.

Recommendation

  • Patch CVE-2026-65709 immediately by upgrading sysPass to version 3.2.12 or newer to address the missing object-level authorization vulnerability.
  • Review web server access logs for any suspicious JSON-RPC API calls to AccountController methods (viewAction, editAction, deleteAction, editPassAction) that appear to originate from API tokens with insufficient permissions.
  • Implement strict network segmentation and firewall rules to limit direct access to the sysPass JSON-RPC API endpoint only to trusted internal sources.