VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

expo: vulnerability history, versions and safety

expo is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 0 release, from May 2022 to Apr 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 C1 M1
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 expo vulnerabilities

Vulert verdict on expo 58.0.17 i

Updated on 23 Oct 2026

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

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

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

  • Current release 58.0.17 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 24 Apr 2023 i
  • Highest CVSS 9.6 i
  • With no published fix 0 i
  • Depended on by 67 packages i
  • Stars 52,895 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 expo, 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
58.0.17 21 Oct 2026 none MIT — Details →
54.0.38 21 Oct 2026 none MIT — Details →
55.0.32 21 Oct 2026 none MIT — Details →
56.0.24 21 Oct 2026 none MIT — Details →
57.0.31 21 Oct 2026 none MIT — Details →
58.0.16 19 Oct 2026 none MIT — Details →
58.0.15 19 Oct 2026 none MIT — Details →
58.0.14 16 Oct 2026 none MIT — Details →
58.0.13 16 Oct 2026 none MIT — Details →
58.0.12 16 Oct 2026 none MIT — Details →
58.0.11 15 Oct 2026 none MIT — Details →
57.0.30 15 Oct 2026 none MIT — Details →
58.0.10 14 Oct 2026 none MIT — Details →
57.0.29 14 Oct 2026 none MIT — Details →
58.0.9 13 Oct 2026 none MIT — Details →
58.0.8 13 Oct 2026 none MIT — Details →
57.0.28 12 Oct 2026 none MIT — Details →
58.0.7 09 Oct 2026 none MIT — Details →
58.0.6 06 Oct 2026 none MIT — Details →
57.0.27 06 Oct 2026 none MIT — Details →
58.0.5 05 Oct 2026 none MIT — Details →
58.0.4 05 Oct 2026 none MIT — Details →
58.0.3 03 Oct 2026 none MIT — Details →
58.0.2 01 Oct 2026 none MIT — Details →
58.0.1 01 Oct 2026 none MIT — Details →
58.0.0 29 Sep 2026 none MIT — Details →
56.0.23 29 Sep 2026 none MIT — Details →
57.0.26 29 Sep 2026 none MIT — Details →
58.0.0-preview.8 28 Sep 2026 none MIT — Details →
58.0.0-preview.7 25 Sep 2026 none MIT — Details →
57.0.25 24 Sep 2026 none MIT — Details →
58.0.0-preview.6 23 Sep 2026 none MIT — Details →
58.0.0-preview.5 22 Sep 2026 none MIT — Details →
58.0.0-preview.4 21 Sep 2026 none MIT — Details →
57.0.24 18 Sep 2026 none MIT — Details →
56.0.22 17 Sep 2026 none MIT — Details →
58.0.0-preview.3 16 Sep 2026 none MIT — Details →
58.0.0-preview.2 15 Sep 2026 none MIT — Details →
57.0.23 15 Sep 2026 none MIT — Details →
58.0.0-preview.1 14 Sep 2026 none MIT — Details →
57.0.22 11 Sep 2026 none MIT — Details →
58.0.0-preview.0 10 Sep 2026 none MIT — Details →
58.0.0-canary-20260909-ea7a89a 09 Sep 2026 none MIT — Details →
57.0.21 08 Sep 2026 none MIT — Details →
57.0.20 04 Sep 2026 none MIT — Details →
58.0.0-canary-20260902-26df09e 02 Sep 2026 none MIT — Details →
57.0.19 01 Sep 2026 none MIT — Details →
55.0.31 31 Aug 2026 none MIT — Details →
57.0.18 28 Aug 2026 none MIT — Details →
56.0.21 28 Aug 2026 none MIT — Details →
57.0.17 26 Aug 2026 none MIT — Details →
55.0.30 25 Aug 2026 none MIT — Details →
57.0.16 24 Aug 2026 none MIT — Details →
57.0.15 20 Aug 2026 none MIT — Details →
54.0.37 17 Aug 2026 none MIT — Details →
55.0.29 17 Aug 2026 none MIT — Details →
56.0.20 17 Aug 2026 none MIT — Details →
57.0.14 17 Aug 2026 none MIT — Details →
57.0.13 14 Aug 2026 none MIT — Details →
58.0.0-canary-20260812-27f94d4 12 Aug 2026 none MIT — Details →
57.0.12 10 Aug 2026 none MIT — Details →
58.0.0-canary-20260806-8c2d007 06 Aug 2026 none MIT — Details →
56.0.19 06 Aug 2026 none MIT — Details →
57.0.11 06 Aug 2026 none MIT — Details →
57.0.10 04 Aug 2026 none MIT — Details →
56.0.18 29 Jul 2026 none MIT — Details →
57.0.9 29 Jul 2026 none MIT — Details →
57.0.0-canary-20260723-64edab9 23 Jul 2026 none MIT — Details →
56.0.17 23 Jul 2026 none MIT — Details →
57.0.8 22 Jul 2026 none MIT — Details →
57.0.0-canary-20260720-b6d63bc 20 Jul 2026 none MIT — Details →
57.0.0-canary-20260718-7cbcda5 18 Jul 2026 none MIT — Details →
57.0.7 17 Jul 2026 none MIT — Details →
57.0.0-canary-20260716-381e806 16 Jul 2026 none MIT — Details →
54.0.36 15 Jul 2026 none MIT — Details →
55.0.28 15 Jul 2026 none MIT — Details →
56.0.16 15 Jul 2026 none MIT — Details →
57.0.6 15 Jul 2026 none MIT — Details →
57.0.5 15 Jul 2026 none MIT — Details →
57.0.4 07 Jul 2026 none MIT — Details →
56.0.15 07 Jul 2026 none MIT — Details →
57.0.3 07 Jul 2026 none MIT — Details →
56.0.14 03 Jul 2026 none MIT — Details →
57.0.2 03 Jul 2026 none MIT — Details →
56.0.6-canary-20260701-9100865 01 Jul 2026 none MIT — Details →
56.0.13 01 Jul 2026 none MIT — Details →
57.0.1 30 Jun 2026 none MIT — Details →
57.0.0 30 Jun 2026 none MIT — Details →
57.0.0-canary-20260629-3010085 29 Jun 2026 none MIT — Details →
57.0.0-preview.1 27 Jun 2026 none MIT — Details →
57.0.0-preview.0 25 Jun 2026 none MIT — Details →
55.0.27 25 Jun 2026 none MIT — Details →
56.0.6-canary-20260624-9d83b81 24 Jun 2026 none MIT — Details →
56.0.12 15 Jun 2026 none MIT — Details →
56.0.11 10 Jun 2026 none MIT — Details →
56.0.10 10 Jun 2026 none MIT — Details →
56.0.6-canary-20260606-4d4666c 06 Jun 2026 none MIT — Details →
56.0.9 05 Jun 2026 none MIT — Details →
56.0.8 29 May 2026 none MIT — Details →
56.0.7 29 May 2026 none MIT — Details →
54.0.35 28 May 2026 none — — Details →
56.0.6 28 May 2026 none — — Details →
56.0.6-canary-20260526-6cd5e37 26 May 2026 none — — Details →
56.0.5 26 May 2026 none — — Details →
57.0.0-canary-20260526-13e89ca 26 May 2026 none — — Details →
56.0.4 23 May 2026 none — — Details →
56.0.3 21 May 2026 none — — Details →
55.0.26 21 May 2026 none — — Details →
56.0.2 21 May 2026 none — — Details →
56.0.1 21 May 2026 none — — Details →
56.0.0 20 May 2026 none — — Details →
55.0.25 19 May 2026 none — — Details →
56.0.0-preview.13 19 May 2026 none — — Details →
56.0.0-preview.12 15 May 2026 none — — Details →
56.0.0-preview.11 14 May 2026 none — — Details →
56.0.0-preview.10 13 May 2026 none — — Details →
55.0.24 13 May 2026 none — — Details →
56.0.0-preview.9 12 May 2026 none — — Details →
56.0.0-preview.8 11 May 2026 none — — Details →
56.0.0-preview.7 08 May 2026 none — — Details →

The newest 120 of 1,009 versions Vulert tracks. 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 expo

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-28131: Expo Package OAuth Vulnerability Leading to Account Takeover 9.6 critical 48.0.0 24 Apr 2023
CVE-2020-24653: Insecure Security Attribute Application in Expo on iOS N/A medium 9.1.0 24 May 2022

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 expo

Is expo safe to use?

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

Vulert scores expo 79/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 expo affected?

No. 58.0.17, 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 expo have?

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

0 vulnerabilities were recorded for expo 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 expo 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 expo for upcoming vulnerabilities?

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