Incorrect Behavior Order: Authorization Before Parsing and Canonicalization Affecting etcd package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.37% (30th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-ETCD-18924547
  • published19 Aug 2026
  • disclosed12 Aug 2026

Introduced: 12 Aug 2026

NewCVE-2026-73499  (opens in a new tab)
CWE-551  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:10 etcd.

NVD Description

Note: Versions mentioned in the description apply only to the upstream etcd package and not the etcd package as distributed by RHEL. See How to fix? for RHEL:10 relevant fixed versions and status.

etcd is a distributed key-value store for the data of a distributed system. Prior to versions 3.5.33, 3.6.14, and 3.7.1, a user granted READ permission on a single exact key can use the Watch gRPC API with clientv3.WithFromKey() to receive watch events for every key lexicographically greater than or equal to the permitted key. In server/etcdserver/api/v3rpc/watch.go, the open-ended RangeEnd sentinel is rewritten before the RBAC permission check in server/auth/range_perm_cache.go function isRangeOpPermitted, causing the request to be treated as an exact-key watch. Range/Get and DeleteRange requests are not affected, and the issue affects only clusters with authentication enabled. This issue is fixed in versions 3.5.33, 3.6.14, and 3.7.1.

CVSS Base Scores

version 3.1