Vulnerability Database · Packagist · Package report

web-auth/webauthn-framework: vulnerability history, versions and safety

web-auth/webauthn-framework is a package in the Packagist ecosystem. Vulert records 3 vulnerabilities for it across 114 releases, from Sep 2021 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded C1 M1 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 07 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on web-auth/webauthn-framework i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 07 May 2026. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 3 vulnerabilities on record across 4 years, 2 in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 3 over 4 years · 2 in the last year i
  • Latest disclosure 07 May 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i

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 holds for web-auth/webauthn-framework, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
5.3.0 L1 Yes Details →
5.2.3 M1 Yes Details →
5.2.2 M1 Yes Details →
5.2.1 M1 Yes Details →
5.2.0 M1 Yes Details →
5.1.3 M1 Yes Details →
5.1.2 M1 Yes Details →
5.1.1 M1 Yes Details →
5.1.0 M1 Yes Details →
5.0.1 M1 Yes Details →
5.0.0 M1 Yes Details →
4.9.3 M1 Yes Details →
4.9.2 M1 Yes Details →
4.9.1 M1 Yes Details →
4.9.0 M1 Yes Details →
4.8.7 M1 Yes Details →
4.8.6 M1 Yes Details →
4.8.5 M1 Yes Details →
4.8.4 M1 Yes Details →
4.8.3 M1 Yes Details →
4.8.2 M1 Yes Details →
4.8.1 M1 Yes Details →
4.8.0 M1 Yes Details →
4.7.9 M1 Yes Details →
4.7.8 M1 Yes Details →
4.7.7 M1 Yes Details →
4.7.6 M1 Yes Details →
4.7.5 M1 Yes Details →
4.7.4 M1 Yes Details →
4.7.3 M1 Yes Details →
4.7.2 M1 Yes Details →
4.7.1 M1 Yes Details →
4.7.0 M1 Yes Details →
4.6.4 M1 Yes Details →
4.6.3 M1 Yes Details →
4.6.2 M1 Yes Details →
4.6.1 M1 Yes Details →
4.6.0 M1 Yes Details →
4.5.2 M1 Yes Details →
4.5.1 M1 Yes Details →
4.5.0 M1 Yes Details →
4.4.3 M1 Yes Details →
4.4.2 M1 Yes Details →
4.4.1 M1 Yes Details →
4.4.0 M1 Yes Details →
4.3.1 M1 Yes Details →
4.3.0 M1 Yes Details →
4.2.3 M1 Yes Details →
4.2.2 M1 Yes Details →
4.2.1 M1 Yes Details →
4.2.0 M1 Yes Details →
4.1.5 M1 Yes Details →
4.1.4 M1 Yes Details →
4.1.3 M1 Yes Details →
4.1.2 M1 Yes Details →
4.1.1 M1 Yes Details →
4.1.0 M1 Yes Details →
v4.0.5 M1 Yes Details →
v4.0.4 M1 Yes Details →
v4.0.3 M1 Yes Details →
v4.0.2 M1 Yes Details →
v4.0.1 M1 Yes Details →
v4.0.0 M1 Yes Details →
v3.3.12 M1 Yes Details →
v3.3.11 M1 Yes Details →
v3.3.10 M1 Yes Details →
v3.3.9 M1 Yes Details →
v3.3.8 M1 Yes Details →
v3.3.7 M1 Yes Details →
v3.3.6 M1 Yes Details →
v3.3.5 M1 Yes Details →
v3.3.4 M1 Yes Details →
v3.3.3 C1 M1 Yes Details →
v3.3.2 C1 M1 Yes Details →
v3.3.1 C1 M1 Yes Details →
v3.3.0 C1 M1 Yes Details →
v3.2.12 M1 Yes Details →
v3.2.11 M1 Yes Details →
v3.2.10 M1 Yes Details →
v3.2.9 M1 Yes Details →
v3.2.8 M1 Yes Details →
v3.2.7 M1 Yes Details →
v3.2.6 M1 Yes Details →
v3.2.5 M1 Yes Details →
v3.2.4 M1 Yes Details →
v3.2.3 M1 Yes Details →
v3.2.2 M1 Yes Details →
v3.2.1 M1 Yes Details →
v3.2.0 M1 Yes Details →
v3.1.1 M1 Yes Details →
v3.1.0 M1 Yes Details →
v3.0.2 M1 Yes Details →
v3.0.1 M1 Yes Details →
v3.0.0 M1 Yes Details →
v2.1.7 M1 Yes Details →
v2.1.6 M1 Yes Details →
v2.1.5 M1 Yes Details →
v2.1.4 M1 Yes Details →
v2.1.3 M1 Yes Details →
v2.1.2 M1 Yes Details →
v2.1.1 M1 Yes Details →
v2.1.0 M1 Yes Details →
v2.0.3 M1 Yes Details →
v2.0.2 M1 Yes Details →
v2.0.1 M1 Yes Details →
v2.0.0 M1 Yes Details →
v2.0.0-alpha1 M1 Yes Details →
v1.2.2 M1 Yes Details →
v1.2.1 M1 Yes Details →
v1.2.0 M1 Yes Details →
v1.1.0 M1 Yes Details →
v1.1.0-alpha1 M1 Yes Details →
v1.0.1 M1 Yes Details →
v1.0.0 M1 Yes Details →

Newest 114 of 114 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for web-auth/webauthn-framework

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 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: 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 web-auth/webauthn-framework

Is web-auth/webauthn-framework safe to use?

Vulert records 3 vulnerabilities for web-auth/webauthn-framework in Packagist: 1 critical, 0 high, 1 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does web-auth/webauthn-framework have?

3 vulnerabilities are recorded for web-auth/webauthn-framework in the Packagist ecosystem: 1 critical, 0 high, 1 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new web-auth/webauthn-framework vulnerabilities disclosed?

2 vulnerabilities were recorded for web-auth/webauthn-framework in the last 12 months, and the oldest entry in this database dates to 29 Sep 2021. 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 web-auth/webauthn-framework 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 web-auth/webauthn-framework for upcoming vulnerabilities?

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