How severe is GHSA-8xc6-g8xw-h2c4?

GHSA-8xc6-g8xw-h2c4 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-8xc6-g8xw-h2c4?

GHSA-8xc6-g8xw-h2c4 affects the following packages: Yarp.ReverseProxy (NuGet), Yarp.ReverseProxy (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-8xc6-g8xw-h2c4?

Update Yarp.ReverseProxy to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8xc6-g8xw-h2c4 is resolved across your whole dependency graph.

How do I detect GHSA-8xc6-g8xw-h2c4 in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Yarp.ReverseProxy. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-8xc6-g8xw-h2c4 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-8xc6-g8xw-h2c4?

O3 pinpoints whether GHSA-8xc6-g8xw-h2c4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-8xc6-g8xw-h2c4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-8xc6-g8xw-h2c4 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-8xc6-g8xw-h2c4?

GHSA-8xc6-g8xw-h2c4 has an EPSS (Exploit Prediction Scoring System) score of 3.1%, placing it in the 86th 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.

When was GHSA-8xc6-g8xw-h2c4 published, and has it been updated?

GHSA-8xc6-g8xw-h2c4 was published on April 22, 2022 and was last updated on December 5, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET NuGet

GHSA-8xc6-g8xw-h2c4

HIGH

YARP Denial of Service Vulnerability

Also known asCVE-2022-26924

Published

Apr 22, 2022

Updated

Dec 5, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

3.1%probability of exploitation in next 30 days

Lower Risk86th percentile-4.83%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

.NETYarp.ReverseProxy.NETYarp.ReverseProxy

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

A denial of service vulnerability exists in how YARP processes input.

Patches

If you're using YARP 1.0.0, you should update to NuGet package version 1.0.1. If you're using YARP 1.1.0-RC.1, you should update to NuGet package version 1.1.0-rc.1.22211.2.

You can do so by updating the PackageReference in your .csproj file

<ItemGroup>
- <PackageReference Include="Yarp.ReverseProxy" Version="1.0.0" />
- <PackageReference Include="Yarp.Telemetry.Consumption" Version="1.0.0" />
+ <PackageReference Include="Yarp.ReverseProxy" Version="1.0.1" />
+ <PackageReference Include="Yarp.Telemetry.Consumption" Version="1.0.1" />
</ItemGroup>

or by selecting 1.0.1 in the NuGet UI inside Visual Studio (Manage NuGet Packages / Updates)

References

CVE-2022-26924

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`Yarp.ReverseProxy`	all versions	1.0.1
.NETNuGet	`Yarp.ReverseProxy`	≥ 1.1.0-rc.1.22152.1&&< 1.1.0-rc.1.22211.2	1.1.0-rc.1.22211.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Yarp.ReverseProxy. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update Yarp.ReverseProxy to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8xc6-g8xw-h2c4 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-8xc6-g8xw-h2c4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-8xc6-g8xw-h2c4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact A denial of service vulnerability exists in how YARP processes input. ### Patches If you're using YARP `1.0.0`, you should update to NuGet package version [`1.0.1`](https://www.nuget.org/packages/Yarp.ReverseProxy/1.0.1). If you're using YARP `1.1.0-RC.1`, you should update to NuGet package version [`1.1.0-rc.1.22211.2`](https://www.nuget.org/packages/Yarp.ReverseProxy/1.1.0-rc.1.22211.2). You can do so by updating the `PackageReference` in your `.csproj` file ```diff <ItemGroup> - <PackageReference Include="Yarp.ReverseProxy" Version="1.0.0" /> - <PackageReference Include="Yarp

O3 Security · Impact-Aware SCA

Is GHSA-8xc6-g8xw-h2c4 in your dependencies?

O3 detects GHSA-8xc6-g8xw-h2c4 across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works