VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

rapidjson: vulnerability history, versions and safety

rapidjson is a package in the OSS-Fuzz ecosystem. Vulert records 3 vulnerabilities for it across 1 affected range, from Sep 2021 to Jan 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H1 M2
i
3 with no fix published

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

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

Most recent disclosure 25 Jan 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all rapidjson vulnerabilities

Vulert verdict on rapidjson i

Updated on 23 Oct 2026

Careful: 3 of the 3 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each.

Long-term outlook: usable, but needs attention 3 vulnerabilities on record across 4 years, 2 in the last year.

What to do: Plan around the 3 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 3 over 4 years · 2 in the last year i
  • Latest disclosure 25 Jan 2026 i
  • Highest CVSS n/a i
  • With no published fix 3 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

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
all releases, no fix published yet 3

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for rapidjson

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical UNKNOWN WRITE Vulnerability in RapidJSON Package N/A high No fix published 28 Sep 2021
Critical UNKNOWN READ Vulnerability in RapidJSON Package N/A medium No fix published 25 Jan 2026
Critical Crash Vulnerability in rapidjson Package - UNKNOWN Issue N/A medium No fix published 22 Jan 2026

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 rapidjson

Is rapidjson safe to use?

Vulert records 3 vulnerabilities for rapidjson in OSS-Fuzz: 0 critical, 1 high, 2 medium and 0 low. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does rapidjson have?

3 vulnerabilities are recorded for rapidjson in the OSS-Fuzz ecosystem: 0 critical, 1 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 rapidjson vulnerabilities disclosed?

2 vulnerabilities were recorded for rapidjson in the last 12 months, and the oldest entry in this database dates to 28 Sep 2021. 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 rapidjson 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 rapidjson for upcoming vulnerabilities?

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