# CVE-2026-67208: Juggle 1.6.0 Unauthenticated RCE via Exposed H2 Console

> Unauthenticated attackers can execute arbitrary OS commands via the exposed H2 console using default credentials, leading to root-level code execution.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-8rhq-39vx-cjqx

## What is CVE-2026-67208?

CVE-2026-67208 is a critical vulnerability in somta Juggle, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Juggle through 1.6.0 contains a remote code execution vulnerability that allows unauthenticated remote attackers to execute arbitrary OS commands by connecting to the exposed H2 database web console using default shipped credentials. Attackers can access the unprotected /h2-console endpoint, authenticate with default credentials, and leverage the H2 CREATE ALIAS Runtime.exec() technique to execute arbitrary commands, resulting in root-level code execution when running the stock Docker image.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-1188 (Initialization of a Resource with an Insecure Default)

## Which versions are affected by CVE-2026-67208?


## How do I fix CVE-2026-67208?

No fix has been published for CVE-2026-67208 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-67208 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67208 exists.

Public exploit code:

- Juggle <= 1.6.0 - Unauthenticated Exposed H2 Database Console (nuclei): http/cves/2026/CVE-2026-67208.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-67208 and fix it if it is affected.

What it is: CVE-2026-67208 is a critical vulnerability in somta Juggle, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67208 exists.

Affected product: somta Juggle. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-67208/ (Markdown: https://insights.sbomify.com/CVE-2026-67208/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-67208
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-67208
- OSV: https://osv.dev/vulnerability/CVE-2026-67208

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-67208/
Summaries are generated and may contain mistakes; the official description above is the record.