mirror of
https://github.com/wekan/wekan.git
synced 2026-11-20 15:45:01 -05:00
CVE-2026-98432 is a Linux kernel use-after-free in IPv4 TCP connection handling, shown to give remote code execution through an MPTCP listener (golang-announce, 2026-10). Since Go 1.24 every Linux listen socket of a Go program is MPTCP by default, and WeKan ships two Go servers: Caddy, the snap's web server on ports 80 and 443, and FerretDB, the default database. Every place WeKan starts one sets GODEBUG=multipathtcp=0: the snap's environment (every app, Caddy and FerretDB among them), the Docker entrypoint and the bundle launcher - which keep an operator's own multipathtcp setting - every docker-compose FerretDB service (the commented FerretDB 2 example too), and the FerretDB the Sandstorm grain starts. Caddy is an upstream binary, so no rebuild is needed: Go reads GODEBUG at start. wekan/FerretDB builds with `godebug multipathtcp=0` as well. The real fix is a patched host kernel. Checked on Linux: a Go server's default listener reports MPTCP true; GODEBUG=multipathtcp=0, or the go.mod setting, makes it false. tests/goMptcpOff.test.cjs pins every launcher, runs the launcher line, and fails when something turns MPTCP back on. Thanks to xet7 !