Improper Validation of Unsafe Equivalence in Input The advisory has been revoked - it doesn't affect any version of package dotnet-sdk-8.0-source-built-artifacts (opens in a new tab)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-RHEL8-DOTNETSDK80SOURCEBUILTARTIFACTS-21494551
- published23 Oct 2026
- disclosed31 Jul 2026
Introduced: 31 Jul 2026
CVE-2026-18446 (opens in a new tab)Amendment
The Red Hat security team deemed this advisory irrelevant for RHEL:8.
NVD Description
Note: Versions mentioned in the description apply only to the upstream dotnet-sdk-8.0-source-built-artifacts package and not the dotnet-sdk-8.0-source-built-artifacts package as distributed by RHEL.
fast-uri before 4.1.2, 3.1.5, and 2.4.4 requires a literal double forward slash to recognize a URI authority, so a reference that uses a backslash based introducer in place of it (backslash backslash, forward slash backslash, or backslash forward slash) is parsed with no authority and folds into the path. Node's native WHATWG URL parser instead treats a backslash as interchangeable with a forward slash for special schemes, so the two parsers extract different hosts from the same input. Applications that use fast-uri to enforce host based policy such as allowlists, SSRF filtering, or redirect validation before passing the same URL into Node's URL or fetch consumers can be steered to an unintended host. Upgrade to fast-uri 4.1.2, 3.1.5, or 2.4.4.