# CVE-2026-111622: smart-sso through 2.1.1 OAuth2 Authorization Code Theft via Unvalidated redirectUri

> Attackers can steal OAuth2 authorization codes via an unvalidated redirectUri in the login handler, leading to account takeover.

- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-7rfc-8j8f-xgwj

## What is CVE-2026-111622?

CVE-2026-111622 is a high-severity vulnerability in a466350665 smart-sso, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

smart-sso through 2.1.1 contains an open redirect vulnerability in the /login handler that allows unauthenticated attackers to steal OAuth2 authorization codes by supplying an unvalidated redirectUri parameter. Attackers can send crafted /login links to users with active SSO sessions, then redeem stolen codes at /oauth2/access_token with any valid client credentials to obtain victims' access tokens.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2026-111622?


## How do I fix CVE-2026-111622?

No fix has been published for CVE-2026-111622 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-111622 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111622 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-111622 and fix it if it is affected.

What it is: CVE-2026-111622 is a high-severity vulnerability in a466350665 smart-sso, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111622 exists.

Affected product: a466350665 smart-sso. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-111622/ (Markdown: https://insights.sbomify.com/CVE-2026-111622/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-111622
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-111622
- OSV: https://osv.dev/vulnerability/CVE-2026-111622

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-111622/
Summaries are generated and may contain mistakes; the official description above is the record.