External risk intelligence

9Router Unauthenticated Database Export and Import Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-55500

The vulnerability resides in an API endpoint of a router/gateway application. Such products are commonly deployed as network edge services or management interfaces, making the API surface readily reachable from the network or potentially the public internet in typical deployment patterns.

Information Disclosure

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

The 9Router AI router has a critical vulnerability in its database settings endpoint that allows unauthorized access to export or import the entire database, which includes sensitive credentials and tokens. This issue affects versions prior to 0.4.80 and has been addressed in version 0.4.80.

Unauthenticated access to sensitive router data.
Potential for complete system compromise and data theft.
Verify if this AI router is deployed in your environment.

Attack Path

How an attacker could exploit the issue

An attacker with low-privileged access could interact with the `/api/settings/database` endpoint to export sensitive information or import malicious data, potentially leading to a complete system compromise. The vulnerability exists because the endpoint's protection relies solely on a token check rather than a robust authentication and authorization mechanism.

Requires low-privileged access.
Triggered by API endpoint access.
Leads to full system compromise.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker to export the entire database, potentially exposing sensitive credentials, API keys, and OAuth tokens, or to import a malicious database, overwriting existing configurations. This impacts systems where the /api/settings/database endpoint is accessible.

Sensitive credentials and keys at risk.
Unauthenticated access to API endpoint.
Complete system configuration compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

Given that 9Router is an AI router, the platform or infrastructure team responsible for managing network services and the application owner are likely accountable for addressing this vulnerability. The immediate practical first step is to inventory all instances of 9Router, determine their network exposure, confirm business criticality, and identify the specific system owner. Remediation planning should then proceed based on these findings.

Platform or application owner.
Verify reachability and criticality.
Plan and coordinate remediation actions.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is 9Router?

9Router is a specialized AI router and token management application designed to optimize AI model interactions. It acts as a gateway, handling requests and managing connectivity, which makes it a critical point for storing sensitive secrets like API keys and OAuth tokens used to communicate with AI services.

What does CWE-200 mean for CVE-2026-55500?

CWE-200 refers to the exposure of sensitive information to an unauthorized actor. In the context of CVE-2026-55500, this weakness means the application fails to properly restrict access to its internal database, allowing unintended parties to view or replace the entire data store, including all stored credentials.

How is this vulnerability triggered?

The flaw is triggered by interacting directly with the /api/settings/database endpoint. Access does not require administrative rights; it relies on a flawed security check. Simply having low-privileged access to this specific API route is enough to execute the export or import functions. It is not triggered by standard traffic passing through the router, but rather by direct calls to the management API itself.

Is my 9Router instance at risk?

According to Halo Surface Signal, this vulnerability is likely reachable if your instance is deployed as a network edge service or management interface. If the API endpoint is accessible from the network or the public internet, the risk is significantly higher. You should assess where your instance is placed within your network topology to determine its visibility.

Do I need to update 9Router?

Yes, you should update to version 0.4.80 or later to resolve this issue. As a first step, inventory all your running instances to confirm which are affected. Once you have identified them, coordinate with your infrastructure or platform teams to plan the update, prioritizing systems that are reachable over the network or directly exposed to external traffic.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.