Security Updates - November 16, 2026
Damian Hickey Head of Engineering
We've published several security advisories for Duende products including IdentityServer and BFF, along with updated packages that fix them. We strongly recommend updating to the latest patched releases.
IdentityServer
- GHSA-mv65-jhg4-3qh6: mTLS client authentication can be bypassed with a self-signed certificate that matches the expected subject name.
- GHSA-4xw7-58r7-8h6h: Signing in with server-side sessions reuses an existing session key, which allows session fixation.
- GHSA-qqfr-626g-64rp: A DPoP proof key confusion allows leaked DPoP refresh and access tokens to be used.
- GHSA-wcc6-7mjx-g6j5: Incorrectly formatted SAML messages can cause a denial of service.
- GHSA-hmrv-xfgm-wgh2: The SAML service provider doesn't validate bearer SubjectConfirmationData.
- GHSA-478v-p4g7-f7g4: id_token_hint isn't validated thoroughly enough.
- GHSA-6xhh-5qhq-m9vf: The SAML service provider ends a session when it receives a logout request from a different identity provider.
- GHSA-hhqg-4hp5-4v5h: The SAML service provider accepts a changed RelayState in signed HTTP-Redirect messages.
BFF
- GHSA-x394-gwr7-4885: Responses from proxied APIs can set session cookies, and signing in then reuses that planted server-side session.
- GHSA-6gxg-chg2-rm9v: Static asset proxying can forward requests to arbitrary URLs.
Duende.AspNetCore.Authentication.JwtBearer
- GHSA-rhcf-m7hh-vpm7: A DPoP proof key confusion allows leaked DPoP access tokens to be used.
Duende.AspNetCore.Authentication.OAuth2Introspection
- GHSA-84rm-mhfq-f476: OAuth2Introspection accepts a token on one authentication scheme based on another scheme's introspection result.
Please review the ones that apply to the products you use and update as soon as you can.