9Router: Authenticated Server-Side Request Forgery (SSRF) via OIDC Provider Test Endpoint

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.6 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L

EPSS

• CVE-2026-56677: 0.38% estimated exploitation activity in the next 30 days; percentile 31.49 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary A Server-Side Request Forgery (SSRF) vulnerability exists in the 9Router dashboard via the /api/auth/oidc/test endpoint. The application accepts a user-controlled URL string through the issuerUrl parameter and performs an outbound HTTP request without validating if the destination IP belongs to a restricted internal network range. Notably, this endpoint can be accessed without active session authentication (Unauthenticated), allowing any remote actor with network visibility to the dashboard API endpoints to trigger outbound infrastructure connections. Depending on the state and response of the internal port targeted, this flaw exhibits two distinct behaviors: 1. Port Scanning / Blind SSRF (Non-OIDC structures): Probing internal ports that are closed or running non-HTTP/non-OIDC services (e.g., SSH, Databases) forces predictable application behavior changes (e.g., structural timeout or clear JSON parsing error messages like "Unexpected token..."), allowing internal network…

Published by the source

17 Aug 2026, 21:58 UTC

Last modified by the source

17 Aug 2026, 21:58 UTC

Source last checked

26 Oct 2026, 13:01 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8g4w-4ffg-8vgx

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-56677

Advisory: 9Router: Authenticated Server-Side Request Forgery (SSRF) via OIDC Provider Test Endpoint
IDs: CVE-2026-56677, GHSA-8g4w-4ffg-8vgx
Record: https://patchnext.com/advisories/cve-2026-56677 (revision 1, source checked 26 Oct 2026, 13:01 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm 9router: affected <= 0.5.4

## Suggested inspection (read-only)
- `npm ls 9router --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on 9router.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-8g4w-4ffg-8vgx (GitHub-reviewed advisory GHSA-8g4w-4ffg-8vgx lists affected ranges: npm 9router >=0 <=0.5.4)

Commands are suggestions: review each one before running it.