How severe is GHSA-rv9j-c866-gp5h?

GHSA-rv9j-c866-gp5h has a CVSS score of 7.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-rv9j-c866-gp5h?

GHSA-rv9j-c866-gp5h affects the following packages: Microsoft.IdentityModel.Protocols.SignedHttpRequest (NuGet), Microsoft.IdentityModel.Protocols.SignedHttpRequest (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-rv9j-c866-gp5h?

Update Microsoft.IdentityModel.Protocols.SignedHttpRequest to 6.34.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rv9j-c866-gp5h is resolved across your whole dependency graph.

How do I detect GHSA-rv9j-c866-gp5h in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.IdentityModel.Protocols.SignedHttpRequest, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-rv9j-c866-gp5h if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is GHSA-rv9j-c866-gp5h actively exploited in the wild?

No public exploit code has been indexed for GHSA-rv9j-c866-gp5h yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-rv9j-c866-gp5h?

GHSA-rv9j-c866-gp5h has an EPSS (Exploit Prediction Scoring System) score of 2.2%, placing it in the 83th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-rv9j-c866-gp5h?

GHSA-rv9j-c866-gp5h is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-rv9j-c866-gp5h published, and has it been updated?

GHSA-rv9j-c866-gp5h was published on January 9, 2024 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET

.NET NuGet

Not in CISA KEV

HIGH severity

Microsoft.IdentityModel.Protocols.SignedHttpRequest remote code execution vulnerabilityGHSA-rv9j-c866-gp5h

HIGH

GHSA-rv9j-c866-gp5h is a high-severity (CVSS 7.1) Code Injection vulnerability in Microsoft.IdentityModel.Protocols.SignedHttpRequest. A fix is available for Microsoft.IdentityModel.Protocols.SignedHttpRequest — see the affected versions and patch details below.

Also known asCVE-2024-21643

Published

Jan 9, 2024

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-rv9j-c866-gp5h.

EPSS Exploitation Probability

via FIRST.org ↗

2.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

.NETMicrosoft.IdentityModel.Protocols.SignedHttpRequest.NETMicrosoft.IdentityModel.Protocols.SignedHttpRequest

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

Impact

What kind of vulnerability is it? Who is impacted? Anyone leveraging the SignedHttpRequestprotocol or the SignedHttpRequestValidatoris vulnerable. Microsoft.IdentityModel trusts the jkuclaim by default for the SignedHttpRequestprotocol. 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

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`Microsoft.IdentityModel.Protocols.SignedHttpRequest`	all versions	6.34.0`dotnet add package Microsoft.IdentityModel.Protocols.SignedHttpRequest --version 6.34.0`
.NETNuGet	`Microsoft.IdentityModel.Protocols.SignedHttpRequest`	≥ 7.0.0-preview&&< 7.1.2	7.1.2`dotnet add package Microsoft.IdentityModel.Protocols.SignedHttpRequest --version 7.1.2`

Affected Products

1 product · 2 configurations

Application

identitymodel extensionsmicrosoft

≥ 7.0.0 && < 7.1.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.IdentityModel.Protocols.SignedHttpRequest, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Microsoft.IdentityModel.Protocols.SignedHttpRequest to 6.34.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rv9j-c866-gp5h is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

### 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

O3 Security · Impact-Aware SCA

Is GHSA-rv9j-c866-gp5h in your dependencies?

Find it across NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

Low

Raw vector

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

CWE Classification

CWE-94Code Injection

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

azure-activedirectory-identitymodel-extensions-for-dotnet

7.0/10

Maintained10/10

Code-Review10/10

Branch-Protection2/10

Assessed Oct 19, 2026

Timeline

Disclosed

Jan 9, 2024

Last updated

Sep 10, 2026

Identifiers

GHSA-rv9j-c866-gp5h

References

Advisorynvd.nist.gov · CVE 2024 21643 Webgithub.com · GHSA rv9j c866 gp5h Webgithub.com · 6.34.0 Webgithub.com · 7.1.2 Webgithub.com · jkucve Packagegithub.com · azure activedirectory identitymodel extensions for dotnet

Related vulnerabilities

This CVE is high severity; 8 of 8 other CVEs with CWE-94 are rated as high or higher (top: critical).

CVE-2026-63469CVE-2026-63470CVE-2026-63471CVE-2026-62284CVE-2026-61536CVE-2026-44267CVE-2026-44266CVE-2026-115878Browse all CWE-94

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedSep 10, 2026

Microsoft.IdentityModel.Protocols.SignedHttpRequest remote code execution vulnerabilityGHSA-rv9j-c866-gp5h

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Impact

Patches

Workarounds

References

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-rv9j-c866-gp5h in your dependencies?