Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

rendertron can remotely shut down Chrome instanceGHSA-4q69-q4q7-x82c

HIGHFix: GoogleChrome/rendertron#88

GHSA-4q69-q4q7-x82c is a high-severity (CVSS 7.5) vulnerability in rendertron. 1 public exploit reference exists, so weaponization risk is real. A fix is available for rendertron — see the affected versions and patch details below.

Also known asCVE-2017-18353
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs66th percentile — riskier than 66% of all scored CVEsHighest risk
0.00%0.55%1.10%1.65%0.4%1.2%Apr 26Aug 26Oct 26

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

How urgent is this, really

GHSA-4q69-q4q7-x82c by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

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 1.0.0 includes an _ah/stop route to shutdown the Chrome instance responsible for serving render requests to all users. Visiting this route with a GET request allows any unauthorized remote attacker to disable the core service of the application.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmrendertronall versions1.1.0npm install rendertron@1.1.0

Affected Products

1 product · 1 configurations
Application
rendertrongoogle
1 version
1.0.0
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Rendertron 1.0.0 includes an _ah/stop route to shutdown the Chrome insta…

bugs.chromium.orgNVDOct 2019

Detection & mitigation playbook

Open-source dependency

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

  2. Fix

    Update rendertron to 1.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4q69-q4q7-x82c 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.

Frequently Asked Questions

Rendertron 1.0.0 includes an `_ah/stop` route to shutdown the Chrome instance responsible for serving render requests to all users. Visiting this route with a GET request allows any unauthorized remote attacker to disable the core service of the application.
O3 Security · Impact-Aware SCA

Is GHSA-4q69-q4q7-x82c in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
rendertron can remotely shut down Chrome instance