Is CVE-2026-56678 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-56678 being exploited in the wild.

How severe is CVE-2026-56678?

Medium severity, with a CVSS score of 6.4, published 15 July 2026.

Which products and versions are affected?

9router (npm) <= 0.5.2, SEMVER:introduced=0,fixed=0.5.6.

Is there a fix for CVE-2026-56678?

Yes. 9router (npm): upgrade to 0.5.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-56678 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-56678?

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.

CVE-2026-56678: decolua 9router SSRF and credential forwarding in Kiro API validation

Q: Which products and versions are affected?

9router (npm) <= 0.5.2, SEMVER:introduced=0,fixed=0.5.6.

Q: Is there a fix for CVE-2026-56678?

Yes. 9router (npm): upgrade to 0.5.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-56678 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-56678?

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.

CVE-2026-56678 · Severity: medium · CVSS 6.4 · Published 2026-07-15

9Router, an AI routing and token management tool, contains a security flaw in how it validates Kiro API keys. An authenticated user can trick the system into sending sensitive API keys to a server they control instead of the official Amazon service. This could lead to the theft of AI service credentials and allow an attacker to probe internal network resources that are normally hidden from the internet.

Technologies: 9router (npm). Vendors: npm.

Quick answers

Is CVE-2026-56678 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-56678 being exploited in the wild.
How severe is CVE-2026-56678?: Medium severity, with a CVSS score of 6.4, published 15 July 2026.
Which products and versions are affected?: 9router (npm) <= 0.5.2, SEMVER:introduced=0,fixed=0.5.6.
Is there a fix for CVE-2026-56678?: Yes. 9router (npm): upgrade to 0.5.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-56678 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-56678?: 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.6 or later
```
npm install 9router@0.5.6
```

Technical details

A Server-Side Request Forgery (SSRF) vulnerability exists in the 9Router Kiro API-key validation endpoint (`/api/oauth/kiro/api-key`). The application fails to validate the `region` parameter before interpolating it into an upstream URL template (`https://codewhisperer.${region}.amazonaws.com`). An authenticated attacker can inject a crafted region string containing a hostname and a fragment identifier (e.g., `attacker.com#`) to redirect the request to an arbitrary host. Because the application forwards the `Authorization` bearer token to this constructed URL and reflects upstream error messages, an attacker can steal API keys or perform internal network scanning. The vulnerability is addressed in version 0.5.6 by implementing strict region allowlisting and removing upstream response reflection.

Affected products

decolua 9router < 0.5.6

Identifiers

CVE-2026-56678
GHSA-6mwv-4mrm-5p3m

Timeline

2026-06-20: patched: Version 0.5.6 released
2026-07-10: advisory: GitHub Security Advisory published
2026-07-15: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.