Tools / kanidm / Security

Security Deep Dive

kanidm

Security posture and CVE patch evidence from tracked releases.

Back to Tool

1 critical dependency CVE affects v1.10.3.

Audit transitive dependencies; consider upgrading or pinning replacements.

— Signed — SLSA — SBOM ✓ Security policy Weekly cadence · 7d median Active maintainer

Trust Signals — 3 of 9 Present

Evidence already collected from releases and repository metadata.

3/9 Present

Signed releases Unknown

Latest release artifact signature Latest release

—

SLSA provenance Unknown

Attestation predicate level Latest release

—

SBOM published Unknown

GitHub SBOM API Latest release

—

SECURITY.md Present

GitHub repository metadata Repository policy

Checked: 22d ago

Release cadence: weekly Present

7d median over recent releases Release history

Latest release: 13d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 2d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 13d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 13d ago

Signing assets Not active yet

.sig, .crt, cosign.pub, or similar Release asset

Latest release: 13d ago

5.6/10 Security Score

6.5/10 Scorecard

Dependency Exposure 28 transitive dependency CVEs found in the latest SBOM. 1 critical.

Security Score

A composite score aggregating Scorecard performance, CVE patch history, OpenSSF badge tier, and dependency vulnerability exposure. Score ≥ 7.0 is healthy; < 4.0 warrants attention.

epss

0.25 / 0.5

No EPSS data

freshness

1.00 / 1.0

2d stale

scorecard

2.60 / 4.0

Score 6.5/10

cve health

1.00 / 2.5

No open CVEs

patch speed

0.50 / 0.5

⚠ Estimated — no CVE patch history

kev exposure

1.50 / 1.5

No KEV exposure

supply chain risk

-1.25 / 10.0

Risk 12.5/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

4.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

8.7

10%

supply chain risk: 12.53 transitive cves: 1c/4h

Provenance trust

provenance trust

6.5

40%

scorecard score: 6.5 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 2d

Operational risk

operational risk

8.5

10%

kev exposure: clear epss max: none

How is this calculated?

The six dimensions group the legacy score signals into weighted categories: direct vulnerability status, patch responsiveness, dependency exposure, provenance checks, maintainer activity, and exploitability risk. The flat component values above remain available for compatibility.

Supply Chain Risk

Risk 12.5/100

1 Transitive critical CVEs

0 KEV-transitive CVEs

73% Dependency freshness

Scorecard

Scorecard 6.5/10

OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.

Check	Score	Reason
Maintained	10	30 commit(s) and 26 issue activity found in the last 90 days -- score normalized to 10
Code-Review	9	Found 17/18 approved changesets -- score normalized to 9
Security-Policy	10	security policy file detected
Dangerous-Workflow	10	no dangerous workflow patterns detected
Token-Permissions	0	detected GitHub workflow tokens with excessive permissions
Binary-Artifacts	10	no binaries found in the repo
CII-Best-Practices	5	badge detected: Passing
License	10	license file detected
Fuzzing	0	project is not fuzzed
Signed-Releases	-1	no releases found
Branch-Protection	-1	internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
Packaging	10	packaging workflow detected
SAST	0	SAST tool is not run on all commits -- score normalized to 0
Pinned-Dependencies	0	dependency not pinned by hash detected -- score normalized to 0

Dependency Vulnerabilities

998 dependencies scanned View full dependency list →

Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.

Critical

High

Medium

Low

Unknown

Still affecting latest (11) All (28)

Critical 1 High 4 Medium 10 Low 11 Unknown 2

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2026-27962	critical	—	authlib	1.6.6	v1.10.1
CVE-2026-26007	high	—	cryptography	45.0.6	v1.10.1
CVE-2026-28490	high	—	authlib	1.6.6	v1.10.1
CVE-2026-28498	high	—	authlib	1.6.6	v1.10.1
CVE-2026-28802	high	—	authlib	1.6.6	v1.10.1
CVE-2023-49092	medium	—	rsa	0.9.10	v1.10.1
CVE-2025-69873	medium	—	ajv	6.12.6	v1.10.1
CVE-2025-71176	medium	—	pytest	8.4.1	v1.10.1
CVE-2026-22815	medium	—	aiohttp	3.13.3	v1.10.1
CVE-2026-33750	medium	—	brace-expansion	1.1.11	v1.10.1
CVE-2026-34515	medium	—	aiohttp	3.13.3	v1.10.1
CVE-2026-34516	medium	—	aiohttp	3.13.3	v1.10.1
CVE-2026-34525	medium	—	aiohttp	3.13.3	v1.10.1
CVE-2026-39892	medium	—	cryptography	45.0.6	v1.10.1
CVE-2026-41425	medium	—	authlib	1.6.6	v1.10.1
CVE-2025-5889	low	—	brace-expansion	1.1.11	v1.10.1
CVE-2026-34073	low	—	cryptography	45.0.6	v1.10.1
CVE-2026-34513	low	—	aiohttp	3.13.3	v1.10.1
CVE-2026-34514	low	—	aiohttp	3.13.3	v1.10.1
CVE-2026-34517	low	—	aiohttp	3.13.3	v1.10.1
CVE-2026-34518	low	—	aiohttp	3.13.3	v1.10.1
CVE-2026-34519	low	—	aiohttp	3.13.3	v1.10.1
CVE-2026-34520	low	—	aiohttp	3.13.3	v1.10.1
CVE-2026-4539	low	—	pygments	2.19.2	v1.10.1
GHSA-2p6r-x3vv-xqm2	low	—	rpassword	5.0.1	v1.10.1
GHSA-xffm-g5w8-qvg7	low	—	@eslint/plugin-kit	0.2.4	v1.10.1
RUSTSEC-2021-0127	unknown	—	serde_cbor	0.11.2	v1.10.1
RUSTSEC-2024-0436	unknown	—	paste	1.0.15	v1.10.1

Showing 28 of 28