Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Checkout DevGuardView on GitHub
Search

GHSA-w7j5-j98m-w679

HighCVSS 8.4 / 10
Published Mar 3, 2026·Last modified Mar 4, 2026
Affected Components(0)

No affected components available

Description

Three Dockerfiles in scripts/docker/ and scripts/e2e/ lack a USER directive, meaning all processes run as uid 0 (root). If any process is compromised, the attacker has root inside the container, making container breakout significantly easier. Partial fix (2026-02-08): Commit 28e1a65e added USER sandbox to Dockerfile.sandbox and Dockerfile.sandbox-browser. The E2E/test Dockerfiles listed below remain unpatched.

Affected components:

  • scripts/e2e/Dockerfile
  • scripts/e2e/Dockerfile.qr-import
  • scripts/docker/install-sh-e2e/Dockerfile
  • scripts/docker/install-sh-nonroot/Dockerfile (runs as app but with NOPASSWD sudo — see related advisory)

Technical Reproduction:

  1. Open each Dockerfile listed above and search for a USER directive — none found.
  2. Run any of these containers: docker run --rm -it <image> id
  3. Observe: returns uid=0(root).

Demonstrated Impact:

  • Root inside the container enables kernel exploit attempts, volume mount abuse, and privileged syscall access.
  • Test images share the same base (node:22-bookworm) as production, creating risk of accidental deployment of root-running images.

Environment: Base images node:22-bookworm and node:22-bookworm-slim default to root. Dockerfile.sandbox and Dockerfile.sandbox-browser were remediated in commit 28e1a65e; only the E2E/test images listed above remain affected.

Remediation: Add a USER directive before CMD/ENTRYPOINT in each remaining Dockerfile: RUN useradd --create-home --shell /bin/bash appuser USER appuser

Risk Scores
Base Score
8.4

The vulnerability requires local access to the device to be exploited. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability.

Threat Intelligence
5.7

Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.

EPSS
N/A

Probability that this vulnerability will be exploited in the wild within the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Browse More

High severity
Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard