CVE-2024-21643
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 2.23 % · percentile 83.06 % · scored 15 Nov 2026.
Saved 15 Nov 2026 14:45:34 UTC · View this risk record (JSON)
No access to your tenant or devices. Every item links to its source. What this means
IdentityModel Extensions for .NET provide assemblies for web developers that wish to use federated identity providers for establishing the caller's identity. Anyone leveraging the `SignedHttpRequest`protocol or the `SignedHttpRequestValidator`is vulnerable. Microsoft.IdentityModel trusts the `jku`claim by default for the `SignedHttpRequest`protocol. This raises the possibility to make any remote or local `HTTP GET` request. The vulnerability has been fixed in Microsoft.IdentityModel.Protocols.SignedHttpRequest. Users should update all their Microsoft.IdentityModel versions to 7.1.2 (for 7x) or higher, 6.34.0 (for 6x) or higher.
Read the publisher's advisoryIdentityModel Extensions for .NET provide assemblies for web developers that wish to use federated identity providers for establishing the caller's identity. Anyone leveraging the `SignedHttpRequest`protocol or the `SignedHttpRequestValidator`is vulnerable. Microsoft.IdentityModel trusts the `jku`claim by default for the `SignedHttpRequest`protocol. This raises the possibility to make any remote or local `HTTP GET` request. The vulnerability has been fixed in Microsoft.IdentityModel.Protocols.SignedHttpRequest. Users should update all their Microsoft.IdentityModel versions to 7.1.2 (for 7x) or higher, 6.34.0 (for 6x) or higher.
Read the publisher's advisoryIdentityModel Extensions for .NET provide assemblies for web developers that wish to use federated identity providers for establishing the caller's identity. Anyone leveraging the `SignedHttpRequest`protocol or the `SignedHttpRequestValidator`is vulnerable. Microsoft.IdentityModel trusts the `jku`claim by default for the `SignedHttpRequest`protocol. This raises the possibility to make any remote or local `HTTP GET` request. The vulnerability has been fixed in Microsoft.IdentityModel.Protocols.SignedHttpRequest. Users should update all their Microsoft.IdentityModel versions to 7.1.2 (for 7x) or higher, 6.34.0 (for 6x) or higher.
Read the publisher's advisory### Impact _What kind of vulnerability is it? Who is impacted?_ Anyone leveraging the `SignedHttpRequest`protocol or the `SignedHttpRequestValidator`is vulnerable. Microsoft.IdentityModel trusts the `jku`claim by default for the `SignedHttpRequest`protocol. This raises the possibility to make any remote or local `HTTP GET` request. ### Patches _Has the problem been patched? What versions should users upgrade to?_ The vulnerability has been fixed in Microsoft.IdentityModel.Protocols.SignedHttpRequest. Users **should** update **all** their Microsoft.IdentityModel versions to 7.1.2 (for 7x) or higher, 6.34.0 (for 6x) or higher, if using Microsoft.IdentityModel.Protocols.SignedHttpRequest. ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ No, users must upgrade. ### References _Are there any links users can visit to find out more?_ https://aka.ms/IdentityModel/Jan2024/jku
Read the publisher's advisoryCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 2.23 % · percentile 83.06 % · scored 15 Nov 2026.
Saved 15 Nov 2026 14:45:34 UTC · View this risk record (JSON)
Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.
A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).
CVE-2024-21643 · 15 Nov 2026 14:45:34 UTC
CVE-2024-21643 · 14 Nov 2026 16:37:01 UTC
CVE-2024-21643 · 13 Nov 2026 19:59:34 UTC
CVE-2024-21643 · 12 Nov 2026 18:18:51 UTC
CVE-2024-21643 · 10 Nov 2026 20:24:10 UTC
CVE-2024-21643 · 09 Nov 2026 21:04:24 UTC
CVE-2024-21643 · 08 Nov 2026 15:12:21 UTC
CVE-2024-21643 · 07 Nov 2026 16:07:52 UTC
CVE-2024-21643 · 06 Nov 2026 19:10:17 UTC
CVE-2024-21643 · 05 Nov 2026 22:49:22 UTC
CVE-2024-21643 · 05 Nov 2026 02:54:06 UTC
CVE-2024-21643 · 03 Nov 2026 16:59:18 UTC
CVE-2024-21643 · 02 Nov 2026 23:59:04 UTC
CVE-2024-21643 · 01 Nov 2026 23:58:58 UTC
CVE-2024-21643 · 01 Nov 2026 03:04:52 UTC
CVE-2024-21643 · 31 Oct 2026 01:52:30 UTC
CVE-2024-21643 · 29 Oct 2026 18:29:26 UTC
CVE-2024-21643 · 28 Oct 2026 19:55:37 UTC
CVE-2024-21643 · 27 Oct 2026 15:46:19 UTC
CVE-2024-21643 · 27 Oct 2026 00:23:05 UTC
CVE-2024-21643 · 25 Oct 2026 15:18:41 UTC
See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.
Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.
euvd · EUVD-2024-0423 · Published
euvd · EUVD-2024-0423 · Published
euvd · EUVD-2024-0423 · Published
euvd · EUVD-2024-0423 · Published
euvd · EUVD-2024-0423 · Published
euvd · EUVD-2024-0423 · Published
euvd · EUVD-2024-0423 · Published
euvd · EUVD-2024-0423 · Published
euvd · EUVD-2024-0423 · Published
euvd · EUVD-2024-0423 · Published
nvd · CVE-2024-21643 · Published
osv · GHSA-rv9j-c866-gp5h · Published
cve-program · CVE-2024-21643 · Published