Vulnerability Database · npm · Package report
@react-three/fiber: vulnerability history, versions and safety
@react-three/fiber is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the npm ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on @react-three/fiber 9.8.2 i
Updated on 23 Oct 2026
Good news: 9.8.2, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Key ecosystem project
- Community Moderate
What to do: Stay on 9.8.2 or newer. This can change: a vulnerability disclosed tomorrow can affect 9.8.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 9.8.2 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 410 packages i
- Stars 33,020 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 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-three/fiber, 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.
- 10.0.0-canary.58acabc 21 Oct 2026
- 10.0.0-alpha.6 17 Oct 2026
- 10.0.0-canary.88b1ca7 17 Oct 2026
- 9.8.2 14 Oct 2026
- 10.0.0-canary.42caa10 14 Oct 2026
- 10.0.0-canary.e78793c 14 Oct 2026
- 10.0.0-canary.d46ab63 14 Oct 2026
- 10.0.0-canary.908b65b 13 Oct 2026
- 10.0.0-canary.4b18a0a 13 Oct 2026
- 10.0.0-canary.fbc659b 11 Oct 2026
- 10.0.0-canary.245de23 11 Oct 2026
- 10.0.0-canary.5140ac8 10 Oct 2026
- 10.0.0-canary.22cea7b 10 Oct 2026
- 10.0.0-canary.932f901 10 Oct 2026
- 10.0.0-canary.87166dc 10 Oct 2026
- 10.0.0-canary.494048e 10 Oct 2026
- 10.0.0-canary.a056612 06 Oct 2026
- 10.0.0-canary.fbd44ae 02 Oct 2026
- 10.0.0-canary.d0fe0de 01 Oct 2026
- 10.0.0-canary.04087d8 30 Sep 2026
- 10.0.0-canary.f511bb4 30 Sep 2026
- 10.0.0-canary.a1c1d93 30 Sep 2026
- 10.0.0-canary.54ec785 30 Sep 2026
- 10.0.0-canary.65af8e9 29 Sep 2026
- 10.0.0-canary.b9d5979 29 Sep 2026
- 10.0.0-canary.6413936 29 Sep 2026
- 10.0.0-canary.3f8df2b 29 Sep 2026
- 10.0.0-canary.f75fbf6 29 Sep 2026
- 10.0.0-canary.d458ee7 29 Sep 2026
- 10.0.0-canary.2e64646 29 Sep 2026
- 10.0.0-canary.f50076a 29 Sep 2026
- 10.0.0-canary.98da52a 29 Sep 2026
- 10.0.0-canary.1998a73 29 Sep 2026
- 10.0.0-canary.33238a1 29 Sep 2026
- 10.0.0-canary.dd5379c 29 Sep 2026
- 10.0.0-canary.ee5a08a 29 Sep 2026
- 10.0.0-canary.de8b03c 29 Sep 2026
- 10.0.0-canary.d202062 29 Sep 2026
- 10.0.0-canary.b86abaa 29 Sep 2026
- 10.0.0-canary.a9bd42a 29 Sep 2026
- 10.0.0-canary.590ca48 29 Sep 2026
- 10.0.0-canary.d5cebb9 29 Sep 2026
- 10.0.0-canary.e3891fb 29 Sep 2026
- 10.0.0-canary.43287ab 29 Sep 2026
- 10.0.0-canary.9b237a7 29 Sep 2026
- 10.0.0-canary.975e1e7 29 Sep 2026
- 10.0.0-canary.14007b4 26 Sep 2026
- 10.0.0-canary.f81281f 26 Sep 2026
- 10.0.0-canary.e53bd54 26 Sep 2026
- 10.0.0-canary.ab9effa 26 Sep 2026
- 10.0.0-canary.130aea9 26 Sep 2026
- 10.0.0-canary.bf4b0be 26 Sep 2026
- 10.0.0-canary.777b94d 26 Sep 2026
- 10.0.0-canary.de17310 26 Sep 2026
- 10.0.0-canary.dc0ec15 26 Sep 2026
- 10.0.0-canary.4bf885a 26 Sep 2026
- 10.0.0-canary.c4ecb6a 25 Sep 2026
- 10.0.0-canary.ea31ccd 25 Sep 2026
- 9.8.1 24 Sep 2026
- 9.8.0 22 Sep 2026
- 10.0.0-canary.24d1f81 20 Sep 2026
- 10.0.0-canary.d91831d 16 Sep 2026
- 10.0.0-canary.979dc2d 13 Sep 2026
- 10.0.0-alpha.5 08 Sep 2026
- 10.0.0-canary.27df622 08 Sep 2026
- 10.0.0-canary.4f9f64c 08 Sep 2026
- 10.0.0-canary.eb6c14f 08 Sep 2026
- 10.0.0-canary.0ea97c0 07 Sep 2026
- 10.0.0-canary.af75fd4 07 Sep 2026
- 10.0.0-canary.4f316e6 07 Sep 2026
- 10.0.0-canary.0fc81c2 07 Sep 2026
- 10.0.0-canary.c385e9f 04 Sep 2026
- 10.0.0-canary.cdaab7c 28 Aug 2026
- 10.0.0-canary.ce4bd5f 27 Aug 2026
- 10.0.0-canary.5d015c5 27 Aug 2026
- 10.0.0-canary.f49e56e 27 Aug 2026
- 10.0.0-canary.07c4f9d 27 Aug 2026
- 10.0.0-alpha.4 24 Aug 2026
- 10.0.0-canary.39882dd 24 Aug 2026
- 10.0.0-canary.7a50545 24 Aug 2026
- 10.0.0-canary.471df95 24 Aug 2026
- 10.0.0-canary.7dfc4e4 24 Aug 2026
- 10.0.0-canary.ac30da2 11 Aug 2026
- 10.0.0-canary.0f7fc9b 11 Aug 2026
- 10.0.0-canary.20de6b2 11 Aug 2026
- 10.0.0-canary.f5d9cbd 11 Aug 2026
- 10.0.0-canary.6eb9584 11 Aug 2026
- 10.0.0-canary.da7a768 11 Aug 2026
- 10.0.0-canary.fd3335d 11 Aug 2026
- 10.0.0-alpha.3 07 Aug 2026
- 10.0.0-canary.c6846c3 07 Aug 2026
- 10.0.0-canary.611635d 07 Aug 2026
- 10.0.0-canary.ba354c7 07 Aug 2026
- 10.0.0-canary.0d86c23 07 Aug 2026
- 10.0.0-canary.4bc4a97 07 Aug 2026
- 10.0.0-canary.5d86b8f 07 Aug 2026
- 10.0.0-canary.0f8db17 07 Aug 2026
- 10.0.0-canary.8f5b4d3 07 Aug 2026
- 10.0.0-canary.7b7cecd 07 Aug 2026
- 10.0.0-canary.60e7a38 07 Aug 2026
- 10.0.0-canary.76d2134 07 Aug 2026
- 10.0.0-canary.6d6e5ab 07 Aug 2026
- 10.0.0-canary.c5c1a94 01 Aug 2026
- 10.0.0-canary.1be335a 31 Jul 2026
- 10.0.0-canary.bc9af3b 31 Jul 2026
- 9.7.0 31 Jul 2026
- 10.0.0-canary.b6c54f2 30 Jul 2026
- 10.0.0-canary.e881a4a 30 Jul 2026
- 10.0.0-canary.4a21acb 30 Jul 2026
- 10.0.0-canary.ca63ccd 27 Jul 2026
- 10.0.0-canary.c49d4cb 27 Jul 2026
- 10.0.0-canary.0706a92 25 Jul 2026
- 10.0.0-canary.f046a54 25 Jul 2026
- 10.0.0-canary.5c62eb9 25 Jul 2026
- 10.0.0-canary.2c50459 08 Jul 2026
- 10.0.0-canary.164c7be 07 Jul 2026
- 10.0.0-canary.9806389 07 Jul 2026
- 10.0.0-canary.d6fdf72 07 Jul 2026
- 9.6.1 28 Apr 2026
- 9.6.0 13 Apr 2026
The newest 120 of 407 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.
02 Disclosure history
How often vulnerabilities are recorded
No dated vulnerabilities are recorded for this package yet.
Other ways into the data
03 Vulnerabilities
Recorded vulnerabilities for @react-three/fiber
No vulnerabilities match this view.
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
Questions
About @react-three/fiber
Is @react-three/fiber safe to use?
Vulert has no vulnerabilities on record for @react-three/fiber in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.
What is @react-three/fiber's Vulert package health score?
Vulert scores @react-three/fiber 86/100, which reads as healthy. 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-three/fiber affected?
No. 9.8.2, 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.
How many vulnerabilities does @react-three/fiber have?
0 vulnerabilities are recorded for @react-three/fiber in the npm ecosystem: 0 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 @react-three/fiber vulnerabilities disclosed?
0 vulnerabilities were recorded for @react-three/fiber in the last 12 months. 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-three/fiber 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-three/fiber for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @react-three/fiber version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.