Skip to content

Releases: hyperledger/fabric-ca

v1.5.17

06 Feb 16:12

Choose a tag to compare

v1.5.17 Release Notes - February 6, 2026

v1.5.17 updates dependencies to address the following security vulnerabilities:

This release also allows CA URLs to include path components. For example, https://my-fabric-ca/ca. Previously only https://my-fabric-ca would be accepted.

Dependencies

Fabric CA v1.5.17 has been tested with the following dependencies:

  • Go 1.25.7
  • Ubuntu 22.04 (for Docker images)
  • Databases
    • PostgreSQL 17
    • MariaDB 11

Full Changelog: v1.5.16...v1.5.17

v1.5.16

08 Dec 03:01

Choose a tag to compare

v1.5.16 Release Notes - December 7, 2025

v1.5.16 updates dependencies.

Dependencies

Fabric CA v1.5.16 has been tested with the following dependencies:

  • Go 1.25.5
  • Ubuntu 22.04 (for Docker images)
  • Databases
    • PostgreSQL 13
    • MySQL 8.0

v1.5.15

08 Feb 04:44

Choose a tag to compare

v1.5.15 Release Notes - February 7, 2025

v1.5.15 adds logging of Fabric CA server configuration upon startup,
as well as the configuration for FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3
to assist with the change mentioned below that was delivered in v1.5.14.

Dependencies

Fabric CA v1.5.15 has been tested with the following dependencies:

  • Go 1.23.5
  • Ubuntu 22.04 (for Docker images)
  • Databases
    • PostgreSQL 13
    • MySQL 8.0

Changes

In Fabric CA v1.4 a more secure mechanism was made available for authentication.
Most Fabric CA clients have been updated to utilize the new authentication header,
therefore Fabric CA v1.5.14 changes the default to utilize the more secure mechanism.
If you have an older Fabric CA client you can still utilize the prior mechanism by
setting the following environment variable on the Fabric CA server:

FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=true

Known Vulnerabilities

None.

Resolved Vulnerabilities

None.

v1.5.14

27 Jan 23:03

Choose a tag to compare

v1.5.14 Release Notes - January 27, 2025

v1.5.14 updates code dependencies.

Dependencies

Fabric CA v1.5.14 has been tested with the following dependencies:

  • Go 1.23.5
  • Ubuntu 20.04 (for Docker images)
  • Databases
    • PostgreSQL 13
    • MySQL 8.0

Changes

In Fabric CA v1.4 a more secure mechanism was made available for authentication.
Most Fabric CA clients have been updated to utilize the new authentication header,
therefore Fabric CA v1.5.14 changes the default to utilize the more secure mechanism.
If you have an older Fabric CA client you can still utilize the prior mechanism by
setting the following environment variable on the Fabric CA server:

FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=true

Known Vulnerabilities

None.

Resolved Vulnerabilities

None.

v1.5.13

20 Sep 11:24
c7d4eb9

Choose a tag to compare

v1.5.13 Release Notes - September 20, 2024

v1.5.13 updates code dependencies.

Dependencies

Fabric CA v1.5.13 has been tested with the following dependencies:

  • Go 1.23.1
  • Ubuntu 20.04 (for Docker images)
  • Databases
    • PostgreSQL 13
    • MySQL 8.0

Changes, Known Issues, and Workarounds

None.

Known Vulnerabilities

  • FABC-174 Commands can be manipulated to delete identities or affiliations

    This vulnerability can be resolved in one of two ways:

    1. Use HTTPS (TLS) so that the authorization header is not in clear text.

    2. The token generation/authentication mechanism was improved to optionally prevent
      token reuse. As of v1.4 a more secure token can be used by setting environment variable:

    FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false

    However, it cannot be set to false until all clients have
    been updated to generate the more secure token and tolerate
    FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false.
    The Fabric CA client has been updated in v1.4 to generate the more secure token.
    The Fabric SDKs will be updated by v2.0 timeframe to generate the more secure token,
    at which time the default for Fabric CA server will change to:
    FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false

Resolved Vulnerabilities

None.

v1.5.12

18 Jun 17:20

Choose a tag to compare

v1.5.12 Release Notes - June 18, 2024

v1.5.12 updates code dependencies.

Dependencies

Fabric CA v1.5.12 has been tested with the following dependencies:

  • Go 1.22.4
  • Ubuntu 20.04 (for Docker images)
  • Databases
    • PostgreSQL 13
    • MySQL 8.0

Changes, Known Issues, and Workarounds

None.

Known Vulnerabilities

  • FABC-174 Commands can be manipulated to delete identities or affiliations

    This vulnerability can be resolved in one of two ways:

    1. Use HTTPS (TLS) so that the authorization header is not in clear text.

    2. The token generation/authentication mechanism was improved to optionally prevent
      token reuse. As of v1.4 a more secure token can be used by setting environment variable:

    FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false

    However, it cannot be set to false until all clients have
    been updated to generate the more secure token and tolerate
    FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false.
    The Fabric CA client has been updated in v1.4 to generate the more secure token.
    The Fabric SDKs will be updated by v2.0 timeframe to generate the more secure token,
    at which time the default for Fabric CA server will change to:
    FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false

