VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

rendertron: vulnerability history, versions and safety

rendertron is a package in the npm ecosystem. Vulert records 5 vulnerabilities for it across 5 releases, from Jan 2019 to Mar 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded H3 M2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all rendertron vulnerabilities

Vulert verdict on rendertron 3.1.0 i

Updated on 22 Oct 2026

Good news: 3.1.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 5.

Package health score 60/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Moderate

What to do: Stay on 3.1.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.1.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 3.1.0 — unaffected i
  • Vulnerabilities on record 5 over 2 years · 0 in the last year i
  • Latest disclosure 01 Mar 2021 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 5,949 i
  • OpenSSF scorecard 3/10 i
  • Last release 71 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for rendertron, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
3.1.0 04 Nov 2020 none Apache-2.0 — Details →
3.0.0 02 Jul 2020 none Apache-2.0 — Details →
2.0.1 18 Sep 2018 M1 Apache-2.0 Yes Details →
2.0.0 26 Jul 2018 M1 Apache-2.0 Yes Details →
1.1.1 06 Jan 2018 M1 Apache-2.0 Yes Details →
1.1.0 27 Oct 2017 M1 Apache-2.0 Yes Details →
1.0.1 27 Oct 2017 H3 M2 Apache-2.0 Yes Details →

All 7 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 4
  • 2021 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 5 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for rendertron

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-18353: Vulnerability in rendertron 7.5 high 1.1.0 04 Jan 2019
CVE-2017-18354: Local File Inclusion Vulnerability in Rendertron 7.5 high 1.1.0 04 Jan 2019
CVE-2017-18355: rendertron - Exposed Absolute Paths in node_modules 7.5 high 1.1.0 12 Feb 2019
CVE-2017-18352: Rendertron - Reflected Cross Site Scripting (XSS) 6.1 medium 1.1.0 07 Jan 2019
CVE-2020-8902: SSRF in Rendertron N/A medium 3.0.0 01 Mar 2021

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About rendertron

Is rendertron safe to use?

Vulert records 5 vulnerabilities for rendertron in npm: 0 critical, 3 high, 2 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is rendertron's Vulert package health score?

Vulert scores rendertron 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of rendertron affected?

No. 3.1.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of rendertron should I use?

3.1.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does rendertron have?

5 vulnerabilities are recorded for rendertron in the npm ecosystem: 0 critical, 3 high, 2 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new rendertron vulnerabilities disclosed?

0 vulnerabilities were recorded for rendertron in the last 12 months, and the oldest entry in this database dates to 04 Jan 2019. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of rendertron are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor rendertron for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the rendertron version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.