dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-1568

CRITICAL · 9.6 CVSS v3.1 Published 2026-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Rapid7 InsightVM versions before 8.34.0 contain a signature verification issue on the Assertion Consumer Service (ACS) cloud endpoint that could allow an attacker to gain unauthorized access to InsightVM accounts setup via "Security Console" installations, resulting in full account takeover. The issue occurs due to the application processing these unsigned assertions and issuing session cookies that granted access to the targeted user accounts. This has been fixed in version 8.34.0 of InsightVM.

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 · high confidence

InsightVM versions before 8.34.0 fail to validate SAML response signatures on the Assertion Consumer Service (ACS) cloud endpoint. Attackers can submit forged unsigned SAML assertions to the ACS, causing the application to issue valid session cookies for the targeted user account, resulting in full account takeover via authentication bypass.

MitigationUpgrade InsightVM to version 8.34.0 or later to remediate the unsigned SAML assertion processing vulnerability. Organizations using Security Console SAML SSO should validate the fix in a non-production environment first.

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/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. Determine InsightVM version
    Locate the installed InsightVM Security Console version. This is typically accessible through the product UI (often under Help or About) or via version information in the installation directory.
    Affected if The installed version is before 8.34.0
  2. Confirm SAML SSO is enabled
    Check whether the Security Console has SAML Single Sign-On configured and active. This is usually found in the authentication or identity provider settings of the administrative interface.
    Affected if SAML SSO authentication is currently enabled for the Security Console
  3. Verify cloud ACS endpoint is in use
    Identify whether the SAML configuration references the cloud-based Assertion Consumer Service endpoint. This is typically configured in the SAML service provider settings or identity provider metadata.
    Affected if The ACS endpoint is the InsightVM cloud service URL and unsigned SAML assertions can be submitted to it

The environment is affected if InsightVM version is below 8.34.0 AND SAML SSO authentication is enabled using the cloud ACS endpoint.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade InsightVM to version 8.34.0 or later to remediate the unsigned SAML assertion processing vulnerability. Organizations using Security Console SAML SSO should validate the fix in a non-production environment first.

Recommended fix High confidence

InsightVM version 8.34.0

  1. Identify the current InsightVM version by accessing the Security Console or checking the system configuration
  2. Download InsightVM version 8.34.0 or later from the official Rapid7 portal at https://www.rapid7.com/products/insightvm/
  3. Backup the current InsightVM configuration, database, and any custom settings before proceeding with the upgrade
  4. Stop the InsightVM Security Console service
  5. Run the installer for version 8.34.0, following the standard upgrade prompts
  6. Restart the InsightVM Security Console service after the upgrade completes
  7. Verify the upgrade was successful by checking the version in the Security Console
  8. Confirm that SAML authentication is now properly verifying signatures on the ACS endpoint

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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