dbcve.org
CmcApplication · Nozominetworks

CVE-2026-31982

HIGH · 7.1 CVSS v3.1 Published 2026-07-09
Fix available
A fix is available. Upgrade to 26.2.0 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges 6 weeks old

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
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.

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 SAML SSO where an unauthenticated attacker can poison cached redirection parameters at the SAML sign-in endpoint, causing subsequent users to be redirected to attacker-controlled sites for phishing/credential theft, while also disrupting SAML authentication for all users.

MitigationImplement strict allowlist validation on redirect parameters, avoid using user-controlled parameters for redirects without sanitization, and clear cached SAML redirections when suspicious activity is detected.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CmcApplication
Affected:< 26.2.0
GuardianApplication
Affected:< 26.2.0

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
Low

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

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. Check installed CMC version
    Access the CMC web interface and navigate to the About or System Information page, or run 'cmc --version' from the command line if available
    Affected if The version is listed as less than 26.2.0
  2. Check installed Guardian version
    Access the Guardian console or admin interface and locate the version information, typically found under Help > About or System > Version
    Affected if The version is listed as less than 26.2.0
  3. Verify SAML SSO is configured
    Navigate to the authentication or SSO settings in the CMC/Guardian admin interface and confirm if SAML-based Single Sign-On is enabled
    Affected if SAML SSO is enabled and the product version is below 26.2.0
  4. Inspect SAML sign-in endpoint configuration
    Review the SAML SP configuration for the 'redirect' or 'AssertionConsumerServiceURL' parameter handling - look for user-controlled redirect parameters that lack allowlist validation
    Affected if Redirect parameters accept arbitrary URLs without strict allowlist validation and the version is vulnerable
  5. Check for signs of poisoned redirects
    Review SAML authentication logs for unusual redirect URLs, unexpected external domains, or multiple failed authentication attempts with varying redirect targets
    Affected if Logs show redirect URLs pointing to unknown external domains or anomalous redirect patterns

A user is affected if they run CMC or Guardian versions below 26.2.0 with SAML SSO enabled, and the redirect parameters lack strict allowlist validation or show signs of tampering.

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.

dbcve · scoped
Upgrade available Upgrade to 26.2.0 or later
Fixed in 26.2.0
Interim mitigation

Implement strict allowlist validation on redirect parameters, avoid using user-controlled parameters for redirects without sanitization, and clear cached SAML redirections when suspicious activity is detected.

Recommended fix Moderate confidence

26.2.0

  1. 1. Back up your current Cmc and Guardian configurations and data.
  2. 2. Download the updated version 26.2.0 or later from the official vendor source.
  3. 3. Review the release notes for version 26.2.0 to understand any special upgrade requirements.
  4. 4. Follow the standard upgrade procedure for Cmc and Guardian products.
  5. 5. After upgrade, verify that SAML Single Sign-On functionality works correctly.
  6. 6. Test that the open redirect vulnerability is remediated by attempting a crafted redirect URL and confirming it is blocked or properly validated.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cmc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-31982 — 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-2026-31982 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