Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
.NET
.NET NuGet
Not in CISA KEV
HIGH severity

.NET Core Information DisclosureGHSA-7jgj-8wvc-jh57

HIGH

GHSA-7jgj-8wvc-jh57 is a high-severity (CVSS 7.5) Information Exposure vulnerability in System.Net.Http. EPSS puts its 30-day exploitation probability at 14.8% (97th percentile). A fix is available for System.Net.Http — see the affected versions and patch details below.

Also known asCVE-2018-8292
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
14.8%probability of exploitation in next 30 days
Moderate Risk+6.69%
Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk
4.36%8.66%13.0%17.3%6.8%8.1%8.1%14.8%Apr 26Jun 26Oct 26

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

How urgent is this, really

GHSA-7jgj-8wvc-jh57 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected
.NETSystem.Net.Http

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

An information disclosure vulnerability exists in .NET Core when authentication information is inadvertently exposed in a redirect, aka ".NET Core Information Disclosure Vulnerability." This affects .NET Core 2.1, .NET Core 1.0, .NET Core 1.1, PowerShell Core 6.0.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetSystem.Net.Httpall versions4.3.4dotnet add package System.Net.Http --version 4.3.4

Affected Products

2 products · 4 configurations
Application
asp.net coremicrosoft
3 versions
1.01.12.1
Application
powershell coremicrosoft
1 version
6.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update System.Net.Http to 4.3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7jgj-8wvc-jh57 is resolved across your whole dependency graph.

  3. Workarounds

    Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
ProductFixed inAdvisory
.NET Core on Red Hat Enterprise Linuxrh-dotnetcore10-dotnetcore-0:1.0.13-1.el7RHSA-2018:2902

Frequently Asked Questions

An information disclosure vulnerability exists in .NET Core when authentication information is inadvertently exposed in a redirect, aka ".NET Core Information Disclosure Vulnerability." This affects .NET Core 2.1, .NET Core 1.0, .NET Core 1.1, PowerShell Core 6.0.
O3 Security · Impact-Aware SCA

Is GHSA-7jgj-8wvc-jh57 in your dependencies?

Find it across NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works
.NET Core Information Disclosure (High 7.5)