Vulnerability Database · npm · Package report

react-native-reanimated: vulnerability history, versions and safety

react-native-reanimated is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 0 release, first recorded in Oct 2022. 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.

Vulert verdict on react-native-reanimated 4.7.1 i

Updated on 22 Oct 2026

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

Package health score 84/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 4.7.1 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 01 Oct 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 160 packages i
  • Stars 11,024 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT 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 react-native-reanimated, 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
4.8.0-nightly-20261021-63aa14096 21 Oct 2026 none MIT — Details →
4.8.0-nightly-20261020-af603ea3d 20 Oct 2026 none MIT — Details →
4.8.0-nightly-20261019-1d2b2132f 19 Oct 2026 none MIT — Details →
4.8.0-nightly-20261018-f21f7262e 18 Oct 2026 none MIT — Details →
4.8.0-nightly-20261017-f21f7262e 17 Oct 2026 none MIT — Details →
4.8.0-nightly-20261016-f21f7262e 16 Oct 2026 none MIT — Details →
4.8.0-nightly-20261015-505638fa0 15 Oct 2026 none MIT — Details →
4.8.0-nightly-20261014-07bd2f7d1 14 Oct 2026 none MIT — Details →
4.8.0-nightly-20261013-d25c744f7 13 Oct 2026 none MIT — Details →
4.8.0-nightly-20261012-f51abe448 12 Oct 2026 none MIT — Details →
4.8.0-nightly-20261011-390c8c6fe 11 Oct 2026 none MIT — Details →
4.8.0-nightly-20261010-390c8c6fe 10 Oct 2026 none MIT — Details →
4.8.0-nightly-20261009-390c8c6fe 09 Oct 2026 none MIT — Details →
4.8.0-nightly-20261008-591f01833 08 Oct 2026 none MIT — Details →
4.8.0-nightly-20261007-a93346850 08 Oct 2026 none MIT — Details →
4.8.0-nightly-20261006-9eaf504d2 06 Oct 2026 none MIT — Details →
4.8.0-nightly-20261005-8b2706fc8 05 Oct 2026 none MIT — Details →
4.8.0-nightly-20261004-7cb928218 04 Oct 2026 none MIT — Details →
4.8.0-nightly-20261002-7cb928218 02 Oct 2026 none MIT — Details →
4.7.1 02 Oct 2026 none MIT — Details →
4.8.0-nightly-20261001-6bcd8a412 01 Oct 2026 none MIT — Details →
4.8.0-nightly-20260930-bc8a1140d 30 Sep 2026 none MIT — Details →
4.8.0-nightly-20260929-b603aacf3 29 Sep 2026 none MIT — Details →
4.8.0-nightly-20260928-9f59e6c9e 28 Sep 2026 none MIT — Details →
4.8.0-nightly-20260927-9b3ae129d 27 Sep 2026 none MIT — Details →
4.8.0-nightly-20260926-9b3ae129d 26 Sep 2026 none MIT — Details →
4.8.0-nightly-20260925-9b3ae129d 25 Sep 2026 none MIT — Details →
4.8.0-nightly-20260924-6148a855e 24 Sep 2026 none MIT — Details →
4.8.0-nightly-20260923-20d6c94cb 23 Sep 2026 none MIT — Details →
4.8.0-nightly-20260922-79881d984 22 Sep 2026 none MIT — Details →
4.7.0 18 Sep 2026 none MIT — Details →
4.7.0-nightly-20260917-20294e0e2 17 Sep 2026 none MIT — Details →
4.7.0-nightly-20260916-1fb70959f 16 Sep 2026 none MIT — Details →
4.7.0-nightly-20260915-07aa7ab51 15 Sep 2026 none MIT — Details →
4.7.0-nightly-20260914-71d2e46cd 14 Sep 2026 none MIT — Details →
4.7.0-nightly-20260913-5336bb7f4 13 Sep 2026 none MIT — Details →
4.7.0-nightly-20260912-5336bb7f4 12 Sep 2026 none MIT — Details →
4.7.0-nightly-20260911-5336bb7f4 11 Sep 2026 none MIT — Details →
4.7.0-nightly-20260910-32a6e7e10 10 Sep 2026 none MIT — Details →
4.7.0-nightly-20260909-9d20dff17 09 Sep 2026 none MIT — Details →
4.7.0-nightly-20260908-7c8665b5a 08 Sep 2026 none MIT — Details →
4.7.0-nightly-20260907-afc7b9cdd 07 Sep 2026 none MIT — Details →
4.7.0-nightly-20260906-c2e9c026d 06 Sep 2026 none MIT — Details →
4.7.0-nightly-20260905-c2e9c026d 05 Sep 2026 none MIT — Details →
4.7.0-nightly-20260904-c2e9c026d 04 Sep 2026 none MIT — Details →
4.7.0-nightly-20260903-c2e9c026d 03 Sep 2026 none MIT — Details →
4.7.0-nightly-20260902-d62791191 02 Sep 2026 none MIT — Details →
4.7.0-nightly-20260901-805a4501e 01 Sep 2026 none MIT — Details →
4.7.0-nightly-20260831-805a4501e 31 Aug 2026 none MIT — Details →
4.7.0-nightly-20260830-05adcb7ee 30 Aug 2026 none MIT — Details →
4.7.0-nightly-20260829-05adcb7ee 29 Aug 2026 none MIT — Details →
4.7.0-nightly-20260828-05adcb7ee 28 Aug 2026 none MIT — Details →
4.7.0-nightly-20260828-e0762d9c0 28 Aug 2026 none MIT — Details →
4.5.5 27 Aug 2026 none MIT — Details →
4.7.0-nightly-20260827-a65753055 27 Aug 2026 none MIT — Details →
4.7.0-nightly-20260825-404c5649d 25 Aug 2026 none MIT — Details →
4.5.4 25 Aug 2026 none MIT — Details →
4.7.0-nightly-20260824-0788fcdeb 24 Aug 2026 none MIT — Details →
4.6.0 21 Aug 2026 none MIT — Details →
4.6.0-nightly-20260820-18970f775 20 Aug 2026 none MIT — Details →
4.6.0-nightly-20260819-d5d828f89 19 Aug 2026 none MIT — Details →
4.6.0-nightly-20260818-2a121ea78 18 Aug 2026 none MIT — Details →
4.6.0-nightly-20260817-b15bb32ab 18 Aug 2026 none MIT — Details →
4.6.0-nightly-20260816-8c1bcf8e2 16 Aug 2026 none MIT — Details →
4.6.0-nightly-20260815-4e0d15867 15 Aug 2026 none MIT — Details →
4.6.0-nightly-20260814-4e0d15867 14 Aug 2026 none MIT — Details →
4.6.0-nightly-20260813-b69d2ff6d 13 Aug 2026 none MIT — Details →
4.6.0-nightly-20260812-0f8cf6dcc 12 Aug 2026 none MIT — Details →
4.6.0-nightly-20260811-248dee712 11 Aug 2026 none MIT — Details →
4.6.0-nightly-20260810-fb9cb5596 10 Aug 2026 none MIT — Details →
4.3.4 10 Aug 2026 none MIT — Details →
4.6.0-nightly-20260809-d10808bc5 09 Aug 2026 none MIT — Details →
4.6.0-nightly-20260808-d10808bc5 08 Aug 2026 none MIT — Details →
4.6.0-nightly-20260807-d10808bc5 07 Aug 2026 none MIT — Details →
4.6.0-nightly-20260807-fb68ce75c 07 Aug 2026 none MIT — Details →
4.6.0-nightly-20260805-44bf4cf21 05 Aug 2026 none MIT — Details →
4.6.0-nightly-20260804-460019806 04 Aug 2026 none MIT — Details →
4.6.0-nightly-20260803-00a6c0b2e 04 Aug 2026 none MIT — Details →
4.6.0-nightly-20260802-1933c81db 02 Aug 2026 none MIT — Details →
4.6.0-nightly-20260801-1933c81db 01 Aug 2026 none MIT — Details →
4.6.0-nightly-20260731-1933c81db 31 Jul 2026 none MIT — Details →
4.6.0-nightly-20260730-722537265 30 Jul 2026 none MIT — Details →
4.6.0-nightly-20260729-33e89b086 29 Jul 2026 none MIT — Details →
4.6.0-nightly-20260728-97f1f7b15 28 Jul 2026 none MIT — Details →
4.6.0-nightly-20260727-757885b42 27 Jul 2026 none MIT — Details →
4.6.0-nightly-20260726-1e3608a90 26 Jul 2026 none MIT — Details →
4.6.0-nightly-20260725-1e3608a90 25 Jul 2026 none MIT — Details →
4.6.0-nightly-20260724-976586373 24 Jul 2026 none MIT — Details →
4.6.0-nightly-20260723-9933d2194 23 Jul 2026 none MIT — Details →
4.3.3 23 Jul 2026 none MIT — Details →
4.4.3 23 Jul 2026 none MIT — Details →
4.6.0-nightly-20260722-72274dc0a 22 Jul 2026 none MIT — Details →
4.5.3 22 Jul 2026 none MIT — Details →
4.6.0-nightly-20260721-3876aedb8 21 Jul 2026 none MIT — Details →
4.6.0-nightly-20260720-af2c3e3f8 20 Jul 2026 none MIT — Details →
4.6.0-nightly-20260719-55ef079be 19 Jul 2026 none MIT — Details →
4.6.0-nightly-20260718-55ef079be 18 Jul 2026 none MIT — Details →
4.6.0-nightly-20260717-55ef079be 17 Jul 2026 none MIT — Details →
4.6.0-nightly-20260716-d88c1b086 16 Jul 2026 none MIT — Details →
4.5.2 16 Jul 2026 none MIT — Details →
4.6.0-nightly-20260715-28da6f623 15 Jul 2026 none — — Details →
4.6.0-nightly-20260714-71053ec96 14 Jul 2026 none — — Details →
4.6.0-nightly-20260713-ae25bec74 13 Jul 2026 none — — Details →
4.6.0-nightly-20260712-12a8d1045 12 Jul 2026 none — — Details →
4.6.0-nightly-20260711-12a8d1045 11 Jul 2026 none — — Details →
4.6.0-nightly-20260710-12a8d1045 10 Jul 2026 none — — Details →
4.6.0-nightly-20260709-5eb775e3e 09 Jul 2026 none — — Details →
4.6.0-nightly-20260708-910cb26ee 08 Jul 2026 none — — Details →
4.6.0-nightly-20260707-ee9d9e569 07 Jul 2026 none — — Details →
4.6.0-nightly-20260706-be51e03bd 06 Jul 2026 none — — Details →
4.6.0-nightly-20260705-0f46da0e1 05 Jul 2026 none — — Details →
4.6.0-nightly-20260704-0f46da0e1 04 Jul 2026 none — — Details →
4.3.2 04 Jul 2026 none — — Details →
4.6.0-nightly-20260703-215b26021 03 Jul 2026 none — — Details →
4.6.0-nightly-20260702-4f032e785 02 Jul 2026 none — — Details →
4.4.2 02 Jul 2026 none — — Details →
4.5.1 02 Jul 2026 none — — Details →
4.6.0-nightly-20260701-143cd82d4 01 Jul 2026 none — — Details →
4.6.0-nightly-20260630-baf8d71ac 30 Jun 2026 none — — Details →
4.6.0-nightly-20260629-91934bd06 29 Jun 2026 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 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-native-reanimated

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →

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 react-native-reanimated

Is react-native-reanimated safe to use?

Vulert records 1 vulnerabilities for react-native-reanimated 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-native-reanimated's Vulert package health score?

Vulert scores react-native-reanimated 84/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-native-reanimated affected?

No. 4.7.1, 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-native-reanimated should I use?

4.7.1 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-native-reanimated have?

1 vulnerability is recorded for react-native-reanimated 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-native-reanimated vulnerabilities disclosed?

0 vulnerabilities were recorded for react-native-reanimated in the last 12 months, and the oldest entry in this database dates to 01 Oct 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 react-native-reanimated 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-native-reanimated for upcoming vulnerabilities?

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