CVE-2026-33343

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 88% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

etcd is a distributed key-value store for the data of a distributed system. Prior to versions 3.4.42, 3.5.28, and 3.6.9, an authenticated user with RBAC restricted permissions on key ranges can use nested transactions to bypass all key-level authorization. This allows any authenticated user with direct access to etcd to effectively ignore all key range restrictions, accessing the entire etcd data store. Kubernetes does not rely on etcd’s built-in authentication and authorization. Instead, the API server handles authentication and authorization itself, so typical Kubernetes deployments are not affected. Versions 3.4.42, 3.5.28, and 3.6.9 contain a patch. If upgrading is not immediately possible, reduce exposure by treating the affected RPCs as unauthenticated in practice. Restrict network access to etcd server ports so only trusted components can connect and require strong client identity at the transport layer, such as mTLS with tightly scoped client certificate distribution.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

March 26, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Jul 27, 2026
Patch available. Sources: github.
github Patch Available

Nested etcd transactions bypass RBAC authorization checks · Advisory · etcd-io/etcd · GitHub

https://github.com/etcd-io/etcd/security/advisories/GHSA-rfx7-8w68-q57q

Vendor Advisories for CVE-2026-33343(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(6 across 5 ecosystems)
Go(2)
PackageVulnerable rangeFixed inDependents
go.etcd.io/etcd———
go.etcd.io/etcd/v3—3.6.9—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
etcd3.3.25+dfsg-6 ... 3.5.5-1 (36 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
etcd3.4.23-4 ... 3.5.5-1 (30 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
etcd3.5.16-10 ... 3.5.30-2 (13 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
etcd3.5.16-10 ... 3.5.16-9 (7 versions)3.5.16-11—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 03:11 UTCEPSS rescore
  7. 2026-09-13 16:47 UTCEPSS rescore
  8. 2026-09-12 15:01 UTCEPSS rescore
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-11 09:37 UTCEPSS rescore
  11. 2026-09-10 09:34 UTCEPSS rescore
  12. 2026-09-08 22:00 UTCEPSS rescore
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-04 05:06 UTCEPSS rescore
  17. 2026-09-02 14:11 UTCEPSS rescore
  18. 2026-09-02 13:57 UTCOSV refresh
  19. 2026-09-01 13:53 UTCEPSS rescore
  20. 2026-09-01 04:39 UTCEPSS rescore
  21. 2026-09-01 04:39 UTCEPSS rescore
  22. 2026-08-30 19:17 UTCEPSS rescore
  23. 2026-08-30 01:22 UTCEPSS rescore
  24. 2026-08-28 21:41 UTCEPSS rescore
  25. 2026-08-26 14:46 UTCEPSS rescore
Show 49 more
  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-24 14:17 UTCEPSS rescore
  3. 2026-08-23 00:19 UTCEPSS rescore
  4. 2026-08-21 23:49 UTCEPSS rescore
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-20 22:55 UTCEPSS rescore
  7. 2026-08-19 17:03 UTCEPSS rescore
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 10:09 UTCEG score recompute
  12. 2026-08-16 10:09 UTCVendor advisory
  13. 2026-08-16 02:14 UTCEPSS rescore
  14. 2026-08-15 01:30 UTCEPSS rescore
  15. 2026-08-14 06:27 UTCEG score recompute
  16. 2026-08-14 06:27 UTCVendor advisory
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-12 20:44 UTCEG score recompute
  19. 2026-08-12 13:50 UTCEPSS rescore
  20. 2026-08-11 08:45 UTCEG score recompute
  21. 2026-08-11 08:45 UTCVendor advisory
  22. 2026-08-11 00:00 UTCEPSS rescore
  23. 2026-08-10 07:22 UTCEG score recompute
  24. 2026-08-09 13:46 UTCEPSS rescore
  25. 2026-08-09 06:00 UTCEG score recompute
  26. 2026-08-08 16:37 UTCEPSS rescore
  27. 2026-08-07 16:25 UTCEG score recompute
  28. 2026-08-07 16:25 UTCVendor advisory
  29. 2026-08-06 13:46 UTCEPSS rescore
  30. 2026-08-06 00:53 UTCEG score recompute
  31. 2026-08-06 00:53 UTCVendor advisory
  32. 2026-08-05 19:17 UTCEPSS rescore
  33. 2026-08-04 15:10 UTCEPSS rescore
  34. 2026-08-04 10:38 UTCEPSS rescore
  35. 2026-08-03 23:18 UTCEG score recompute
  36. 2026-08-03 23:18 UTCVendor advisory
  37. 2026-08-03 10:36 UTCEPSS rescore
  38. 2026-08-02 15:24 UTCEG score recompute
  39. 2026-08-02 15:24 UTCVendor advisory
  40. 2026-08-02 02:27 UTCEPSS rescore
  41. 2026-08-01 04:16 UTCEPSS rescore
  42. 2026-07-30 16:28 UTCEPSS rescore
  43. 2026-07-30 01:30 UTCEPSS rescore
  44. 2026-07-27 14:46 UTCEG score recompute▲ 6.50
  45. 2026-07-27 14:46 UTCVendor advisory
  46. 2026-07-27 14:13 UTCEPSS rescore
  47. 2026-07-27 12:56 UTCEG score recompute
  48. 2026-07-27 12:56 UTCVendor advisory
  49. 2026-07-27 12:50 UTCOSV refresh

Frequently asked(5)

What is CVE-2026-33343?
CVE-2026-33343 is a medium vulnerability published on March 26, 2026. etcd is a distributed key-value store for the data of a distributed system. Prior to versions 3.4.42, 3.5.28, and 3.6.9, an authenticated user with RBAC restricted permissions on key ranges can use nested transactions to bypass all key-level authorization. This allows any authenticated user with…
When was CVE-2026-33343 disclosed?
CVE-2026-33343 was first published in the National Vulnerability Database on March 26, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33343 actively exploited?
CVE-2026-33343 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 88.4% of all scored CVEs.
What is the CVSS score of CVE-2026-33343?
CVE-2026-33343 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-33343?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33343, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33343

Explore →

Is Your Infrastructure Affected by CVE-2026-33343?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs