limbo.watch

In limbo for 8 days

GHSA-4wq4-2ppv-q3hg

@better-auth/expo on npm · published in better-auth/better-auth

Read the advisory on GitHub ↗

Fixed in 1.7.16. Dependabot, npm audit and OSV-Scanner won’t flag this yet. Find it in your project

Facts

Severity
Critical · CVSS score 9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Affected versions (@better-auth/expo)
>= 1.4.0-beta.6, < 1.7.16As entered by the maintainer. Not reviewed.
Fixed in (@better-auth/expo)
1.7.16
Affected versions (@better-auth/expo)
>= 1.8.0-beta.0, < 1.8.0-beta.5As entered by the maintainer. Not reviewed.
Fixed in (@better-auth/expo)
1.8.0-beta.5
Affected versions (better-auth)
< 1.7.16As entered by the maintainer. Not reviewed.
Fixed in (better-auth)
1.7.16
Affected versions (better-auth)
>= 1.8.0-beta.0, < 1.8.0-beta.5As entered by the maintainer. Not reviewed.
Fixed in (better-auth)
1.8.0-beta.5
CVE
None cited by the advisory
GitHub Advisory Database
Not reviewed
OSV.dev
Not present
Other CVEs pointing here
CVE-2026-121802 (published by another CNA)

If you use @better-auth/expo >= 1.4.0-beta.6, < 1.7.16

Upgrade to 1.7.16 or later. Dependabot, npm audit and OSV-Scanner won’t flag this yet.

Timeline

  1. 2026-11-03 21:37 UTC

    Published by the maintainers

    No CVE cited

  2. 2026-11-04 14:42 UTC

    First seen by Limbowatch

    not reviewed · not in OSV

  3. Waiting

    Reviewed by GitHub

  4. Waiting

    In OSV; scanners can see it

Machine-readable record: feed/GHSA-4wq4-2ppv-q3hg.json