Quick answers
- Is CVE-2026-55501 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55501 being exploited in the wild.
- How severe is CVE-2026-55501?
- High severity, with a CVSS score of 7.3, published 10 July 2026.
- Which products and versions are affected?
- 9router (npm) <= 0.4.71, SEMVER:introduced=0,fixed=0.4.77.
- Is there a fix for CVE-2026-55501?
- Yes. 9router (npm): upgrade to 0.4.77 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-55501 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-55501?
- Check whether you run 9router (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- 9router (npm): upgrade to 0.4.77 or later
npm install 9router@0.4.77
Technical details
A rate limit bypass exists in 9Router prior to version 0.4.80 due to improper client identity derivation. The `getClientIp` function in `src/lib/auth/loginLimiter.js` prioritizes the `X-Forwarded-For` HTTP header without verifying if the request originated from a trusted proxy. By rotating the value of this header in each request, a remote, unauthenticated attacker can ensure every login attempt is assigned to a fresh rate-limit bucket. This effectively bypasses the 5-attempt threshold and progressive lockout durations, enabling high-speed brute-force attacks against the dashboard. The vulnerability is remediated in version 0.4.80 by implementing a custom server that strips client-supplied forwarding headers and uses unspoofable socket IPs.
Affected products
- decolua 9router < 0.4.80
Identifiers
- CVE-2026-55501
- GHSA-7cfm-pqrj-xgq7
Timeline
- 2026-06-08: patched: Fix committed to repository
- 2026-06-13: advisory: Version 0.4.80 released
- 2026-06-20: advisory: GitHub Security Advisory published
- 2026-07-10: disclosed: CVE published to NVD