dbcve.org
Open RedirectWeakness · CWE-601

CVE-2025-12789

MEDIUM · 6.1 CVSS v3.1 Published 2025-11-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A flaw was found in Red Hat Single Sign-On. This issue is an Open Redirect vulnerability that occurs during the logout process. The redirect_uri parameter associated with the openid-connect logout protocol does not properly validate the provided URL.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Open redirect vulnerability in Red Hat Single Sign-On's OpenID Connect logout protocol. The redirect_uri parameter is not properly validated before redirecting users after logout, allowing attackers to craft malicious URLs that redirect victims to attacker-controlled sites.

MitigationImplement strict allowlist-based validation of the redirect_uri parameter against pre-registered trusted URLs before performing logout redirects.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm RH-SSO installation
    Check for the presence of Red Hat Single Sign-On by reviewing installed packages, services, or the product version (typically found in /opt/rh/sso or via systemctl status rh-sso-* commands)
    Affected if Red Hat Single Sign-On is installed and running
  2. Identify RH-SSO version
    Run 'rh-sso-version' or check /opt/rh/sso/standalone/configuration/build.properties for the exact version number
    Affected if The installed version falls within any affected version range for CVE-2025-12789 (compare against official Red Hat advisory)
  3. Verify OpenID Connect logout is configured
    Inspect the RH-SSO realm settings under Authentication > Flows > Redirect to Identity Provider, or review the oidc logout endpoint configuration in the server configuration files (standalone.xml or domain.xml)
    Affected if OpenID Connect logout (OIDC RP-initiated logout) is enabled in any realm
  4. Check redirect_uri validation configuration
    Review the realm's Identity Provider settings for redirect_uri validation, or examine the logout configuration for any allowlist or whitelist of permitted redirect_uri values
    Affected if No strict allowlist-based redirect_uri validation is configured, or the validation is missing entirely

A user is affected if RH-SSO is installed, OpenID Connect logout is enabled, and the redirect_uri parameter lacks strict allowlist-based validation against pre-registered trusted URLs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict allowlist-based validation of the redirect_uri parameter against pre-registered trusted URLs before performing logout redirects.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12789 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12789 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data