CVE-2026-47783

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-05-20. NVD baseline CVSS 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.1Exploit: NoneExposed: 0

A fix is available — apply it.

In memcached before 1.6.42, username data for SASL password database authentication has a timing side channel because a loop exits as soon as a valid username is found by sasl_server_userdb_checkpass.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
EPSS
67.7%
KEV
Not listed

Published

May 20, 2026

Last Modified

July 15, 2026

Advisory Details (3)

Auto-updated May 20, 2026
No patch confirmed yet.
generic

ReleaseNotes1642 · memcached/memcached Wiki · GitHub

https://github.com/memcached/memcached/wiki/ReleaseNotes1642
generic

Comparing 1.6.41...1.6.42 · memcached/memcached · GitHub

https://github.com/memcached/memcached/compare/1.6.41...1.6.42
generic

Fix timing side-channel in SASL password database authentication · memcached/memcached@d13f282 · GitHub

https://github.com/memcached/memcached/commit/d13f282b4bce33a9c33b8a1bbf07f12114160fed

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntumemcached (1.6.38-1ubuntu0.1) @ questing2026-06-29ubuntu
redhatmemcached-0:1.6.23-7.el10_2.12026-06-22redhat
redhatmemcached-0:1.6.9-7.el9_8.12026-06-22redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 45× 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 157 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-47783?
CVE-2026-47783 is a high vulnerability published on May 20, 2026. In memcached before 1.6.42, username data for SASL password database authentication has a timing side channel because a loop exits as soon as a valid username is found by saslserveruserdb_checkpass.
When was CVE-2026-47783 disclosed?
CVE-2026-47783 was first published in the National Vulnerability Database on May 20, 2026, with the most recent update on July 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-47783 actively exploited?
CVE-2026-47783 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 67.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-47783?
CVE-2026-47783 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-47783?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47783, 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

Explore the affected products and dependency analysis for CVE-2026-47783

Explore →

Is Your Infrastructure Affected by CVE-2026-47783?

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