critical

CVE

CVE-2026-109518, CVE-2026-123158

CWE

CWE-367, CWE-494, CWE-287, CWE-506

Affected Surface

  • Debian and Ubuntu hosts, CI runners, and base container images that still run vulnerable `apt` builds with retries and HTTP resume enabled
  • Alpine and other `musl` Linux systems running vulnerable OpenSSH builds without PAM, especially hosts that expose password authentication for accounts with `*` in `/etc/shadow`
  • Developer workstations, Swarm Desktop users, and npm consumers that pulled `@ethersphere/bee-js@13.3.0` or Swarm Desktop `0.56.2` during the compromise window

Welcome to Corgea’s weekly briefing. The briefing covers the most important security findings and research from the week.

This edition covers research published from Wednesday, 4 November through Tuesday, 10 November 2026, following the prior 3 November briefing. No interim weekly briefing landed between those Tuesday editions, so the 54 research posts below are all new to this roundup.

Top Article

Max Justicz deserves the discovery credit here, and Julian Andres Klode plus the Debian and Canonical maintainers deserve credit for getting a fix out quickly. This sits at the top because it breaks a trust boundary that a lot of teams barely notice anymore: APT can verify the package hash, hand the file off to dpkg, and still lose the race if redirects, retries, and hard links line up the wrong way. The impact is bigger than one package manager bug. It reaches developer laptops, CI runners, Docker builds, and base images that still fetch over plain HTTP or through a proxy. Keep it next to Corgea’s coverage of WordPress Core’s upgrade-directory race in KEV, Dulwich’s Windows checkout and format_patch path traversals, and the broader OpenSSH, apt, musl, and zlib distro patch stack.

More news

CVE-2026-123158 (*sshole): OpenSSH < 10.6p2 password authentication bypass on musl Linux exploited in the wild within nine hours, plus musl regcomp() heap overflow CVE-2026-107891

Özgün Kültekin of Wakefield deserves the discovery credit, and Previdian deserves the first public exploitation telemetry. The bug only needed the right Alpine-style conditions to turn an odd musl failure path into unauthenticated root access. That is exactly what happened. Public exploitation started within hours, and the affected pattern shows up on real servers, containers, and cloud images. Read it with the distro-level follow-ups on OpenSSH, apt, musl, zlib, and UnrealIRCd, the zlib and CPython Jinja2 sandbox escape chain, and Canonical LXD and Incus’s mTLS bypass.

@ethersphere/bee-js 13.3.0 and swarm-desktop 0.56.2 hijacked via bee-worker to steal Swarm wallet keys and deploy evjawbreaker over an Ethereum C2 dead drop

Socket Threat Research, StepSecurity, SafeDep, OX Security, and Bitbison deserve the public teardown credit, while Ethersphere deserves credit for shipping the clean 0.56.3 recovery release. This story matters because the attacker did not need a typo package or a fake maintainer profile. They used the project’s own release identities and trusted-publishing path to push a malicious npm release with valid provenance, then pivoted into wallet-key theft and persistent remote access. It belongs in the same reading stack as the fake-interview Tailwind and Animate.css plugins, the testmetest and @iobandamwer/* npm worm, the dynamic-mcp and labelearthengine-api package wave, and PolinRider’s cross-ecosystem expansion.

Other news:

From research to remediation

Check whether this pattern exists in your codebase

Turn this research into a remediation workflow. Scan dependencies and package manifests for similar supply-chain risk, then prioritize fixes with reachability context.

References