memcached · GitHub

Memcached 1.6.45 Release Notes

Date: 2026-7-9

Download

http://www.memcached.org/files/memcached-1.6.45.tar.gz

Overview

I apologize for the three releases in a row. I'm trying to find every bug possible in hopes of slowing down the deluge of security reports.

So this is a lot of crash and security bugs. If you decide to deploy this please be cautious; use a canary server and let it bake, just in case.

Tired.

Fixes

  • proxy: extra warning for user config error
  • proto: convert more strto calls
  • proto: meta preparse F flag fix
  • proxy: fix res:line() returning wrong response
  • proxy: fix overread of spaces for large gets
  • ascii: safely convert flag args to numerics
  • ascii: fix unlocked refcount-- on error path
  • proxy: key filter null byte written to wrong place
  • proxy: fix detail len clamp in request logging
  • proxy: enforce minimum rate limit
  • ascii: fix refcount leak on ms parse error
  • proxy: reserve enough log space for proxy BE_EVENT
  • network: fix segfault on OOM during net read
  • proxy: fix missing default handler in resnull
  • stats: cap stats prefix count at 2^16
  • binprot: GETK against extstore internal miss can hang worker
  • proxy: fix memory leak after failed request render
  • proxy: fix underflow in key hash filters
  • logger: closed worker fix again
  • ascii: fix crash with invalid automove windows
  • proxy: fix footgun when excessive backend labels
  • slabs: fix off by one in slab picker loop
  • ascii: fix potential overrun when given all spaces
  • proxy: fix mutator crash in flagcopyall
  • restart: avoid runaway read with corrupt file
  • proxy: fix ring hash default mode
  • tls: uninitialized string can be used in error
  • proxy: fix off by one in request_append
  • logger: fix use-after-free of closed watcher

New Features

None

Contributors

The following people contributed to this release since 1.6.44.

Note that this is based on who contributed changes, not how they were done. In many cases, a code snippet on the mailing list or a bug report ended up as a commit with your name on it.

Note that this is just a summary of how many changes each person made which doesn't necessarily reflect how significant each change was. For details on what led up into a branch, either grab the git repo and look at the output of git log 1.6.44..1.6.45 or use a web view.

    33	dormando

Read the original on github.com ↗