How severe is GHSA-w32m-9786-jp63?

No CVSS score has been assigned to GHSA-w32m-9786-jp63 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w32m-9786-jp63?

GHSA-w32m-9786-jp63 affects the following packages: golang.org/x/net/html (Go). Ecosystems affected: Go.

How do I fix GHSA-w32m-9786-jp63?

Update golang.org/x/net/html to 0.33.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w32m-9786-jp63 is resolved across your whole dependency graph.

How do I detect GHSA-w32m-9786-jp63 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for golang.org/x/net/html, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-w32m-9786-jp63 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-w32m-9786-jp63?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-w32m-9786-jp63 can be triaged on real exposure rather than presence alone.

Is GHSA-w32m-9786-jp63 actively exploited in the wild?

No public exploit code has been indexed for GHSA-w32m-9786-jp63 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-w32m-9786-jp63?

GHSA-w32m-9786-jp63 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 57th 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-w32m-9786-jp63?

GHSA-w32m-9786-jp63 is classified as CWE-1333 (CWE-1333). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-w32m-9786-jp63 published, and has it been updated?

GHSA-w32m-9786-jp63 was published on December 18, 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.

🐹 Go

Not in CISA KEV

GHSA-w32m-9786-jp63 — html

GHSA-w32m-9786-jp63 is a CWE-1333 vulnerability in golang.org/x/net/html. A fix is available for golang.org/x/net/html — see the affected versions and patch details below.

Non-linear parsing of case-insensitive content in golang.org/x/net/html

Also known asCVE-2024-45338GO-2024-3333

Published

Dec 18, 2024

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
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-w32m-9786-jp63.

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs57th percentile — riskier than 57% of all scored CVEsHighest risk

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.

Real-World Exposure

1 pkg affected

🐹golang.org/x/net/html

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

Description

An attacker can craft an input to the Parse functions that would be processed non-linearly with respect to its length, resulting in extremely slow parsing. This could cause a denial of service.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`golang.org/x/net/html`	all versions	0.33.0`go get golang.org/x/net/html@v0.33.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for golang.org/x/net/html, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update golang.org/x/net/html to 0.33.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w32m-9786-jp63 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-w32m-9786-jp63 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-w32m-9786-jp63. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 HatImportant

This vulnerability is rated as an Important severity because an attacker can craft malicious input that causes the parsing functions to process data non-linearly, resulting in significant delays which leads to a denial of service by exhausting system resources.

Product	Fixed in	Advisory
Cryostat 3 on RHEL 8	`cryostat-tech-preview/cryostat-db-rhel8:3.0.1-16`	RHSA-2025:0224
gatekeeper 3.14 for RHEL 9	`gatekeeper/gatekeeper-operator-bundle:v3.14.3-3`	RHSA-2025:1333
gatekeeper 3.15 for RHEL 9	`gatekeeper/gatekeeper-operator-bundle:v3.15.3-2`	RHSA-2025:1332
gatekeeper 3.17 for RHEL 9	`gatekeeper/gatekeeper-operator-bundle:v3.17.1-6`	RHSA-2025:1331
LVMS-4.14-RHEL-9	`lvms4/lvms-must-gather-rhel9:v4.14.12-7`	RHBA-2025:1169
LVMS-4.15-RHEL-9	`lvms4/lvms-must-gather-rhel9:v4.15.10-3`	RHBA-2025:0680
LVMS-4.16-RHEL-9	`lvms4/lvms-must-gather-rhel9:v4.16.7-2`	RHBA-2025:0681
LVMS-4.17-RHEL-9	`lvms4/lvms-must-gather-rhel9:v4.17.4-2`	RHBA-2025:0697

Frequently Asked Questions

An attacker can craft an input to the Parse functions that would be processed non-linearly with respect to its length, resulting in extremely slow parsing. This could cause a denial of service.

O3 Security · Impact-Aware SCA

Is GHSA-w32m-9786-jp63 in your dependencies?

O3 Security finds GHSA-w32m-9786-jp63 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works