Authentication bypass via manipulated id_token_hint
Published Mar 17, 2026 · Updated Mar 17, 2026
Improper authentication in Duende IdentityServer4 4.1.2 and earlier allows remote attackers to bypass authentication via id_token_hint. An undisclosed function at /connect/authorize improperly processes a manipulated id_token_hint during token renewal; no vendor mechanism details are public. The request needs no credentials but has high attack complexity; the record does not identify the resulting account or session capability.
Summary
What happened
Improper authentication in Duende IdentityServer4 4.1.2 and earlier allows remote attackers to bypass authentication via id_token_hint. An undisclosed function at /connect/authorize improperly processes a manipulated id_token_hint during token renewal; no vendor mechanism details are public. The request needs no credentials but has high attack complexity; the record does not identify the resulting account or session capability.
The record
- CVE
- CVE-2026-4349
- Published
- Mar 17, 2026
- Updated
- Mar 17, 2026
- Vendor
- Duende Software
- Product
- Duende IdentityServer
- Classifications
- CWE-287, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 17, 2026CVE publishedPublication date reported by the CVE source.
- Mar 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo