CVE-2026-56681: 9Router: Authentication Bypass in Public LLM API via Spoofable X-9r-Real-Ip Header

Published Sep 22, 2026
·
Updated

9Router is an AI router & token saver. Prior to 0.5.6, 9Router deployments that allow requests to reach Next.js without the sanitizing custom-server.js wrapper trust the client-supplied X-9r-Real-Ip header in src/dashboardGuard.js when isLocalRequest decides whether canAccessPublicLlmApi may skip API-key validation for /api/v1/ routes. A remote unauthenticated attacker can set X-9r-Real-Ip to 127.0.0.1 and be classified as a local client, including on the verified GET /api/v1/models route. This permits unauthorized use of the instance owner's configured LLM providers, consumption of paid credits, and enumeration of configured providers and models. This issue is fixed in version 0.5.6.

Affected Software

1 affected component
9Router<0.5.6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade 9Router to a version that resolves this vulnerability.

    Fixed in 0.5.6

Event History

Sep 22, 2026
CVE Published
via MITRE·04:02 PM
Data Sourced
via MITRE·04:02 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed?

Deployments running versions before 0.5.6 are exposed if requests can reach Next.js without passing through the sanitizing custom-server.js wrapper. The issue affects public /api/v1/* routes where the client-controlled X-9r-Real-Ip header is trusted.

2

What does an attacker need to exploit this issue?

An attacker needs only network access to the affected 9Router instance. They can send an unauthenticated request with X-9r-Real-Ip set to 127.0.0.1 to be treated as a local client.

3

How can I check whether exploitation is possible?

Verify whether the deployment is older than 0.5.6 and whether any request path bypasses the sanitizing custom-server.js wrapper before reaching Next.js. A request to GET /api/v1/models with a spoofed X-9r-Real-Ip header can be used to assess whether API-key validation is skipped.

4

What should I do if I cannot upgrade immediately?

Ensure all requests are routed through the sanitizing custom-server.js wrapper so client-supplied X-9r-Real-Ip values cannot reach Next.js unsanitized. Upgrade to version 0.5.6 when possible.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203