Summary
CVE-2026-88391 is a critical, unauthenticated remote code execution vulnerability in Dromara Northstar, an open-source Java-based quantitative trading platform, affecting all versions up to and including 9.1.1. The flaw stems from an exposed and unauthenticated H2 database console that allows a network-reachable attacker to execute arbitrary operating system commands without any credentials. The issue has been assigned a CVSS v3.1 base score of 9.8 (Critical).
Technical details
- Root cause: Northstar ships with the embedded H2 database console enabled, but the application’s authentication interceptor is scoped only to
/northstar/**paths, leaving the/h2-consoleendpoint completely unprotected. - Trigger conditions: The embedded H2 database uses the default
saaccount with an empty password, so no credential guessing or bypass is required to authenticate to the console itself. - Attack vector: An attacker sends unauthenticated HTTP requests to
/h2-console/to obtain a session, authenticates to the H2 console via/h2-console/login.dousing the defaultsa/blank-password credentials, then submits a SQLCREATE ALIASstatement via/h2-console/query.dothat wrapsRuntime.getRuntime().exec(), creating a callable function for arbitrary command execution. - Impact: Once the alias is created, the attacker can invoke it (e.g.,
CALL SHELLEXEC('whoami')) to run arbitrary system commands with the privileges of the application process, resulting in full remote code execution with no authentication or user interaction required (CWE-94: Improper Control of Generation of Code / Code Injection).
Affected software
- Dromara Northstar (dromara/northstar) — all versions up to and including 9.1.1
Severity
- CVSS v3.1 Base Score: 9.8 (Critical)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: No official vendor-released patched version has been confirmed publicly at this time. Organizations running Northstar ≤ 9.1.1 should monitor the Dromara northstar GitHub repository for an updated release that remediates this issue and apply it as soon as it becomes available.
- If no patch is available:
- Disable the H2 console entirely in the application configuration if it is not required for operation.
- Restrict network access to
/h2-console(and ideally the entire management/admin interface) using firewall rules, reverse proxy ACLs, or VPN-only access so it is not reachable from the public internet. - Change default H2 database credentials away from
sa/empty password if the console must remain enabled. - Place the application behind a web application firewall capable of blocking requests to
/h2-console/*paths from untrusted sources.

