Skip to main content
Vulnerability Database/CVE-2026-111622

CVE-2026-111622: smart-sso OAuth2 Open Redirect Vulnerability

CVE-2026-111622 is an open redirect flaw in smart-sso through version 2.1.1 enabling attackers to steal OAuth2 authorization codes via malicious links. This article covers technical details, security impact, and remediation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-111622 Overview

CVE-2026-111622 is an open redirect vulnerability in smart-sso through version 2.1.1 that enables OAuth2 authorization code theft. The flaw resides in the /login handler, which accepts an attacker-supplied redirectUri parameter without validation. Unauthenticated attackers can craft malicious /login URLs and send them to users holding active single sign-on (SSO) sessions. When the victim clicks the link, the server issues an OAuth2 authorization code and redirects to the attacker-controlled destination, leaking the code. Attackers then redeem the stolen code at /oauth2/access_token using any valid client credentials to obtain the victim's access token. The weakness is tracked as CWE-601 (URL Redirection to Untrusted Site).

Critical Impact

Unauthenticated attackers can hijack victim SSO sessions and obtain OAuth2 access tokens, enabling account takeover across any application integrated with smart-sso.

Affected Products

  • smart-sso through version 2.1.1
  • smart-sso-server component containing the vulnerable LoginController
  • Downstream applications relying on smart-sso for OAuth2 authorization

Discovery Timeline

  • 2026-10-16 - CVE-2026-111622 published to NVD
  • 2026-10-16 - Last updated in NVD database

Technical Details for CVE-2026-111622

Vulnerability Analysis

The vulnerability stems from the /login handler in smart-sso-server accepting the redirectUri parameter without validating it against an allowlist of trusted origins. After a user authenticates, the server generates an OAuth2 authorization code and performs an HTTP redirect to the supplied redirectUri, appending the code as a query parameter. Because the destination is attacker-controlled, the code is delivered directly to the attacker's server rather than the legitimate client application. See the VulnCheck advisory and the HackMD security analysis for a detailed walkthrough.

Root Cause

The LoginController in smart-sso 1.6.0 and the updated 2.1.1 LoginController does not verify that the redirectUri matches a registered client callback URL. Compounding the issue, the Oauth2Controller at /oauth2/access_token does not bind the issued authorization code to the client that originally requested it. Any registered client credential pair can therefore redeem any leaked code.

Attack Vector

An attacker registers or already possesses valid client credentials for the smart-sso instance. The attacker crafts a /login URL with redirectUri pointing to an attacker-controlled host and delivers it to a target through phishing, chat, or embedded content. If the victim already has an active SSO session, the server issues an authorization code and redirects immediately, leaking the code to the attacker. The attacker then calls /oauth2/access_token with the stolen code and their own client credentials to receive the victim's access token. The vulnerability requires user interaction and relies on the victim having an active session.

No verified proof-of-concept code examples are published. Refer to the VulnCheck advisory for the full exploitation chain.

Detection Methods for CVE-2026-111622

Indicators of Compromise

  • Access log entries to /login containing redirectUri values pointing to external or unregistered domains
  • HTTP redirects (302) from the SSO server to hosts outside the trusted client allowlist
  • Calls to /oauth2/access_token where the client_id redeeming a code does not match the client_id originally associated with the login flow
  • Unusual geographic or temporal mismatch between a user's SSO login and subsequent token redemption

Detection Strategies

  • Parse smart-sso-server access logs and alert on /login requests whose redirectUri host is not on a known-good list
  • Correlate issued authorization codes with the clients that redeem them to flag mismatches
  • Deploy web application firewall rules that reject /login requests when redirectUri fails host validation

Monitoring Recommendations

  • Centralize smart-sso application logs in a SIEM and build detections for anomalous redirectUri values
  • Monitor for spikes in /oauth2/access_token requests originating from a small set of client credentials
  • Track user-reported phishing containing links to the SSO /login endpoint and pivot on observed redirectUri parameters

How to Mitigate CVE-2026-111622

Immediate Actions Required

  • Inventory all deployments of smart-sso and identify instances running 2.1.1 or earlier
  • Restrict access to the SSO server behind VPN or IP allowlisting where feasible until a fix is applied
  • Rotate any OAuth2 client secrets and invalidate active sessions if exploitation is suspected
  • Communicate phishing risk to users who authenticate against the affected SSO service

Patch Information

At publication, no fixed release addressing CVE-2026-111622 has been identified in the upstream smart-sso GitHub project. Monitor the project for a patched version that validates redirectUri against a per-client allowlist and binds authorization codes to the issuing client. Review the VulnCheck advisory for the latest status.

Workarounds

  • Fork smart-sso and modify LoginController to validate redirectUri against a strict allowlist of registered client callback URLs
  • Modify Oauth2Controller to bind issued authorization codes to the originating client_id and reject redemption attempts from mismatched clients
  • Deploy a reverse proxy or WAF rule that strips or validates the redirectUri parameter on /login requests before reaching the application
  • Shorten authorization code lifetimes to reduce the window in which a leaked code can be redeemed

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.