Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Etcd pkg Insecure ciphers are allowed by default

GHSA-5x4g-q5rc-36jp

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (go.etcd.io/etcd/client/pkg/v3 3.4.10, 3.3.23), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Vulnerability type Cryptography Detail The TLS ciphers list supported by etcd contains insecure cipher suites. Users can configure the desired ciphers using the “--cipher-suites” flag, and a default list of secure cipher suites is used if empty. Workarounds By default, no action is required. If users want to specify cipher suites using the '--cipher-suites' flag, they should try not to specify insecure cipher suites. Please refer to the security documentation. References Find out more on this vulnerability in the security audit report For more information If you have any questions or comments about this advisory: Contact the etcd security committee

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-5x4g-q5rc-36jp

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-5x4g-q5rc-36jp

Advisory: Etcd pkg Insecure ciphers are allowed by default
IDs: GHSA-5x4g-q5rc-36jp
Record: https://patchnext.com/advisories/ghsa-5x4g-q5rc-36jp (revision 1, source checked 26 Oct 2026, 15:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: go.etcd.io/etcd/client/pkg/v3 3.4.10, 3.3.23. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go go.etcd.io/etcd/client/pkg/v3: affected >= 3.4.0-rc.0, <= 3.4.9; < 3.3.23; fixed in 3.3.23, 3.4.10

## Suggested inspection (read-only)
- Go go.etcd.io/etcd/client/pkg/v3: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on go.etcd.io/etcd/client/pkg/v3.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-5x4g-q5rc-36jp (GitHub-reviewed advisory GHSA-5x4g-q5rc-36jp lists affected ranges: Go go.etcd.io/etcd/client/pkg/v3 >=3.4.0-rc.0 =0 <3.3.23)

Commands are suggestions: review each one before running it.

Loading voting…