Skip to content

FIDO Client to Authenticator Protocol (CTAP) 2.3 Proposed Standard, February 26, 2026 #365

Closed

Description

@IshaiO

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

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

Activity

  1. moved this to 📋 Backlog in STS Roadmapon May 2, 2025
  2. added this to the 01. Milestone 1 milestone on May 2, 2025
  3. added
    needs reviewThis issue has been newly opened or updated and is awaiting review by the maintainers
    on May 2, 2025
  4. added
    Art 5a(23) ICFIntegrity & Core functionalities of EUDI Wallets
    on May 2, 2025
  5. OBIvision commented on May 5, 2025

    @OBIvision
  6. removed
    needs reviewThis issue has been newly opened or updated and is awaiting review by the maintainers
    on May 27, 2025
  7. changed the title [-]FIDO - Client to Authenticator Protocol (CTAP), Proposed Standard, February 28, 2025[/-] [+]FIDO - Client to Authenticator Protocol (CTAP) 2.2 Proposed Standard, July 14, 2025[/+] on Aug 7, 2025
  8. moved this from 📋 Backlog to 🏗 In progress in STS Roadmapon Aug 7, 2025
  9. added
    Domain: WalletCovers STSs specific to ARF and wallet operations such as credential formats, protocols, and APIs
    sts: readyThe standard has a stable version published
    on Sep 24, 2025
  10. added
    EssentialEssential to guarantee interoperability, issuance, presentation, and verification of a credential
    and removed
    EssentialEssential to guarantee interoperability, issuance, presentation, and verification of a credential
    on Oct 3, 2025
  11. 3 remaining items

  12. added
    FnRAn STS that specifies Functional Requirements
    on Dec 23, 2025
  13. changed the title [-]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[/+] on Jan 16, 2026
  14. added
    sts: needs follow upThe standard needs follow up due to a forthcoming updated version
    on Feb 25, 2026
  15. changed the title [-]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[/+] on Mar 28, 2026
  16. changed the title [-]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[/+] on Jul 5, 2026
  17. removed
    sts: needs follow upThe standard needs follow up due to a forthcoming updated version
    on Jul 7, 2026
  18. added
    CIR (EU) 2026/1731Amending CIR (EU) 2024/2977, (EU) 2024/2979, (EU) 2024/2980 and (EU) 2024/2982
    RegulationStandards referenced or mandated in the Implementing Acts (IA/CIR); binding for implementation.
    on Jul 27, 2026
  19. moved this from 🏗 In progress to ✅ Done in STS Roadmapon Jul 27, 2026
  20. closed this as completedby moving to ✅ Done in STS Roadmapon Jul 27, 2026
  21. removed
    sts: tentative etaThe standard needs more work. Final further away. The target date is tentative and needs review
    on Jul 27, 2026
  22. changed the title [-]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[/+] on Oct 25, 2026
  23. changed the title [-]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[/+] on Nov 1, 2026
  24. added
    needs reviewThis issue has been newly opened or updated and is awaiting review by the maintainers
    on Nov 3, 2026
  25. OBIvision commented on Nov 3, 2026

    @OBIvision

    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 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    CIR (EU) 2026/1731Amending CIR (EU) 2024/2977, (EU) 2024/2979, (EU) 2024/2980 and (EU) 2024/2982Domain: WalletCovers STSs specific to ARF and wallet operations such as credential formats, protocols, and APIsFn: AuthenticationFnRAn STS that specifies Functional RequirementsRegulationStandards referenced or mandated in the Implementing Acts (IA/CIR); binding for implementation.needs reviewThis issue has been newly opened or updated and is awaiting review by the maintainerssts: readyThe standard has a stable version published

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions