CVE-2026-55500 decolua CVE debrief

Who should care

Users of 9Router AI router & token saver, especially those using versions prior to 0.4.80, should be aware of this critical vulnerability. This vulnerability could impact operators who manage 9Router deployments, platform administrators responsible for securing the router, vulnerability management teams who need to assess and prioritize this vulnerability, and security teams who need to monitor for potential exploitation.

Technical summary

CVE-2026-55500 is a critical vulnerability in 9Router AI router & token saver, with a CVSS score of 9.9. The vulnerability exists in the /api/settings/database endpoint, which allows full database export and import without authentication, beyond a middleware check. This issue was fixed in version 0.4.80. The vulnerability could lead to unauthorized access to sensitive information and potential data breaches. Users of 9Router AI router & token saver, especially those using versions prior to 0.4.80, should be aware of this critical vulnerability and take necessary actions to mitigate the risk.

Defensive priority

High

Recommended defensive actions

• Update 9Router to version 0.4.80 or later
• Restrict access to the /api/settings/database endpoint
• Monitor for suspicious activity on the /api/settings/database endpoint
• Implement additional authentication and authorization mechanisms
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide limited information about the vulnerability. Further investigation is needed to fully understand the impact of this vulnerability. The /api/settings/database endpoint allows full database export and import without authentication, beyond a middleware check. This could lead to unauthorized access to sensitive information and potential data breaches. Users should verify their current version and consider updating to 0.4.80 or later. Evidence limits suggest additional details may be required for comprehensive risk assessment.

Official resources