Kanidm: Stored HTML injection in "passkey-enrolment" partial via displayname → htmx-driven authenticated request forgery

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.1 · CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary The kanidmd web UI renders the WebAuthn passkey-registration challenge as raw JSON inside an inline <script id="data" element using the Askama |safe filter. The challenge embeds the account's displayname, which serdejson serialises without escaping </. A displayname containing </script therefore terminates the script element early and injects arbitrary HTML into the credential-update page. Because the page is htmx-driven and the server's CSP allows 'unsafe-eval', injected hx- attributes can issue authenticated same-origin API requests with the viewer's bearer cookie. Impact An authenticated attacker who is a member of idmpeopleadmins can write the displayname of any Person entry — including high-privilege persons — because idmacppeoplepiimanage carries no high-privilege exclusion filter. When the targeted high-privilege user later opens Add Passkey on their own credential-update page (/ui/reset), the injected markup is swapped into the DOM and htmx fires attacker-chosen…

Published by the source

6 May 2026, 23:34 UTC

Last modified by the source

6 May 2026, 23:34 UTC

Source last checked

26 Oct 2026, 15:42 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-gpxg-fx2g-qxj2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-gpxg-fx2g-qxj2

Advisory: Kanidm: Stored HTML injection in "passkey-enrolment" partial via displayname → htmx-driven authenticated request forgery
IDs: GHSA-gpxg-fx2g-qxj2
Record: https://patchnext.com/advisories/ghsa-gpxg-fx2g-qxj2 (revision 1, source checked 26 Oct 2026, 15:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: kanidm 1.9.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io kanidm: affected <= 1.9.2; fixed in 1.9.3

## Suggested inspection (read-only)
- crates.io kanidm: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on kanidm.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gpxg-fx2g-qxj2 (GitHub-reviewed advisory GHSA-gpxg-fx2g-qxj2 lists affected ranges: crates.io kanidm >=0 <=1.9.2)

Commands are suggestions: review each one before running it.