Open redirect in the Liberty ID-FF service provider single sign-on flow
- Exploited
- No known exploitation
- Fix
- Fixed in 14.0.6
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 14.0.6.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.22% · 12th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 12/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
OpenAM Consortium Edition contains an open redirect flaw in its Liberty ID-FF service provider single sign-on flow, and a remote attacker can reach it without logging in. An attacker can lure a user to a crafted URL so that, after the user authenticates, the browser is redirected to an arbitrary website, which may be used for phishing; this affects only deployments with a Liberty ID-FF hosted service provider configured, which is not the default setup.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.1/10CVSS 5.1
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 14.0.6.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- OpenAM consortium OpenAM (OpenAM Consortium Edition)
From 14.0.0 · fixed in 14.0.6
Evidence 2
- Advisory
- Advisory
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121825
Is CVE-2026-121825 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-121825?
OpenAM (OpenAM Consortium Edition): from 14.0.0 before 14.0.6.Source: cve.now feed data
How do I fix CVE-2026-121825?
Upgrade to a fixed version: 14.0.6.Source: cve.now feed data