NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist, #243 most downloaded on Packagist
FIDO2/Webauthn Support For PHP
Latest stable
5.3.15
Last release 4 days ago
18 Nov 2026
Release timing varies
gaps range from 1 weeks to 3 months
Some releases are documented
notes for 19 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
8 years old
132 releases · first in 2019
Drag across the ruler to compare, or tap a release to open it.
PhpCertificateChainValidator validated the whole "x5c" as the certification path, so the topmost certificate of the chain had to be issued by the trus
PhpCertificateChainValidator validated the whole "x5c" as the
certification path, so the topmost certificate of the chain had to be
issued by the trust anchor. The FIDO Alliance now names GlobalSign Root
R46 as the root certificate of the metadata BLOB, and the BLOB ends its
"x5c" with GlobalSign Root R46 cross-signed by GlobalSign Root CA - R3:
the chain validated against R3 but not against R46, and
FidoAllianceCompliantMetadataService silently loaded no statement.
RFC 5280 makes the trust anchor an input of the validation, not a
certificate of the path. The validator now tries each tail of the
chain, from the end-entity certificate alone up to the whole chain, and
keeps the first one that validates against the trust anchor: with R46
the path stops below the cross-certificate, with R3 it goes through it.
The certificates above that path take part neither in the validation
nor in the revocation checks. The chain keeps the order RFC 7515
prescribes for "x5c", so a chain the client controls costs one attempt
per certificate.
The hint of FidoAllianceCompliantMetadataService about the root
certificate URI now points to GlobalSign Root R46.
Closes #1016
PhpCertificateChainValidator validated the whole "x5c" as the certification path, so the topmost certificate of the chain had to be issued by the trus
PhpCertificateChainValidator validated the whole "x5c" as the
certification path, so the topmost certificate of the chain had to be
issued by the trust anchor. The FIDO Alliance now names GlobalSign Root
R46 as the root certificate of the metadata BLOB, and the BLOB ends its
"x5c" with GlobalSign Root R46 cross-signed by GlobalSign Root CA - R3:
the chain validated against R3 but not against R46, and
FidoAllianceCompliantMetadataService silently loaded no statement.
RFC 5280 makes the trust anchor an input of the validation, not a
certificate of the path. The validator now tries each tail of the
chain, from the end-entity certificate alone up to the whole chain, and
keeps the first one that validates against the trust anchor: with R46
the path stops below the cross-certificate, with R3 it goes through it.
The certificates above that path take part neither in the validation
nor in the revocation checks. The chain keeps the order RFC 7515
prescribes for "x5c", so a chain the client controls costs one attempt
per certificate.
The hint of FidoAllianceCompliantMetadataService about the root
certificate URI now points to GlobalSign Root R46.
Closes #1016
Your coding agent can read these notes before it upgrades. Set up the MCP server →
fix(string-stream): check the bytes left before reading them (GHSA-rx…
fix(string-stream): check the bytes left before reading them (GHSA-rx…
fix(tpm): verify a TPM attestation signed with SHA-1 when the applica…
fix(tpm): verify a TPM attestation signed with SHA-1 when the applica…
This project publishes no release notes. Between 5.3.11 and 5.3.12 there were 1 commits, 1 of them substantive:
WebauthnAuthenticationCollector accepted "webauthn.create" and "webauthn.get" in either ceremony, so the client data of an authentication was accepted
WebauthnAuthenticationCollector accepted "webauthn.create" and
"webauthn.get" in either ceremony, so the client data of an
authentication was accepted at a registration, and the client data of a
registration at an authentication. Webauthn Level 3 binds each ceremony
to its type: "Verify that the value of C.type is webauthn.create."
(section 7.1) and "Verify that the value of C.type is the string
webauthn.get." (section 7.2). The validators compared the type with
their ceremony until the ceremony steps of 4.8.0, whose collector
accepts both values.
The collector now expects "webauthn.create" when the options are
PublicKeyCredentialCreationOptions and "webauthn.get" otherwise, and
throws "The client data type is not "webauthn.create"." or "The client
data type is not "webauthn.get".", the messages of the validators before
4.8.0. supportedTypes() still returns both values, so
ClientDataCollectorManager keeps selecting this collector for either
type, and the collector refuses the type of the other ceremony.
The FIDO Conformance Tools 1.9.3.1 check it in
Server-ServerAuthenticatorAttestationResponse-Resp-2 F-5 and
Server-ServerAuthenticatorAssertionResponse-Resp-2 F-5.
Closes #986
This project publishes no release notes. Between 5.3.10 and 5.3.11 there were 5 commits, 4 of them substantive:
fix(fake-credentials): emit raw bytes as fake credential IDs (GHSA-8g…
fix(fake-credentials): emit raw bytes as fake credential IDs (GHSA-8g…
This project publishes no release notes. Between 5.3.9 and 5.3.10 there were 8 commits, 7 of them substantive:
BREAKING CHANGE: webauthn.cose.algorithm.ED256 and webauthn.cose.algorithm.ED512 are no longer registered, so the default verification manager no long…
Both dependencies published security advisories. Raising the constraints
guarantees users get the patched releases instead of relying on Composer
picking a recent enough version.
cose-lib 4.8.0 now enforces X.690 section 8.1.3 when parsing an ECDSA
signature: the SEQUENCE length octets must cover exactly the contents
octets. The ES512 left-padding fixture declared 134 content octets while
carrying 135, so it is rejected as malformed. The fixture is corrected to
0x87, the length it always should have had.
Ed256 (-260) and Ed512 (-261) sign a SHA-256 or SHA-512 digest of the payload
with pure Ed25519, a construction no specification defines. IANA assigned both
identifiers to unrelated algorithms, WalnutDSA and TurboSHAKE128.
As of 4.8.0, web-auth/cose-lib emits an E_USER_WARNING when either algorithm is
built without an explicit acknowledgement, and the Symfony error handler turns
that warning into an exception in the dev environment, so every attestation or
assertion request answers with a 500 as soon as the algorithm manager is built.
This is the same failure RS1 caused, with the same resolution: the bundle does
not acknowledge a questionable algorithm on behalf of the applications, so the
definitions are removed instead.
BREAKING CHANGE: webauthn.cose.algorithm.ED256 and webauthn.cose.algorithm.ED512
are no longer registered, so the default verification manager no longer accepts
their signatures. The bundle never offered them at the registration, since
public_key_credential_parameters defaults to an empty list, so only the
applications that explicitly added -260 or -261 to that list are affected. They
have to declare the services themselves; autoconfiguration adds them back to the
manager.
This project publishes no release notes. Between 5.3.8 and 5.3.9 there were 1 commits, 1 of them substantive:
fix(rp-entity): default rp.name to the Relying Party ID when serializ…
fix(rp-entity): default rp.name to the Relying Party ID when serializ…
fix(rp-entity): default rp.name to the Relying Party ID when serializ…
fix(rp-entity): default rp.name to the Relying Party ID when serializ…
This project publishes no release notes. Between 5.3.6 and 5.3.7 there were 2 commits, 2 of them substantive:
fix(authenticator-data): restrict FLAG_RFU2 to bit 5
Bits 3 and 4 were reserved in Webauthn Level 2 and have been assigned to
BE (Backup Eligibility) and BS (Backup State) in Level 3. The mask was
never narrowed, so getReservedForFutureUse2() reported the backup flags
a second time: a synced passkey with BE and BS set returned 24 instead
of 0.
Closes #920
The specification requires the keys of the evalByCredential map to be
the base64url encoding of the credential ID, and the client rejects the
ceremony with a SyntaxError otherwise. The builder encoded the salts but
used the credential ID as given, which made a raw credential ID produce
an invalid key.
Closes #924
tokenBinding is [RESERVED] since Webauthn Level 3. The value was never
read nor exposed, so the only effect of the check was to fail a ceremony
over a member the Relying Party does not use, with a truncated error
message. The raw client data remains available through the data
property.
Closes #929
The ASN.1 DER encoding of an ECDSA signature has a variable length, as
w3c/webauthn#2315 now makes explicit in the specification example. The
class handling the conversion had no test at all.
Closes #930
This project publishes no release notes. Between 5.3.5 and 5.3.6 there were 4 commits, 4 of them substantive:
fix(fake-credentials): deprecate SimpleFakeCredentialGenerator without a secret ( GHSA-gq4g-fpc9-vjfq )
With an empty secret the decoy credentials derive only from the username
and become predictable, letting an unauthenticated requester tell fake
responses from real ones and re-enabling username enumeration. Emit a
deprecation when the generator is built without a secret; a non-empty
secret will be required in 6.0.0. The Symfony bundle already injects
kernel.secret, so default deployments are unaffected.
Validates the fix and guards against regressions:
fix(top-origin): reject cross-origin responses when no validator is c…
fix(top-origin): reject cross-origin responses when no validator is c…
This project publishes no release notes. Between 5.3.3 and 5.3.4 there were 1 commits, 1 of them substantive:
fix(origins): accept non-URL facet IDs (e.g. android:apk-key-hash:...…
fix(origins): accept non-URL facet IDs (e.g. android:apk-key-hash:...…
feat: support Conditional Create (mediation) for auto-register flows …
feat: support Conditional Create (mediation) for auto-register flows …
feat: support Conditional Create (mediation) for auto-register flows …
feat: support Conditional Create (mediation) for auto-register flows …
feat: support Conditional Create (mediation) for auto-register flows …
feat: support Conditional Create (mediation) for auto-register flows …
Nothing published for this version
fix: enforce HTTPS scheme check in CheckAllowedOrigins fallback path …
fix: enforce HTTPS scheme check in CheckAllowedOrigins fallback path …
fix: add PHPStan type annotations for parse_url() return values in Ch…
fix: add PHPStan type annotations for parse_url() return values in Ch…
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
AuthenticatorAssertionResponseValidator: Add missing word from deprec…
AuthenticatorAssertionResponseValidator: Add missing word from deprec…
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.