sysPass through version 3.2.11 contains a missing object-level authorization vulnerability in the JSON-RPC API that allows API token holders to enumerate account metadata, overwrite passwords, and delete accounts across the entire vault without per-account access control. Attackers can invoke AccountController methods such as viewAction, editAction, deleteAction, and editPassAction without AccountFilterUser checks to modify or delete accounts beyond the scope of their assigned token permissions.
CVE-2026-65709
Score 8.3 from GitHub Security Advisory (severity: HIGH) published 2026-07-24. the CNA's CVSS baseline 8.3; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.3
- EG Score
- 8.3(high)
- EG Risk
- 53(Track*)EG Risk 53/100SSVC: Track*
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity83% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 13%
- KEV
- Not listed
Published
July 24, 2026
Last Modified
July 28, 2026
Advisory Details (2)
Auto-updated Jul 24, 2026sysPass 3.2.11 Missing Object-Level Authorization via JSON-RPC API | Advisories | VulnCheck
https://www.vulncheck.com/advisories/syspass-missing-object-level-authorization-via-json-rpc-apicve-advisories/2026/sysPass/CVE-2026-65709.md at main · Caycon/cve-advisories · GitHub
https://github.com/Caycon/cve-advisories/blob/main/2026/sysPass/CVE-2026-65709.mdVendor Advisories for CVE-2026-65709(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 22× in last 7d / 22× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-29 00:58 UTCEG score recompute
- 2026-07-29 00:58 UTCGHSA enrichment
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-28 13:15 UTCGHSA enrichment
- 2026-07-28 01:30 UTCEG score recompute
- 2026-07-28 01:30 UTCGHSA enrichment
- 2026-07-27 20:43 UTCGHSA enrichment
- 2026-07-27 15:04 UTCEG score recompute
- 2026-07-27 15:04 UTCGHSA enrichment
- 2026-07-27 14:14 UTCEPSS rescore
- 2026-07-27 02:25 UTCEG score recompute
- 2026-07-27 02:25 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:40 UTCEG score recompute
- 2026-07-26 14:40 UTCGHSA enrichment
- 2026-07-26 02:57 UTCEG score recompute
- 2026-07-26 02:56 UTCGHSA enrichment
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 16:54 UTCEG score recompute
- 2026-07-24 16:52 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2019-25487EG 9.8EPSS p94CRITICAL
- CVE-2019-25235EG 9.8CRITICAL
- CVE-2019-15310EG 9.8EPSS p94CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS p97CRITICAL
- CVE-2019-13360EG 9.8EPSS p98CRITICAL
- CVE-2019-12866EG 9.8CRITICAL
- CVE-2019-9756EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-65709?
When was CVE-2026-65709 disclosed?
Is CVE-2026-65709 actively exploited?
What is the CVSS score of CVE-2026-65709?
How do I remediate CVE-2026-65709?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-65709
Is Your Infrastructure Affected by CVE-2026-65709?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.