Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify Guardian/CMC instance with SAML SSO enabled
-
DeliverySend crafted unauthenticated request to SAML endpoint with malicious redirect parameter
-
ExploitPoison server-side SAML redirect cache
-
ExecutionVictim user initiates SAML Single Sign-On
-
PersistUser transparently redirected to attacker phishing page
-
ImpactCredentials harvested or SAML authentication disrupted
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V3 - Web Frontend Security Redirect URL validation
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | SAML Single Sign-On must be configured and enabled on the Guardian or CMC deployment. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N) confirms that exploitation requires no authentication, no special attacker privileges, and no non-default configuration on the attacker's side. Exploitation is bounded by UI:P: victim users must actively initiate a SAML SSO login session after the attacker has poisoned the redirect cache, meaning the attack window depends on the cache lifetime and the frequency of user logins. Deployments that do not use SAML SSO - relying instead on local authentication or other identity mechanisms - are not affected by this vulnerability. The cache-poisoning design means the attacker's single crafted request can affect all subsequent SSO users, not just a single targeted individual. |
| Impact | The CVSS 4.0 score of 5.3 (Medium) uses AV:N/AC:L/AT:N/PR:N/UI:P, reflecting unauthenticated network access with no special conditions and passive victim interaction required. Impact metrics (VI:L/VA:L/SC:L/SI:L/SA:L) indicate limited but non-trivial effects on both the vulnerable system and downstream systems - the subsequent-system metrics capture the multi-victim nature of the cache poisoning. The UI:P requirement (victim must initiate an SSO login) is a realistic bound, not a strong mitigator, as SAML SSO is typically the default login path for enterprise deployments. The cache-poisoning characteristic meaningfully amplifies real-world impact: a single unauthenticated request can affect all users who authenticate via SAML until the cache is cleared, rather than targeting only one victim at a time. No EPSS data, CISA KEV listing, or public proof-of-concept code has been identified, suggesting no known active exploitation. However, organizations using Guardian or CMC for OT/ICS visibility should treat this as a meaningful phishing and credential-theft risk given the sensitivity of the access these products control. The moderate CVSS score somewhat underweights the multi-victim cascade potential. |
| Exploit ScenarioDerived | An unauthenticated external attacker identifies a Nozomi Networks Guardian or CMC instance with SAML SSO enabled and sends a crafted HTTP request to the SAML authentication endpoint, injecting a redirect URL pointing to an attacker-controlled phishing page designed to mimic the Guardian or CMC login interface. The malicious redirect is accepted and cached server-side; when legitimate users subsequently click 'Sign in with SSO,' they are silently forwarded to the phishing page rather than their intended destination, where their credentials are harvested. No public POC code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 09, 2026
Open Redirect via SAML SSO cache poisoning in Nozomi Networks Guardian and CMC allows unauthenticated remote attackers to corrupt the server-side redirect cache for all users by submitting a crafted request to the SAML sign-in endpoint with a malicious redirection parameter. Victims who subsequently initiate SAML Single Sign-On are transparently redirected to attacker-controlled infrastructure, enabling phishing and credential theft. The flaw additionally disrupts legitimate SAML authentication for affected users, introducing an availability dimension beyond the typical Open Redirect threat model. No active exploitation (KEV) or public exploit code has been identified at time of analysis.
RemediationAI
Consult the Nozomi Networks security advisory NN-2026:9-01 at https://security.nozominetworks.com/NN-2026:9-01 for the official fixed version and upgrade instructions. An exact patched version number is not confirmed in currently available data and should not be assumed. As an interim compensating control, disabling SAML Single Sign-On on Guardian and CMC instances and reverting to local or alternative authentication removes the attack surface entirely, at the cost of disrupting federated identity workflows and potentially requiring credential management for each appliance individually. If SAML SSO cannot be disabled, restricting network-layer access to the SAML sign-in endpoint to trusted IP ranges (e.g., internal IdP callback addresses only) reduces exposure to external attackers, though it does not protect against insider threats or compromised internal hosts. Monitoring authentication logs for anomalous redirect targets can serve as a detection measure while a patch is applied.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-601 (URL Redirection to Untrusted Site) describes failures to validate or sanitize user-controlled destination parameters before using them in HTTP redirects. In SAML authentication flows, a RelayState or equivalent post-authentication redirect parameter is passed by the client and processed by the Service Provider to return the user to their intended destination after identity assertion. The critical flaw here is that this redirect value is cached server-side without sufficient validation after being supplied by an unauthenticated party, meaning the poisoned value persists and affects subsequent legitimate authentication attempts by other users - a cache-poisoning amplification pattern rather than a simple per-request redirect manipulation. Affected products per CPE: Nozomi Networks Guardian (cpe:2.3:a:nozomi_networks:guardian:*:*:*:*:*:*:*:*) and Nozomi Networks CMC (cpe:2.3:a:nozomi_networks:cmc:*:*:*:*:*:*:*:*), both with wildcard version entries indicating all tracked versions are considered affected. Guardian and CMC are OT/ICS network visibility and security monitoring platforms, making SAML SSO a common enterprise integration point.
Know when Open Redirect gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:L/SC:L/SI:L/SA:L
Network vector with no privileges required; UI:R because victim must initiate SSO; S:C because cache poisoning propagates impact to users beyond the initial attacker interaction; C:L reflects indirect credential exposure via phishing redirect.
Primary rating from Vendor (Nozomi).
CVSS VectorVendor: Nozomi
Lifecycle Timeline
1DescriptionCVE.org
An Open Redirect vulnerability was discovered in the SAML Single Sign-On functionality due to insufficient validation of a user-controlled redirection parameter. An unauthenticated attacker can craft a request to the SAML sign-in endpoint and poison the cached SAML redirection for other users who subsequently initiate SAML Single Sign-On, enabling phishing and credential-theft attacks, as well as disrupting SAML authentication for all affected users.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
More in Open Redirect
View allA malicious third-party can give a crafted "ssh://..." URL to an unsuspecting victim, and an attempt to visit the URL ca
GFI Kerio Control versions 9.2.5 through 9.4.5 contain an HTTP response splitting vulnerability in the dest parameter of
PHP through 7.0.8 does not attempt to address RFC 3875 section 4.1.18 namespace conflicts and therefore does not protect
Multiple open redirect vulnerabilities in Apache Struts 2.0.0 through 2.3.15 allow remote attackers to redirect users to
When the default servlet in Apache Tomcat versions 9.0.0.M1 to 9.0.11, 8.5.0 to 8.5.33 and 7.0.23 to 7.0.90 returned a r
Open redirect vulnerability in age-verification.php in the Age Verification plugin 0.4 and earlier for WordPress allows
Open redirect vulnerability in Kaseya Virtual System Administrator (VSA) 7.x before 7.0.0.29, 8.x before 8.0.0.18, 9.0 b
Vulnerability in the Oracle Applications Framework component of Oracle E-Business Suite (subcomponent: Popup windows (li
Unspecified vulnerability in the Oracle Application Server Single Sign-On component in Oracle Fusion Middleware 10.1.4.3
Flarum is open source discussion platform software. Rated medium severity (CVSS 6.5), this vulnerability is remotely exp
Open redirect vulnerability in Novius OS 5.0.1 (Elche) allows remote attackers to redirect users to arbitrary web sites
Open redirect vulnerability in the Redirect function in stageshow_redirect.php in the StageShow plugin before 5.0.9 for
EUVD-2026-42532
GHSA-mhgm-6mc5-8v9j
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB