Repository navigation
Security alert: Please update Node.js to address the October 2026 vulnerabilities #488
jhuckaby
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Security alert: Please update Node.js to address the October 2026 vulnerabilities
Hi everyone! Please plan to update Node.js on your xyOps servers as soon as possible. The October 2026 security releases address several vulnerabilities, including a Brotli decompression flaw that can lead to remote code execution.
The xyOps v1.1.11 Docker image includes Node.js v24.22.1, the latest Node.js v24 release as of October 25, 2026, with all of these Node.js security fixes applicable to v24 included. See the xyOps v1.1.11 release.
Which Node.js versions should I install?
Update to the following patched version, or a newer release in the same supported release line:
If you are running an end-of-life version, move to a supported release line. See the official Node.js security announcement for release details and downloads.
What was fixed?
The Node.js advisory states:
Highlights include:
See the Node.js advisory for the complete list.
Brotli exposure extends beyond Node.js
Aikido's write-up on CVE-2026-111497, also called Node2Shell or HTTP2Shell, explains that other software bundling the vulnerable Brotli decoder is affected too. HTTP clients can encounter the flaw when decoding malicious compressed responses, so exposure is not limited to public-facing servers.
If your jobs use Python, check their environments for the Brotli and brotlicffi packages. The patched versions are Brotli 1.2.1 and brotlicffi 1.2.1.0, or later. These packages can be installed indirectly through other dependencies.
What should xyOps users do?
Warning
The xyOps conductor's self-upgrade mechanism only updates the xyOps software itself. It does not upgrade Node.js. Self-upgrading to xyOps v1.1.11 alone will not apply these Node.js security fixes. This update requires special care: upgrade Node.js separately for native installations, or deploy the updated Docker image as described below.
You can check a Node.js installation with:
For Docker, check inside the running container:
For native services, verify the Node.js executable actually used by the service, since your interactive shell may select a different installation.
Please prioritize these updates and confirm that your running services are using the patched versions. Thanks everyone!
All reactions