How severe is GHSA-xr9h-9m79-x29g?

No CVSS score has been assigned to GHSA-xr9h-9m79-x29g yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xr9h-9m79-x29g?

GHSA-xr9h-9m79-x29g affects the following packages: rendertron (npm). Ecosystems affected: npm.

How do I fix GHSA-xr9h-9m79-x29g?

Update rendertron to 3.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xr9h-9m79-x29g is resolved across your whole dependency graph.

How do I detect GHSA-xr9h-9m79-x29g in my npm dependencies?

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

How do I mitigate GHSA-xr9h-9m79-x29g if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is GHSA-xr9h-9m79-x29g actively exploited in the wild?

No public exploit code has been indexed for GHSA-xr9h-9m79-x29g 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-xr9h-9m79-x29g?

GHSA-xr9h-9m79-x29g has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 24th 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-xr9h-9m79-x29g?

GHSA-xr9h-9m79-x29g is classified as CWE-284 (CWE-284), Server-Side Request Forgery (SSRF) (CWE-918). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-xr9h-9m79-x29g published, and has it been updated?

GHSA-xr9h-9m79-x29g was published on March 1, 2021 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

SSRF in Rendertron

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs24th percentile — riskier than 24% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

rendertronnpm

220downloads / week

Description

Rendertron versions prior to 3.0.0 are are susceptible to a Server-Side Request Forgery (SSRF) attack. An attacker can use a specially crafted webpage to force a rendertron headless chrome process to render internal sites it has access to, and display it as a screenshot. Suggested mitigations are to upgrade your rendertron to version 3.0.0, or, if you cannot update, to secure the infrastructure to limit the headless chrome's access to your internal domain.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`rendertron`	all versions	3.0.0`npm install rendertron@3.0.0`

Affected Products

1 product · 1 configurations

Application

rendertrongoogle

< 3.0.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rendertron, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update rendertron to 3.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xr9h-9m79-x29g is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

Rendertron versions prior to 3.0.0 are are susceptible to a Server-Side Request Forgery (SSRF) attack. An attacker can use a specially crafted webpage to force a rendertron headless chrome process to render internal sites it has access to, and display it as a screenshot. Suggested mitigations are to upgrade your rendertron to version 3.0.0, or, if you cannot update, to secure the infrastructure to limit the headless chrome's access to your internal domain.

O3 Security · Impact-Aware SCA

Is GHSA-xr9h-9m79-x29g in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

SSRF in RendertronGHSA-xr9h-9m79-x29g