VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

react-pdf: vulnerability history, versions and safety

react-pdf is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 102 releases, first recorded in May 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
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 react-pdf vulnerabilities

Vulert verdict on react-pdf 11.0.0 i

Updated on 23 Oct 2026

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

Package health score 82/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 11.0.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 07 May 2024 i
  • Highest CVSS 7.1 i
  • With no published fix 0 i
  • Depended on by 22 packages i
  • Stars 11,190 i
  • OpenSSF scorecard 4/10 i
  • Last release 1 month ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 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 react-pdf, 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
11.0.0 10 Sep 2026 none MIT — Details →
10.5.0 20 Aug 2026 none MIT — Details →
10.4.1 25 Feb 2026 none MIT — Details →
10.4.0 21 Feb 2026 none MIT — Details →
10.3.0 30 Dec 2025 none MIT — Details →
10.2.0 09 Oct 2025 none MIT — Details →
10.1.0 15 Aug 2025 none MIT — Details →
10.0.1 26 Jun 2025 none MIT — Details →
10.0.0 26 Jun 2025 none MIT — Details →
9.2.1 19 Dec 2024 none MIT — Details →
9.2.0 19 Dec 2024 none MIT — Details →
9.1.1 18 Sep 2024 none MIT — Details →
9.1.0 02 Jul 2024 none MIT — Details →
9.0.0 29 May 2024 none MIT — Details →
8.0.2 07 May 2024 none MIT — Details →
7.7.3 07 May 2024 none MIT — Details →
8.0.1 07 May 2024 none MIT — Details →
7.7.2 07 May 2024 H1 MIT Yes Details →
8.0.0 30 Apr 2024 none MIT — Details →
7.7.1 21 Feb 2024 H1 MIT Yes Details →
7.7.0 10 Jan 2024 H1 MIT Yes Details →
7.6.0 09 Dec 2023 H1 MIT Yes Details →
7.5.1 18 Oct 2023 H1 MIT Yes Details →
7.5.0 05 Oct 2023 H1 MIT Yes Details →
7.4.0 25 Sep 2023 H1 MIT Yes Details →
7.3.3 01 Aug 2023 H1 MIT Yes Details →
7.3.2 01 Aug 2023 H1 MIT Yes Details →
7.3.1 01 Aug 2023 H1 MIT Yes Details →
7.3.0 27 Jul 2023 H1 MIT Yes Details →
7.2.0 21 Jul 2023 H1 MIT Yes Details →
7.1.3 16 Jul 2023 H1 MIT Yes Details →
7.1.2 12 Jun 2023 H1 MIT Yes Details →
7.1.1 07 Jun 2023 H1 MIT Yes Details →
7.1.0 06 Jun 2023 H1 MIT Yes Details →
7.0.3 01 Jun 2023 H1 MIT Yes Details →
7.0.2 31 May 2023 H1 MIT Yes Details →
7.0.1 24 May 2023 H1 MIT Yes Details →
7.0.0 24 May 2023 H1 MIT Yes Details →
7.0.0-beta.4 08 May 2023 H1 MIT Yes Details →
7.0.0-beta.3 08 May 2023 H1 MIT Yes Details →
7.0.0-beta.2 08 May 2023 H1 MIT Yes Details →
7.0.0-beta 08 May 2023 H1 MIT Yes Details →
6.2.2 11 Jan 2023 H1 MIT Yes Details →
6.2.1 28 Dec 2022 H1 MIT Yes Details →
6.2.0 22 Nov 2022 H1 MIT Yes Details →
6.1.1 20 Nov 2022 H1 MIT Yes Details →
6.1.0 15 Nov 2022 H1 MIT Yes Details →
6.0.3 10 Nov 2022 H1 MIT Yes Details →
6.0.2 09 Nov 2022 H1 MIT Yes Details →
6.0.1 08 Nov 2022 H1 MIT Yes Details →
6.0.0 08 Nov 2022 H1 MIT Yes Details →
6.0.0-beta.6 08 Nov 2022 H1 MIT Yes Details →
6.0.0-beta.5 05 Nov 2022 H1 MIT Yes Details →
6.0.0-beta.4 07 Oct 2022 H1 MIT Yes Details →
6.0.0-beta.3 27 Jul 2022 H1 MIT Yes Details →
6.0.0-beta.2 05 Jul 2022 H1 MIT Yes Details →
6.0.0-beta 05 Jul 2022 H1 MIT Yes Details →
5.7.2 30 Mar 2022 H1 MIT Yes Details →
5.7.1 09 Feb 2022 H1 MIT Yes Details →
5.7.0 27 Jan 2022 H1 MIT Yes Details →
5.6.0 13 Dec 2021 H1 MIT Yes Details →
5.5.0 25 Oct 2021 H1 MIT Yes Details →
5.4.1 19 Oct 2021 H1 MIT Yes Details →
5.4.0 27 Sep 2021 H1 MIT Yes Details →
5.4.0-beta.3 01 Sep 2021 H1 MIT Yes Details →
5.4.0-beta.2 27 Jul 2021 H1 MIT Yes Details →
5.3.2 08 Jul 2021 H1 MIT Yes Details →
5.4.0-beta 08 Jul 2021 H1 MIT Yes Details →
5.3.1 07 Jul 2021 H1 MIT Yes Details →
5.3.0 08 May 2021 H1 MIT Yes Details →
5.3.0-beta.3 01 Apr 2021 H1 MIT Yes Details →
5.3.0-beta.2 01 Apr 2021 H1 MIT Yes Details →
5.3.0-beta 18 Mar 2021 H1 MIT Yes Details →
5.2.0 15 Feb 2021 H1 MIT Yes Details →
5.1.0 11 Dec 2020 H1 MIT Yes Details →
5.1.0-beta 23 Nov 2020 H1 MIT Yes Details →
5.0.0 27 Aug 2020 H1 MIT Yes Details →
5.0.0-beta.5 04 Aug 2020 H1 MIT Yes Details →
4.2.0 27 Jul 2020 H1 MIT Yes Details →
5.0.0-beta.4 09 Jun 2020 H1 MIT Yes Details →
5.0.0-beta.3 27 Apr 2020 H1 MIT Yes Details →
5.0.0-beta.2 21 Dec 2019 H1 MIT Yes Details →
5.0.0-beta 16 Nov 2019 H1 MIT Yes Details →
4.2.0-beta 27 Jul 2019 H1 MIT Yes Details →
4.1.0 12 Jun 2019 H1 MIT Yes Details →
4.0.5 03 Mar 2019 H1 MIT Yes Details →
4.0.4 01 Mar 2019 H1 MIT Yes Details →
4.0.3 17 Feb 2019 H1 MIT Yes Details →
4.0.2 05 Jan 2019 H1 MIT Yes Details →
4.0.0 23 Nov 2018 H1 MIT Yes Details →
3.0.6 21 Nov 2018 H1 MIT Yes Details →
4.0.0-beta.6 17 Nov 2018 H1 MIT Yes Details →
4.0.0-beta.5 26 Sep 2018 H1 MIT Yes Details →
4.0.0-beta.4 03 Sep 2018 H1 MIT Yes Details →
4.0.0-beta.3 15 Aug 2018 H1 MIT Yes Details →
4.0.0-beta.2 30 Jun 2018 H1 MIT Yes Details →
4.0.0-beta 04 May 2018 H1 MIT Yes Details →
3.0.5 04 May 2018 H1 MIT Yes Details →
3.0.4 31 Mar 2018 H1 MIT Yes Details →
3.0.3 31 Mar 2018 H1 MIT Yes Details →
3.0.2 22 Mar 2018 H1 — Yes Details →
3.0.1 18 Mar 2018 H1 — Yes Details →
3.0.0 18 Mar 2018 H1 — Yes Details →
3.0.0-beta 15 Mar 2018 H1 — Yes Details →
3.0.0-alpha.4 05 Feb 2018 H1 — Yes Details →
2.5.3 05 Feb 2018 H1 — Yes Details →
3.0.0-alpha.3 25 Jan 2018 H1 — Yes Details →
3.0.0-alpha.2 23 Jan 2018 H1 — Yes Details →
3.0.0-alpha 21 Jan 2018 H1 — Yes Details →
2.5.2 01 Jan 2018 H1 — Yes Details →
2.5.1 30 Dec 2017 H1 — Yes Details →
2.5.0 27 Dec 2017 H1 — Yes Details →
2.4.2 02 Dec 2017 H1 — Yes Details →
2.4.1 21 Nov 2017 H1 — Yes Details →
2.4.0 20 Nov 2017 H1 — Yes Details →
2.3.0 17 Nov 2017 H1 — Yes Details →
2.2.0 11 Nov 2017 H1 — Yes Details →
2.1.7 18 Oct 2017 H1 — Yes Details →
2.2.0-beta.3 15 Oct 2017 H1 — Yes Details →
2.2.0-beta.2 15 Oct 2017 H1 — Yes Details →

The newest 120 of 157 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for react-pdf

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-34342: react-pdf Arbitrary JavaScript Execution Vulnerability 7.1 high 7.7.3 07 May 2024

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 react-pdf

Is react-pdf safe to use?

Vulert records 1 vulnerabilities for react-pdf in npm: 0 critical, 1 high, 0 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 react-pdf's Vulert package health score?

Vulert scores react-pdf 82/100, which reads as in good shape. 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 react-pdf affected?

No. 11.0.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 react-pdf should I use?

11.0.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 react-pdf have?

1 vulnerability is recorded for react-pdf in the npm ecosystem: 0 critical, 1 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 react-pdf vulnerabilities disclosed?

0 vulnerabilities were recorded for react-pdf in the last 12 months, and the oldest entry in this database dates to 07 May 2024. 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 react-pdf 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 react-pdf for upcoming vulnerabilities?

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