Repository navigation
Description
Formal name
FIDO Client to Authenticator Protocol (CTAP) 2.3 Proposed Standard, February 26, 2026
Overview
This specification describes an application layer protocol for communication between a roaming authenticator and another client/platform, as well as bindings of this application protocol to a variety of transport protocols using different physical media. The application layer protocol defines requirements for such transport protocols. Each transport binding defines the details of how such transport layer connections should be set up, in a manner that meets the requirements of the application layer protocol.
This specification is part of the FIDO2 project, which includes this specification and is related to the W3C WebAuthn specification, which is referred to in Annex V of CIR 2024/2979.
Work Plan
Current Version
- FIDO Client to Authenticator Protocol (CTAP) 2.3 Proposed Standard, February 26, 2026: Published as a Proposed Standard Specification, which is considered stable by industry. ( Note: "Stable” in FIDO terminology refers to a “proposed standard” status, which signals readiness for production use).
- It is referenced in CIR (EU) 2026/1731.
EC Assessment Status
- The EC assessed v2.2.
Forthcoming Version
- FIDO Client to Authenticator Protocol (CTAP) v2.3.1, Working Draft, May 29, 2026.
Updates
- 2026-10-05: CTAP v2.3.1 is now available for review. v2.3.1 does not include any changes from v2.3.0 except for the part that described CTAP Hybrid – which was moved to PXP. It is defined as a “Working Draft”.
- 2026-06-30: The EC updated the target date for the assessment to 2026-07-31.
- 2026-05-31: The EC updated the target date for the assessment to 2026-06-30.
- 2026-03-27: The EC updated the target date for the assessment to 2026-05-31.
- 2026-02-26: FIDO published v2.3.
- 2026-02-25: FIFO informed that a new version v2.3 is expected which will contains only minor and mostly editorial updates, clarifying ambiguities and small corrections.
- 2025-11-14: The EC expects to complete the assessment of v2.2 by 2025-12-18.
- 2025-07-14: FIDO published CTAP v2.2.
Alerts
There are no open alerts.
References
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fields✅ Done
Activity
OBIvision commentedon May 5, 2025
[-]FIDO - Client to Authenticator Protocol (CTAP), Proposed Standard, February 28, 2025[/-][+]FIDO - Client to Authenticator Protocol (CTAP) 2.2 Proposed Standard, July 14, 2025[/+]3 remaining items
[-]FIDO - Client to Authenticator Protocol (CTAP) 2.2 Proposed Standard, July 14, 2025[/-][+]FIDO Client to Authenticator Protocol (CTAP) 2.2 Proposed Standard, July 14, 2025[/+][-]FIDO Client to Authenticator Protocol (CTAP) 2.2 Proposed Standard, July 14, 2025[/-][+]FIDO Client to Authenticator Protocol (CTAP) 2.3 Proposed Standard, February 26, 2026[/+][-]FIDO Client to Authenticator Protocol (CTAP) 2.3 Proposed Standard, February 26, 2026[/-][+]FIDO Client to Authenticator Protocol (CTAP) v2.3, Proposed Standard, February 26, 2026[/+][-]FIDO Client to Authenticator Protocol (CTAP) v2.3, Proposed Standard, February 26, 2026[/-][+]FIDO Client to Authenticator Protocol (CTAP) v2.3.1, Working Draft, May 29, 2026[/+][-]FIDO Client to Authenticator Protocol (CTAP) v2.3.1, Working Draft, May 29, 2026[/-][+]FIDO Client to Authenticator Protocol (CTAP) 2.3 Proposed Standard, February 26, 2026[/+]OBIvision commentedon Nov 3, 2026
The main problem with FIDO2 is that CTAP2 is Bigtech spyware by design breaking the root requirement of Qualified Unlinkability.
That is probably intended as the part of the typical man-in-the-middle identity control mechanism .