CVE-2026-47784

HIGHNVD 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
Trending — 4 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.1Exploit: None knownExposed: 0

A fix is available — apply it.

In memcached before 1.6.42, password data for SASL password database authentication has a timing side channel because memcmp is used by sasl_server_userdb_checkpass.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity81% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

May 20, 2026

Last Modified

July 24, 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(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntumemcached (1.6.14-1ubuntu0.2) @ jammy2026-08-23ubuntu
redhatmemcached-main-1.6.42-0.1.hum12026-06-04redhat

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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
memcached1.6.9+dfsg-11.6.9+dfsg-1+deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
memcached1.6.18-1 ... 1.6.45-1 (29 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
memcached1.6.38-1 ... 1.6.45-1 (8 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
memcached1.6.38-1 ... 1.6.41-2 (6 versions)1.6.42-1

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

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 14× in last 7d / 95× 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 264 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-47784?
CVE-2026-47784 is a high vulnerability published on May 20, 2026. In memcached before 1.6.42, password data for SASL password database authentication has a timing side channel because memcmp is used by saslserveruserdb_checkpass.
When was CVE-2026-47784 disclosed?
CVE-2026-47784 was first published in the National Vulnerability Database on May 20, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47784 actively exploited?
CVE-2026-47784 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.5% of all scored CVEs.
What is the CVSS score of CVE-2026-47784?
CVE-2026-47784 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-47784?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47784, 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-47784

Explore →

Is Your Infrastructure Affected by CVE-2026-47784?

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