GHSA-6hxq-p678-4hr2: Npm/@simplewebauthn/server vulnerability

Published Sep 4, 2026
·
Updated

Summary validateCertificatePath() does not verify that an attestation's certificate chain actually terminates at a configured trust anchor. When walking the chain it stops at the first self-signed certificate it finds (which could be user-supplied), and exits early.

This happens before the configured Apple/Google/etc trust anchor (which is concatenated to the end of the chain) is reached.

A user can therefore register a credential and have the server accept it as if it were backed by a genuine Apple / Android SafetyNet / Yubikey / etc.

Details packages/server/src/helpers/validateCertificatePath.ts:

The configured trust anchor is appended to the end of the untrusted chain (line 83):

ts const x5cWithTrustAnchor = x5cCertsParsed.concat([anchor]);

The walk then verifies each cert was signed by the next, but breaks on the first self-signed cert (lines 104–116):

ts if (issuer.subject === issuer.issuer) { // Root cert detected, make sure it signed itself const issuerSignedIssuer = await issuer.verify( { publicKey: issuer.publicKey, signatureOnly: true }, WebCrypto, ); if (!issuerSignedIssuer) { throw new InvalidSubjectAndIssuer(); } break; // <-- exits before the appended trust anchor is ever checked if user supplied self-signed cert comes first }

The success condition is therefore "the certs form an internally-consistent chain ending in some self-signed cert" Rather than "the chain terminates at one of the configured trust anchors."

Exploit shape

attacker sends: x5c = [ forgedLeaf (signed by attacker root), attackerSelfSignedRoot ]

library builds: [ forgedLeaf, attackerSelfSignedRoot, <configured Apple/Google/etc root> ]

walk: forgedLeaf -> attackerSelfSignedRoot (verifies, attacker controls both) attackerSelfSignedRoot is self-signed -> break attackerSelfSignedRoot -> configured root (NEVER CHECKED)

return true. The configured anchor never gets checked.

As far as observed, all attestation enforcement uses validateCertificatePath when using MDS etc.

Affected Software

1 affected componentFixes available
npm/@simplewebauthn/server<=13.3.1
13.3.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/@simplewebauthn/server to a version that resolves this vulnerability.

    Fixed in 13.3.2

Event History

Sep 4, 2026
Advisory Published
via GitHub·05:33 PM
Data Sourced
via GitHub·05:33 PM
DescriptionWeaknessAffected Software

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Deployments using @simplewebauthn/server to validate attestation certificate paths against configured trust anchors are affected. The issue applies where the server relies on that validation to establish that a credential is backed by a genuine Apple, Android SafetyNet, Yubikey, or similar attestation authority.

2

What does an attacker need to exploit it?

An attacker needs to register a credential while supplying an attestation certificate chain containing a self-signed certificate. The validation walk can stop at that user-supplied self-signed certificate before reaching the configured trust anchor.

3

What is the security impact of a successful exploit?

The server can accept an attacker-controlled credential as though it had a valid attestation chain rooted in a configured trusted authority. This bypasses the intended verification that the chain terminates at the configured trust anchor.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203