CVE-2026-67208
Unauthenticated RCE via exposed H2 web console with default creds in Juggle through 1.6.0
Is CVE-2026-67208 being exploited?
Not confirmed. CVE-2026-67208 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 5.3% probability of exploitation in the next 30 days.
How severe is CVE-2026-67208?
CVE-2026-67208 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-67208?
Not known from our data. No patch reference has been recorded for CVE-2026-67208, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-67208 affect?
CVE-2026-67208 affects Juggle through 1.6.0, H2 Database web console (/h2-console), Stock Juggle Docker image. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67208?
Disable or remove H2 console, change default creds, restrict access, and apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attackers can access /h2-console with default creds and run OS commands (Runtime.exec), achieving root on stock Docker images.
Immediate action required
- affected<= 1.6.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.