Resolved Vulnerabilities

None.

v1.5.11

21 May 19:20

Choose a tag to compare

v1.5.11 Release Notes - May 21, 2024

v1.5.11 updates code dependencies.

Dependencies

Fabric CA v1.5.11 has been tested with the following dependencies:

  • Go 1.22.3
  • Ubuntu 20.04 (for Docker images)
  • Databases
    • PostgreSQL 13
    • MySQL 8.0

Changes, Known Issues, and Workarounds

None.

Known Vulnerabilities

  • FABC-174 Commands can be manipulated to delete identities or affiliations

    This vulnerability can be resolved in one of two ways:

    1. Use HTTPS (TLS) so that the authorization header is not in clear text.

    2. The token generation/authentication mechanism was improved to optionally prevent
      token reuse. As of v1.4 a more secure token can be used by setting environment variable:

    FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false

    However, it cannot be set to false until all clients have
    been updated to generate the more secure token and tolerate
    FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false.
    The Fabric CA client has been updated in v1.4 to generate the more secure token.
    The Fabric SDKs will be updated by v2.0 timeframe to generate the more secure token,
    at which time the default for Fabric CA server will change to:
    FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false

Resolved Vulnerabilities

None.

v1.5.10

15 Apr 17:21

Choose a tag to compare

v1.5.10 Release Notes - April 15, 2024

v1.5.10 updates code dependencies.

Dependencies

Fabric CA v1.5.10 has been tested with the following dependencies:

  • Go 1.21.9
  • Ubuntu 20.04 (for Docker images)
  • Databases
    • PostgreSQL 13
    • MySQL 8.0

Changes, Known Issues, and Workarounds

None.

Known Vulnerabilities

  • FABC-174 Commands can be manipulated to delete identities or affiliations

    This vulnerability can be resolved in one of two ways:

    1. Use HTTPS (TLS) so that the authorization header is not in clear text.

    2. The token generation/authentication mechanism was improved to optionally prevent
      token reuse. As of v1.4 a more secure token can be used by setting environment variable:

    FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false

    However, it cannot be set to false until all clients have
    been updated to generate the more secure token and tolerate
    FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false.
    The Fabric CA client has been updated in v1.4 to generate the more secure token.
    The Fabric SDKs will be updated by v2.0 timeframe to generate the more secure token,
    at which time the default for Fabric CA server will change to:
    FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false

Resolved Vulnerabilities

None.

v1.5.9

19 Feb 03:38

Choose a tag to compare

v1.5.9 Release Notes - February 19, 2024

v1.5.9 updates code dependencies, and removes dependency on core fabric.

Dependencies

Fabric CA v1.5.9 has been tested with the following dependencies:

  • Go 1.21.6
  • Ubuntu 20.04 (for Docker images)
  • Databases
    • PostgreSQL 13
    • MySQL 8.0

Changes, Known Issues, and Workarounds

None.

Known Vulnerabilities

  • FABC-174 Commands can be manipulated to delete identities or affiliations

    This vulnerability can be resolved in one of two ways:

    1. Use HTTPS (TLS) so that the authorization header is not in clear text.

    2. The token generation/authentication mechanism was improved to optionally prevent
      token reuse. As of v1.4 a more secure token can be used by setting environment variable:

    FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false

    However, it cannot be set to false until all clients have
    been updated to generate the more secure token and tolerate
    FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false.
    The Fabric CA client has been updated in v1.4 to generate the more secure token.
    The Fabric SDKs will be updated by v2.0 timeframe to generate the more secure token,
    at which time the default for Fabric CA server will change to:
    FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false

Resolved Vulnerabilities

None.

v1.5.8

21 Dec 19:35

Choose a tag to compare

v1.5.8 Release Notes - December 20, 2023

Fixes

Fix s390x build

Update github.com/IBM/mathlib to fix compilation issue on s390x.
#387

Improvements

Log expiry overrides

If certificate expiry during enrollment gets overridden due to the CA's own expiry,
log a warning message about the override.
#384

Dependencies

Fabric CA v1.5.8 has been tested with the following dependencies:

  • Go 1.21.5
  • Ubuntu 20.04 (for Docker images)
  • Databases
    • PostgreSQL 13
    • MySQL 8.0

Changes, Known Issues, and Workarounds

None.

Known Vulnerabilities

  • FABC-174 Commands can be manipulated to delete identities or affiliations

    This vulnerability can be resolved in one of two ways:

    1. Use HTTPS (TLS) so that the authorization header is not in clear text.

    2. The token generation/authentication mechanism was improved to optionally prevent
      token reuse. As of v1.4 a more secure token can be used by setting environment variable:

    FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false

    However, it cannot be set to false until all clients have
    been updated to generate the more secure token and tolerate
    FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false.
    The Fabric CA client has been updated in v1.4 to generate the more secure token.
    The Fabric SDKs will be updated by v2.0 timeframe to generate the more secure token,
    at which time the default for Fabric CA server will change to:
    FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3=false

Resolved Vulnerabilities

None.