Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-56677 – Unauthenticated SSRF – 9Router ≤0.5.4

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-56677 is a server-side request forgery (SSRF) vulnerability in 9Router, affecting the /api/auth/oidc/test endpoint used to test OIDC identity provider configuration. The endpoint forwards an attacker-supplied issuerUrl value to the application’s OIDC discovery fetch routine without restricting requests to private, loopback, or internal network destinations. The flaw carries a CVSS v3.1 base score of 8.6 (High) and is exploitable over the network without authentication when dashboard login is disabled.

Technical details

  • Root cause: The POST /api/auth/oidc/test endpoint passes the user-controlled issuerUrl parameter directly to the fetchOidcDiscovery() function without validating or blocking private/loopback/internal IP ranges.
  • Trigger conditions: The endpoint can be reached without prior authentication when the dashboard’s login requirement is disabled, allowing an attacker to submit arbitrary URLs for the server to fetch.
  • Attack vector: Network-based, low complexity, no privileges or user interaction required (AV:N/AC:L/PR:N/UI:N).
  • Impact: Attackers can perform blind SSRF/port scanning of internal network services by observing response behavior, and can potentially manipulate or reflect responses that mimic OpenID configuration data back to the requester, affecting confidentiality and integrity of internal systems reachable from the 9Router host.

Affected software

  • 9Router (decolua) — version 0.5.4 and all earlier versions.

Severity

  • CVSS v3.1 Base Score: 8.6 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L
  • Weaknesses: CWE-306 (Missing Authentication for Critical Function), CWE-918 (Server-Side Request Forgery)

Mitigation and recommended actions

  • Immediate: Upgrade 9Router to the patched release (0.5.6 or later, per the vendor advisory) that enforces authentication and destination validation on the OIDC test endpoint.
  • If patching is not immediately possible:
    • Ensure dashboard login is enabled/enforced so the /api/auth/oidc/test endpoint is not reachable without authentication.
    • Restrict network egress from the 9Router host so it cannot reach internal loopback (127.0.0.0/8, ::1) or private address ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16).
    • Restrict issuerUrl submissions to HTTPS and known/allow-listed OIDC provider domains where possible via a reverse proxy or WAF rule.

How IONIX identifies potentially affected assets

IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: 9Router

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge