NPM · SEPTEMBER 2026 · EARLY WARNING

submariner npm Package Vulnerability: Critical CVE-2026-66786 Alert

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.
Severity
CRITICAL
CVSS
9.1
Affected component
submariner (npm)
Patched version
Not yet available
CVE-2026-66786

A critical flaw has been reportedly found in the submariner npm package. This vulnerability could allow remote code execution as root on the gateway node.

What happened

An early warning has been issued for a critical flaw in the submariner npm package. In cert-auth mode, the connection configuration is built using free-form strings from the Custom Resource Definition (CRD) without proper validation. A malicious cluster can exploit this by publishing a CableName that includes newlines and ipsec.conf directives. This allows an attacker to inject arbitrary configuration parameters or execute commands through leftupdown hooks, leading to remote code execution as root on the gateway node.

The vulnerability, tracked as CVE-2026-66786, has a CVSS score of 9.1 and is classified as critical. It is under investigation and has not been exploited in the wild as of the latest reports. The flaw is specific to the submariner package and affects an unknown version range. No authoritative version range has been published yet.

What to do about it

How 0Day would have caught this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If submariner is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Frequently asked questions

Am I affected?

If you are using the submariner npm package in your projects, you may be affected. The exact version range is not yet known, so it is advisable to monitor updates closely.

What should I do right now?

Monitor the primary sources for updates on a fixed version of submariner. Rotate any secrets in affected environments as a precautionary measure.

Is there a patched version available?

No official fix has been published yet. Continue to monitor the primary sources for updates.

How severe is this vulnerability?

The vulnerability is classified as critical with a CVSS score of 9.1. It has the potential for remote code execution as root on the gateway node.

Sources

Join the 0Day waitlist →

← Back to all threats