How severe is GHSA-c97m-vxhj-p7j6?

GHSA-c97m-vxhj-p7j6 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-c97m-vxhj-p7j6?

GHSA-c97m-vxhj-p7j6 affects the following packages: github.com/yuin/goldmark/renderer/html (Go). Ecosystems affected: Go.

How do I fix GHSA-c97m-vxhj-p7j6?

Update github.com/yuin/goldmark/renderer/html to 1.7.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c97m-vxhj-p7j6 is resolved across your whole dependency graph.

How do I detect GHSA-c97m-vxhj-p7j6 in my Go dependencies?

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

How do I mitigate GHSA-c97m-vxhj-p7j6 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-c97m-vxhj-p7j6?

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

Is GHSA-c97m-vxhj-p7j6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-c97m-vxhj-p7j6 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-c97m-vxhj-p7j6?

GHSA-c97m-vxhj-p7j6 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 25th 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-c97m-vxhj-p7j6 published, and has it been updated?

GHSA-c97m-vxhj-p7j6 was published on April 17, 2026 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

MEDIUM severity

GHSA-c97m-vxhj-p7j6 — html

MEDIUMFix: yuin/goldmark@cb46bbc

GHSA-c97m-vxhj-p7j6 is a medium-severity (CVSS 6.1) vulnerability in github.com/yuin/goldmark/renderer/html. A fix is available for github.com/yuin/goldmark/renderer/html — see the affected versions and patch details below.

goldmark vulnerable to Cross-site Scripting (XSS)

Also known asCVE-2026-5160GO-2026-5320

Published

Apr 17, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs25th percentile — riskier than 25% 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.

How urgent is this, really

GHSA-c97m-vxhj-p7j6 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

1 pkg affected

🐹github.com/yuin/goldmark/renderer/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

Versions of the package github.com/yuin/goldmark/renderer/html before 1.7.17 are vulnerable to Cross-site Scripting (XSS) due to improper ordering of URL validation and normalization. The renderer validates link destinations using a prefix-based check (IsDangerousURL) before resolving HTML entities. This allows an attacker to bypass protocol filtering by encoding dangerous schemes using HTML5 named character references. For example, a payload such as javascript:alert(1) is not recognized as dangerous during validation, leading to arbitrary script execution in the context of applications that render the URL.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/yuin/goldmark/renderer/html`	all versions	1.7.17`go get github.com/yuin/goldmark/renderer/html@v1.7.17`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/yuin/goldmark/renderer/html, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/yuin/goldmark/renderer/html to 1.7.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c97m-vxhj-p7j6 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-c97m-vxhj-p7j6 can be triaged on real exposure rather than presence alone.

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

Frequently Asked Questions

Versions of the package github.com/yuin/goldmark/renderer/html before 1.7.17 are vulnerable to Cross-site Scripting (XSS) due to improper ordering of URL validation and normalization. The renderer validates link destinations using a prefix-based check (IsDangerousURL) before resolving HTML entities. This allows an attacker to bypass protocol filtering by encoding dangerous schemes using HTML5 named character references. For example, a payload such as javascript&colon;alert(1) is not recognized as dangerous during validation, leading to arbitrary script execution in the context of applications

O3 Security · Impact-Aware SCA

Is GHSA-c97m-vxhj-p7j6 in your dependencies?

O3 Security finds GHSA-c97m-vxhj-p7j6 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