# CVE-2026-121825: Open redirect in the Liberty ID-FF service provider single sign-on flow


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-cmgw-57mx-4pqx

## What is CVE-2026-121825?

CVE-2026-121825 is a medium-severity vulnerability in OpenAM (OpenAM Consortium Edition), published on 9 Nov 2026. 

### Official description

OpenAM (OpenAM Consortium Edition) 14.0.5 and earlier contains an open redirect vulnerability (CWE-601) in the Liberty ID-FF service provider single sign-on flow. The goto parameter of the /preLogin endpoint is stored as the RelayState of the Liberty ID-FF authentication request without validation, and after the user completes single sign-on at the identity provider, the assertion consumer service redirects the browser to that value. A remote unauthenticated attacker can induce a user to access a crafted URL and, after the user authenticates, redirect the user to an arbitrary website, which may be used for phishing. Only deployments in which a Liberty ID-FF hosted service provider is configured are affected; Liberty ID-FF is not configured by default. This issue is fixed in 14.0.6, which disables the legacy Liberty ID-FF endpoints.

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

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


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

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

## Is CVE-2026-121825 being exploited?

There is no known exploitation of CVE-2026-121825 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-121825 is a medium-severity vulnerability in OpenAM (OpenAM Consortium Edition), published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-121825 in the wild and no public exploit code.

Affected product: OpenAM (OpenAM Consortium Edition). 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-121825/ (Markdown: https://insights.sbomify.com/CVE-2026-121825/index.md)
```

## Sources

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

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