Quick answers
- Is CVE-2026-56679 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56679 being exploited in the wild.
- How severe is CVE-2026-56679?
- High severity, with a CVSS score of 4, published 15 July 2026.
- Which products and versions are affected?
- 9router (npm) <= 0.5.2, SEMVER:introduced=0,fixed=0.5.4.
- Is there a fix for CVE-2026-56679?
- Yes. 9router (npm): upgrade to 0.5.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-56679 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-56679?
- 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.5.4 or later
npm install 9router@0.5.4
Technical details
A mass assignment vulnerability (CWE-915) exists in the PATCH /api/settings endpoint of 9Router. The application fails to whitelist input fields when updating persistent settings, allowing the 'requireLogin' field to be overwritten by any authenticated user. By setting 'requireLogin' to false, the 'dashboardGuard.js' logic is bypassed, granting unauthenticated access to protected routes such as /api/keys and /api/providers. This allows for the exfiltration of sensitive credentials and API keys. The issue is fixed in version 0.5.4 by implementing field whitelisting.
Affected products
- decolua 9router < 0.5.4
Identifiers
- CVE-2026-56679
- GHSA-vmjq-hvgq-2wv4
Timeline
- 2026-07-10: advisory: GitHub Security Advisory published
- 2026-07-15: disclosed: CVE published to NVD
- 2026-07-15: patched: Fixed in version 0.5.4