Runtime inventory
Review agreed hosts, images, background workers and build tools. Identify instances, owners and required changes.
Services
We review your application runtime, Brotli data processing and update compatibility. The agreed delivery includes a change plan, configuration backup, rollback procedure, runtime update and functional checks. You receive a record of completed work and remaining recommendations.
We assess Node2Shell exposure and deploy Node.js updates, checking the runtime used by your running application. We select the scope, technology, and engagement model around your current environment, risk profile, and business objective.
Before work begins, we define the outcome, responsibilities, acceptance criteria, and how results will be measured.
We inspect the deployed environment, not just the repository configuration.
Review agreed hosts, images, background workers and build tools. Identify instances, owners and required changes.
Review compressed requests and responses fetched from external services. Identify where untrusted data enters decompression paths.
Agree update order, compatibility checks and a deployment window. Separate verified findings from areas requiring additional access.
Updating application dependencies does not replace updating the Node.js runtime.
Verify Node.js 22.23.4, 24.22.1 or 26.12.1, or a later release containing the CVE-2026-111497 fix. Choose the target line based on support and compatibility.
Rebuild agreed images and redeploy services. Confirm the version of processes serving traffic and ensure subsequent deployments preserve the update.
Check agreed APIs, authentication, jobs and integrations. Review service health and logs, then record the outcome. Suspected prior compromise needs separate investigation.
Interim changes depend on the application’s data paths and infrastructure.
Where immediate updating is not possible, assess limiting untrusted Brotli input. WAF rules and filtering do not replace the patch and may not cover outbound responses.
Assess migration, dependencies and test scope for unsupported runtimes. Agree compatibility work before production changes.
Deliver an instance inventory, change record and follow-up actions. Monitoring and recurring updates can be scoped separately.
Audit and remediation scoped to your environment
Individual quote
Inventory, exposure assessment and a remediation plan.
Individual quote
Runtime updates, image rebuilds, process replacement and agreed checks.
Individual quote
Legacy compatibility work and separately agreed ongoing support.
Price and timing depend on instance count, infrastructure access and application compatibility. Incident response and compromise recovery require a separate scope. Updating alone does not guarantee complete system security.
ContactWe understand the system, business process, constraints, and success metrics.
We define architecture, scope, risks, timeline, and a safe release approach.
We work iteratively, demonstrate progress, and test against real scenarios.
We release the solution, hand over documentation, and support continued development.
Neither replaces checking and updating Node.js. Dependency review is useful, but the running runtime must contain the decoder fix.
No. It may limit some incoming traffic, but does not replace the patch and may not cover data fetched from other services.
Yes. We verify that running instances are replaced and check the runtime actually serving the application.
The standard scope covers version and configuration review plus agreed functional checks. Offensive testing requires a separate scope and authorization.
Node.js: Security releases — 21 October 2026
Last updated: 23 October 2026
Briefly describe your goal or problem. You do not need a complete specification. This is a no-obligation enquiry.
Describe your project