Skip to content
Fencer Intel
low 3.1

GHSA-gv75-j3v8-3crm json

@better-auth/passkey: Passkey verification does not enforce origin or user verification

published 8d ago modified 8d ago

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository better-auth/better-auth. GitHub has not reviewed it into the GitHub Advisory Database and no CVE record has reached us yet, so everything here comes from the maintainers alone. Read the full advisory on GitHub.

cvss
3.1
version 3.1, the maintainers
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

Security advisory published by the maintainers of better-auth/better-auth for @better-auth/passkey and better-auth: the maintainers' own advisory, not a reviewed GitHub Advisory Database entry. The full advisory is on GitHub.

Patch / fix

  • npm @better-auth/passkey 1.7.16, 1.8.0-beta.5
  • npm better-auth 1.4.0

Is GHSA-gv75-j3v8-3crm in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
the maintainers 3.1 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
npm @better-auth/passkey
>=1.4.0-beta.16, <1.7.16
>=1.8.0-beta.0, <1.8.0-beta.5
1.7.16
1.8.0-beta.5
npm better-auth
>=1.2.0-beta.18, <1.4.0
1.4.0

Classification

Weakness
  • CWE-346 Origin Validation Error
  • CWE-602 Client-Side Enforcement of Server-Side Security

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of better-auth/better-auth published their own advisory on GitHub. Its facts and headline are shown here; the description stays on GitHub.