Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
.NET NuGet

GHSA-8j9v-h2vp-2hhv

MEDIUM

GHSA-8j9v-h2vp-2hhv is a medium-severity (CVSS 6.1) CWE-74 vulnerability in HtmlSanitizer. O3 Security confirms whether GHSA-8j9v-h2vp-2hhv is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

XSS in HtmlSanitizer

Also known asCVE-2020-26293
Published
Jan 4, 2021
Updated
Mar 13, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Blast Radius

1 pkg affected
.NETHtmlSanitizer

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

If you have explicitly allowed the <style> tag, an attacker could craft HTML that includes script after passing through the sanitizer. The default settings disallow the <style> tag so there is no risk if you have not explicitly allowed the <style> tag.

Patches

The problem has been fixed in version 5.0.372.

Workarounds

Remove the <style> tag from the set of allowed tags.

For more information

If you have any questions or comments about this advisory open an issue in https://github.com/mganss/HtmlSanitizer

Credits

This issue was discovered by Michal Bentkowski of Securitum.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetHtmlSanitizerall versions5.0.372

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for HtmlSanitizer. 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.

  2. Fix

    Update HtmlSanitizer to 5.0.372 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8j9v-h2vp-2hhv is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-8j9v-h2vp-2hhv 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-8j9v-h2vp-2hhv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact If you have explicitly allowed the `<style>` tag, an attacker could craft HTML that includes script after passing through the sanitizer. The default settings disallow the `<style>` tag so there is no risk if you have not explicitly allowed the `<style>` tag. ### Patches The problem has been fixed in version 5.0.372. ### Workarounds Remove the `<style>` tag from the set of allowed tags. ### For more information If you have any questions or comments about this advisory open an issue in https://github.com/mganss/HtmlSanitizer ### Credits This issue was discovered by Michal Ben
O3 Security · Impact-Aware SCA

Is GHSA-8j9v-h2vp-2hhv in your dependencies?

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