Kanidm is an identity management platform. Prior to version 1.9.3, a single unauthenticated GET to any /scim/v1/... endpoint with a ?filter= query string of a few thousand nested parentheses (≈ 4–12 KB) drives the recursive-descent PEG parser past the worker thread's stack guard page. Rust responds to stack overflow with std::process::abort() — the entire kanidmd process exits. The parse runs inside axum's Query extractor, before any handler body and therefore before any ACL check. This issue has been patched in version 1.9.3.
CVE-2026-46689
This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- 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.7
- EG Score
- 8.7(medium)
- EPSS
- 23.5%
- KEV
- Not listed
Published
May 6, 2026
Last Modified
June 11, 2026
Advisory Details (2)
Auto-updated Jun 11, 2026Unauthenticated process abort via SCIM filter stack exhaustion · Advisory · kanidm/kanidm · GitHub
https://github.com/kanidm/kanidm/security/advisories/GHSA-r5fr-9gmv-jgghv1.9.3
Patch available: kanidm/kanidm v1.9.3
https://github.com/kanidm/kanidm/releases/tag/v1.9.3Vendor Advisories for CVE-2026-46689(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 1 ecosystem)
crates.io(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| kanidm_proto | — | 1.9.3 | — |
| scim_proto | — | 1.9.3 | — |
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 45× 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-08 15:16 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 14:44 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 23:04 UTCEG score recompute
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
Show 21 moreShow fewer
- 2026-06-19 19:26 UTCEPSS rescore
- 2026-06-19 19:26 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-17 17:53 UTCEPSS rescore
- 2026-06-16 17:53 UTCEPSS rescore
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 06:22 UTCEG score recompute
- 2026-06-14 18:41 UTCEG score recompute
- 2026-06-14 07:12 UTCEG score recompute
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 22:09 UTCEG score recompute
- 2026-06-12 09:43 UTCEG score recompute
- 2026-06-11 22:01 UTCEG score recompute
- 2026-06-11 14:00 UTCEPSS rescore
- 2026-06-11 10:31 UTCEG score recompute
- 2026-06-10 23:01 UTCEG score recompute▲ 8.70
- 2026-06-10 23:00 UTCNVD updateCVSS v3 → 8.7 · CVSS v4 → 8.7
- 2026-05-24 06:19 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-400 · CWE-248
Frequently asked(5)
What is CVE-2026-46689?
When was CVE-2026-46689 disclosed?
Is CVE-2026-46689 actively exploited?
What is the CVSS score of CVE-2026-46689?
How do I remediate CVE-2026-46689?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46689
Is Your Infrastructure Affected by CVE-2026-46689?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.