CVE-2026-44283

UNRATEDCVSS · not yet scored
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: Exploit: 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 3.4.44, 3.5.30, and 3.6.11, a vulnerability in etcd allows read access via PrevKv, or lease attachment in Put requests within transaction operations, to bypass RBAC authorization checks. An authenticated user without sufficient read or lease-related permissions may be able to access unauthorized data or attach leases by invoking transaction operations with these features enabled. This vulnerability is fixed in 3.4.44, 3.5.30, and 3.6.11.

CVSS v3
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
EG Risk
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

May 14, 2026

Last Modified

May 15, 2026

Vendor Advisories for CVE-2026-44283(1)

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

Affected Packages

(7 across 5 ecosystems)
Go(3)
PackageVulnerable rangeFixed inDependents
go.etcd.io/etcd3.4.44
go.etcd.io/etcd/server/v33.6.11
go.etcd.io/etcd/v33.5.30
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 5× in last 7d / 27× 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.

Showing the most recent 100 of 131 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-08-30 19:17 UTCEPSS rescore
  5. 2026-08-30 01:22 UTCEPSS rescore
  6. 2026-08-28 21:41 UTCEPSS rescore
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-23 00:19 UTCEPSS rescore
  11. 2026-08-21 23:49 UTCEPSS rescore
  12. 2026-08-20 22:55 UTCEPSS rescore
  13. 2026-08-20 19:36 UTCVendor advisory
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 03:56 UTCVendor advisory
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-12 13:51 UTCEPSS rescore
  22. 2026-08-11 13:43 UTCEPSS rescore
  23. 2026-08-11 00:00 UTCEPSS rescore
  24. 2026-08-09 13:46 UTCEPSS rescore
  25. 2026-08-09 03:54 UTCVendor advisory
Show 75 more
  1. 2026-08-08 16:37 UTCEPSS rescore
  2. 2026-08-06 13:46 UTCEPSS rescore
  3. 2026-08-05 21:36 UTCVendor advisory
  4. 2026-08-05 19:17 UTCEPSS rescore
  5. 2026-08-04 15:10 UTCEPSS rescore
  6. 2026-08-04 10:38 UTCEPSS rescore
  7. 2026-08-03 10:36 UTCEPSS rescore
  8. 2026-08-02 02:27 UTCEPSS rescore
  9. 2026-08-01 19:20 UTCEG score recompute
  10. 2026-08-01 19:20 UTCVendor advisory
  11. 2026-07-30 16:28 UTCEPSS rescore
  12. 2026-07-30 01:30 UTCEPSS rescore
  13. 2026-07-28 15:36 UTCEPSS rescore
  14. 2026-07-27 14:13 UTCEPSS rescore
  15. 2026-07-26 14:54 UTCEPSS rescore
  16. 2026-07-26 14:54 UTCEPSS rescore
  17. 2026-07-25 14:18 UTCEPSS rescore
  18. 2026-07-24 14:17 UTCEPSS rescore
  19. 2026-07-23 14:18 UTCEPSS rescore
  20. 2026-07-23 03:15 UTCEG score recompute
  21. 2026-07-22 14:08 UTCEPSS rescore
  22. 2026-07-21 15:24 UTCEPSS rescore
  23. 2026-07-20 17:08 UTCEPSS rescore
  24. 2026-07-19 14:31 UTCEPSS rescore
  25. 2026-07-19 02:29 UTCEPSS rescore
  26. 2026-07-18 10:04 UTCEPSS rescore
  27. 2026-07-18 01:29 UTCOSV refresh
  28. 2026-07-16 17:03 UTCEPSS rescore
  29. 2026-07-15 16:57 UTCEPSS rescore
  30. 2026-07-15 02:00 UTCEPSS rescore
  31. 2026-07-13 22:30 UTCEPSS rescore
  32. 2026-07-13 06:13 UTCEPSS rescore
  33. 2026-07-12 05:46 UTCEPSS rescore
  34. 2026-07-11 08:27 UTCEPSS rescore
  35. 2026-07-09 19:10 UTCEPSS rescore
  36. 2026-07-08 15:16 UTCEPSS rescore
  37. 2026-07-07 13:46 UTCEPSS rescore
  38. 2026-07-06 16:27 UTCEPSS rescore
  39. 2026-07-06 02:23 UTCEPSS rescore
  40. 2026-07-05 02:30 UTCEPSS rescore
  41. 2026-07-04 06:31 UTCEPSS rescore
  42. 2026-07-01 15:07 UTCEPSS rescore
  43. 2026-06-30 23:22 UTCEPSS rescore
  44. 2026-06-29 21:51 UTCVendor advisory
  45. 2026-06-29 14:06 UTCEPSS rescore
  46. 2026-06-28 14:07 UTCEPSS rescore
  47. 2026-06-28 04:56 UTCEPSS rescore
  48. 2026-06-27 03:08 UTCEPSS rescore
  49. 2026-06-25 19:14 UTCVendor advisory
  50. 2026-06-25 13:49 UTCEPSS rescore
  51. 2026-06-25 13:49 UTCEPSS rescore
  52. 2026-06-24 14:05 UTCEPSS rescore
  53. 2026-06-23 21:33 UTCEPSS rescore
  54. 2026-06-22 14:25 UTCEPSS rescore
  55. 2026-06-22 14:25 UTCEPSS rescore
  56. 2026-06-21 14:56 UTCEPSS rescore
  57. 2026-06-21 14:56 UTCEPSS rescore
  58. 2026-06-21 01:59 UTCEPSS rescore
  59. 2026-06-19 19:25 UTCEPSS rescore
  60. 2026-06-18 17:52 UTCEPSS rescore
  61. 2026-06-18 17:52 UTCEPSS rescore
  62. 2026-06-17 17:53 UTCEPSS rescore
  63. 2026-06-16 17:52 UTCEPSS rescore
  64. 2026-06-15 17:49 UTCEPSS rescore
  65. 2026-06-14 07:00 UTCVendor advisory
  66. 2026-06-13 23:00 UTCEPSS rescore
  67. 2026-06-12 23:12 UTCEPSS rescore
  68. 2026-06-12 23:12 UTCEPSS rescore
  69. 2026-06-11 14:00 UTCEPSS rescore
  70. 2026-06-11 00:41 UTCVendor advisory
  71. 2026-06-10 22:18 UTCEPSS rescore
  72. 2026-06-10 13:22 UTCEPSS rescore
  73. 2026-06-10 13:22 UTCEPSS rescore
  74. 2026-06-08 14:17 UTCEPSS rescore
  75. 2026-06-08 14:17 UTCEPSS rescore

Frequently asked(4)

What is CVE-2026-44283?
CVE-2026-44283 is a publicly disclosed vulnerability published on May 14, 2026. etcd is a distributed key-value store for the data of a distributed system. Prior to 3.4.44, 3.5.30, and 3.6.11, a vulnerability in etcd allows read access via PrevKv, or lease attachment in Put requests within transaction operations, to bypass RBAC authorization checks. An authenticated user…
When was CVE-2026-44283 disclosed?
CVE-2026-44283 was first published in the National Vulnerability Database on May 14, 2026, with the most recent update on May 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44283 actively exploited?
CVE-2026-44283 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 87.0% of all scored CVEs.
How do I remediate CVE-2026-44283?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44283, 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-44283

Explore →

Is Your Infrastructure Affected by CVE-2026-44283?

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