CVE
CVE-2026-103251, CVE-2026-104859
CWE
CWE-862, CWE-78
Affected Surface
- Self-hosted n8n deployments that use Redis-backed queue mode with community packages enabled and broader-than-intended Redis write access
- Nx release pipelines running vulnerable `@nx/docker` versions when pull requests, workspace configuration, CLI flags, or environment variables can shape image references before publish
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, 30 September through Tuesday, 6 October 2026, excluding items already covered in the 29 September briefing and the interim 5 October briefing. After that interim edition pulled in the @nx/docker disclosure, one uncovered English-language Corgea research article remains in scope for this Tuesday handoff.
Top Article
CVE-2026-103251: n8n queue mode lets Redis pub-sub install arbitrary npm packages cluster-wide
Ayush Parkara deserves the public reporting credit for CVE-2026-103251, and it leads this Tuesday edition because it broke the trust boundary that decides what code an automation cluster is allowed to load. n8n already had a checked install path for community packages. Queue mode added a Redis pub-sub path that skipped those checks and treated a bus message as authority to install a package everywhere. If an attacker could write to that Redis channel, every connected node could fetch and load an attacker-chosen npm package without the usual banned-package, checksum, or approval checks.
Read it beside Corgea’s research on Graphalgo’s Terraform and Go-module spread, MemTensor’s OpenClaw and MemoryOS compromise, the npm mirror phishing-host campaign, and @7nohe/openapi-react-query-codegen. The common thread is simple: package risk often appears in the control planes that decide what other machines should trust, not only in the registry client itself.
More news
No additional uncovered English-language Corgea research articles remain in the Wednesday, 30 September through Tuesday, 6 October window after the interim 5 October briefing already summarized the @nx/docker release-pipeline bug.
Other news:
- CVE-2026-104859:
@nx/dockerturned release configuration into/bin/sh -cwas already covered in the 5 October briefing. Arkadiusz Marta of RE:SOURCE deserves the reporting credit. It is still worth reading if your CI jobs accept changes tonx.json,project.json, orNX_DOCKER_IMAGE_REF, because the vulnerable path reached a shell even on dry-run publish steps. - For more cluster-control-plane context, compare the n8n bug with Corgea’s research on Gitea and Forgejo’s private container registry bypass, Ray dashboard DNS rebinding RCE, and Oracle WebLogic’s T3/IIOP KEV exposure.
- For more package-install and CI trust failures, revisit Graphalgo, MemTensor, and the
actions-coolMini Shai-Hulud reactivation.
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.