dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-24069

MEDIUM · 5.4 CVSS v3.1 Published 2026-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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
Kiuwan SAST improperly authorizes SSO logins for locally disabled mapped user accounts, allowing disabled users to continue accessing the application. Kiuwan Cloud was affected, and Kiuwan SAST on-premise (KOP) was affected before 2.8.2509.4.

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

Kiuwan SAST has an authorization bypass vulnerability where SSO login flow does not properly validate locally disabled user account status. When user accounts are mapped between SSO identity providers and Kiuwan local accounts, disabled users can still authenticate and access the application through SSO, bypassing the local account disablement.

MitigationUpdate Kiuwan SAST on-premise to version 2.8.2509.4 or later to patch the vulnerability; for Kiuwan Cloud, await vendor remediation. Review all SSO-mapped user accounts and re-disable any accounts that should not have access.

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
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Determine Kiuwan SAST version
    Check the installed version via admin console or version file in the Kiuwan installation directory. Compare against the fixed version 2.8.2509.4.
    Affected if Running a version lower than 2.8.2509.4 and SSO integration is configured.
  2. Verify SSO integration is enabled
    Access Kiuwan admin settings and check if any SSO identity provider (SAML, OIDC, or similar) is configured and active.
    Affected if SSO authentication methods are configured and in use.
  3. Identify SSO-mapped local accounts
    In user management, review local user accounts that are linked to SSO identity providers. Look for accounts with SSO mapping indicators.
    Affected if Local user accounts exist with SSO identity provider mappings.
  4. Review disabled status of SSO-mapped accounts
    Examine each SSO-mapped local account and check whether the account is marked as disabled in Kiuwan user management.
    Affected if Any SSO-mapped local account shows a disabled status but SSO login could still be attempted.
  5. Confirm vulnerability conditions present
    If you have SSO-enabled accounts marked as disabled in Kiuwan, test whether SSO authentication still grants access to those disabled accounts.
    Affected if Disabled SSO-mapped accounts can successfully authenticate via SSO and access the application.

You are affected if Kiuwan SAST version is below 2.8.2509.4, SSO is enabled, and any local user account mapped to SSO is in a disabled state but could potentially authenticate via the SSO flow.

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

Update Kiuwan SAST on-premise to version 2.8.2509.4 or later to patch the vulnerability; for Kiuwan Cloud, await vendor remediation. Review all SSO-mapped user accounts and re-disable any accounts that should not have access.

Recommended fix Moderate confidence

Kiuwan On-premise (KOP) version 2.8.2509.4 or later

  1. 1. Identify the current Kiuwan On-premise (KOP) version by checking the application or system documentation
  2. 2. Download the fixed version 2.8.2509.4 or later from the official Kiuwan distribution channel
  3. 3. Follow Kiuwan's standard upgrade procedure for On-premise installations
  4. 4. After upgrade, verify the fix by testing SSO login with a locally disabled mapped user account - the account should no longer be able to access the application
  5. 5. For Kiuwan Cloud users, no action required as the vendor has already patched the cloud environment

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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