Memcached 1.6
Memcached 1.6
Third-party support for the Memcached 1.6: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance — independent of the vendor contract.
24/7 engineers own your Memcached 1.6 incidents end to end.
Mitigation and patch-around guidance when the vendor no longer ships fixes.
Controls evidence and documentation that keep auditors satisfied.
Specifications
- product
- memcached
- release
- 1.6
- product Label
- Memcached
- release Label
- 1.6
- codename
- lts
- latest Version
- 1.6.45
- release Date
- 2020-03-08
- maintained
- true
- source Url
- https://endoflife.date/memcached
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Memcached 1.6 — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| Break/Fix Support | Until EOSL | |
| 24/7 Monitoring | ||
| Vulnerability Scanning & Remediation | ||
| Managed Operations | ||
| Procedure & Configuration Review | ||
| Compliance & Audit Documentation | Limited | |
| Discounted Migration to Other Platforms |
Why Choose 3rd Party Support for Memcached 1.6?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Memcached 1.6 when the vendor no longer ships fixes.
Compliance Maintenance
Procedure review, controls evidence and the documentation auditors ask for — maintained continuously, not scrambled at audit time.
24/7 Expert Support
Engineers who know this release monitor, manage and fix issues around the clock — break/fix to managed operations.
Memcached 1.6 Support: Frequently Asked Questions
Is the Memcached 1.6 still supported?
Yes. The Memcached 1.6 is currently supported by Memcached, and third-party support is available as an alternative — issue management, vulnerability remediation, and compliance help independent of the vendor contract.
How much does third-party support for the Memcached 1.6 cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location — request a quote and we respond within 24 hours.
Known Vulnerabilities Affecting Memcached 1.6
8 published CVEs affect the Memcached 1.6, including 7 rated critical or high severity. Our 24/7 engineers help you assess exposure, prioritize fixes and apply available patches.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2023-46853 | CRITICAL | 9.8 | Oct 27, 2023 | In Memcached before 1.6.22, an off-by-one error exists when processing proxy requests in proxy mode, if \n is used instead of \r\n. |
| CVE-2026-47784 | HIGH | 8.1 | 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 sasl_server_userdb_checkpass. |
| CVE-2026-47783 | HIGH | 8.1 | 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 sasl_server_userdb_checkpass. |
| CVE-2023-46852 | HIGH | 7.5 | Oct 27, 2023 | In Memcached before 1.6.22, a buffer overflow exists when processing multiget requests in proxy mode, if there are many spaces after the "get" substring. |
| CVE-2022-48571 | HIGH | 7.5 | Aug 22, 2023 | memcached 1.6.7 allows a Denial of Service via multi-packet uploads in UDP. |
| CVE-2020-22570 | HIGH | 7.5 | Aug 22, 2023 | Memcached 1.6.0 before 1.6.3 allows remote attackers to cause a denial of service (daemon crash) via a crafted meta command. |
| CVE-2020-10931 | HIGH | 7.5 | Mar 24, 2020 | Memcached 1.6.x before 1.6.2 allows remote attackers to cause a denial of service (daemon crash) via a crafted binary protocol header to try_read_command_binary in memcached.c. |
| CVE-2021-37519 | MEDIUM | 5.5 | Feb 3, 2023 | Buffer Overflow vulnerability in authfile.c memcached 1.6.9 allows attackers to cause a denial of service via crafted authenticattion file. |