CVE-2026-56679: 9router: Mass assignment in PATCH /api/settings allows authenticated authorization downgrade
Summary The PATCH /api/settings endpoint writes the entire request body to persistent settings without a field whitelist. An authenticated user can set security-critical fields that are not meant to be modifiable here — notably requireLogin. Setting requireLogin: false disables authentication for the whole application, exposing all protected routes (e.g. /api/keys, /api/providers) to unauthenticated access.
Published Sep 23, 2026
Affected packages
9router
- Ecosystem
- npm
- Affected
- <= 0.5.2
- Fixed in
- 0.5.4
- Check
npm ls 9router
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The PATCH /api/settings endpoint writes the entire request body to persistent settings without a field whitelist. An authenticated user can set security-critical fields that are not meant to be modifiable here — notably requireLogin. Setting requireLogin: false disables authentication for the whole application, exposing all protected routes (e.g. /api/keys, /api/providers) to unauthenticated access.
Details
Root cause is unfiltered mass assignment (CWE-915):
src/app/api/settings/route.js(PATCH handler) parses the body and passes it toupdateSettings(body), with special handling only fornewPasswordandoidcClientSecret. All other fields pass through.src/lib/db/repos/settingsRepo.js—updateSettingsdoesnext = { ...current, ...updates }, so any key in the body overwrites stored settings, includingrequireLogin,tunnelDashboardAccess,authMode.src/dashboardGuard.js—isAuthenticatedreturnstruewheneversettings.requireLogin === false, bypassing auth on all protected routes.
This is distinct from CVE-2026-5842 (CWE-285, pre-auth bypass on /api, patched in 0.3.75). This finding requires a valid authenticated session and abuses input handling, not missing authentication.
PoC
Instance on localhost:20128, default password 123456.
- Authenticate, capture session:
POST /api/auth/loginbody{"password":"123456"}→200 {"success":true} - Mass-assign with the authenticated session:
PATCH /api/settingsbody{"requireLogin":false}→200, response confirms"requireLogin":false - Verify bypass with NO session/credentials:
GET /api/keys→200, returns full API key list unauthenticated - Cleanup (authenticated):
PATCH /api/settingsbody{"requireLogin":true}→GET /api/keysreturns401again
Impact
Post-authentication mass assignment. Any authenticated user (including one using the default password) can disable authentication globally, then read all stored API keys and provider connection data without credentials, and toggle tunnel/dashboard exposure. Escalates to remote full compromise when chained with the default password 123456 on an instance exposed via tunnel (tunnelDashboardAccess defaults to true).
Suggested fix
Whitelist user-configurable fields in the PATCH handler; move security-critical fields (requireLogin, tunnelDashboardAccess, authMode) to a dedicated endpoint requiring re-authentication (current-password re-entry), mirroring the existing DB export/import re-auth flow.
Credited to ngxuankhoi.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-56675
9router /v1 APIs has unauthenticated access via reverse proxy locality collapse
high8.3Sep 23, 2026CVE-2026-56676
9router: Image prefetch DNS rebinding allows SSRF to internal services
high7.4Sep 23, 2026CVE-2026-56678
9router: Kiro region injection allows authenticated SSRF with Authorization header forwarding
medium6.4Sep 23, 2026CVE-2026-56681
9Router has an Authentication Bypass in Public LLM API via Spoofable X-9r-Real-Ip Header
high7.3Sep 22, 2026CVE-2026-56682
9Router has a Login Brute-Force Lockout Bypass via Spoofable X-9r-Real-Ip Header
medium5.3Sep 22, 2026CVE-2026-55638
9router: Unauthenticated LLM proxy access via /codex rewrite authorization bypass
high8.6Aug 28, 2026
