CVE-2026-47783

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
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.3%CVSS: 8.1Exploit: None knownExposed services: Not assessed

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.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100

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%
EPSS PROB
1.3%
EPSS %ILE
68th
KEV
Not listed

Published

May 20, 2026

Last Modified

September 18, 2026

Advisory Details (3)

Auto-updated May 20, 2026
Patch available.
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

Vendor Advisories for CVE-2026-47783(4)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntumemcached (1.6.38-1ubuntu0.1) @ questing2026-09-18ubuntu
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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
memcached1.6.9+dfsg-1
  • every version up to 1.6.9+dfsg-1+deb11u1: fixed in 1.6.9+dfsg-1+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
memcached1.6.18-1
  • every version up to 1.6.18-1+deb12u1: fixed in 1.6.18-1+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
memcached1.6.38-1 ... 1.6.45-1 (8 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
memcached1.6.38-1 ... 1.6.41-2 (6 versions)
  • every version up to 1.6.42-1: fixed in 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 8× in last 7d / 28× 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 307 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Same vendor

1 shown

ubuntu:USN-8320-1

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 on May 20, 2026, with the most recent update on September 18, 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 1.3% probability of exploitation in the next 30 days (68th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47783?
CVE-2026-47783 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-47783?
A fix for CVE-2026-47783 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-47783 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs