VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

Rambox: vulnerability history, versions and safety

Rambox is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 1 release, from May 2022 to Sep 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded C2
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in npm →

See all Rambox vulnerabilities

Vulert verdict on Rambox i

Updated on 23 Oct 2026

Careful: 2 of the 2 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. One of them is a malicious-package vulnerability, where a published version of the package contained hostile code rather than only a bug — worth checking against the versions you have resolved.

Long-term outlook: risky 2 vulnerabilities on record across 1 year, none in the last year.

What to do: Check whether you ever resolved an affected version — the vulnerabilities below name the releases that shipped hostile code. Check what you run: Vulert alerts you when a safe version is published. Monitor it with Vulert →

  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 19 Sep 2023 i
  • Highest CVSS 9.0 i
  • With no published fix 2 i
  • Malicious packages 1 i

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 holds for Rambox, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
1.0.0 C1 No Details →

Newest 1 of 1 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2023 1

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

03 Vulnerabilities

Recorded vulnerabilities for Rambox

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-17625: Rambox RCE Vulnerability 9.0 critical No fix published 24 May 2022
Malicious Code in rambox (npm) N/A critical No fix published 19 Sep 2023

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

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 Rambox

Is Rambox safe to use?

Vulert records 2 vulnerabilities for Rambox in npm: 2 critical, 0 high, 0 medium and 0 low. 2 of them have no published fix yet, so those are the ones to avoid or mitigate. 1 are malicious-package vulnerabilities: the published package itself contained hostile code, not only a bug.

How many vulnerabilities does Rambox have?

2 vulnerabilities are recorded for Rambox in the npm ecosystem: 2 critical, 0 high, 0 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 Rambox vulnerabilities disclosed?

0 vulnerabilities were recorded for Rambox in the last 12 months, and the oldest entry in this database dates to 24 May 2022. 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 Rambox 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.

What does a malicious-package vulnerability mean?

It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.

How do I monitor Rambox for upcoming vulnerabilities?

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