Skip to main content

Current Multi-Tenant Version | 3.68

Warning

The /presets API was deprecated a year ago when it was replaced by /preset-manager. We are now announcing EOL for the /presets API. Please ensure that it is no longer used in your workflows as we will soon stop supporting it entirely.

New Features and Enhancements

API Security in Risk Orchestration

General Availability: October 18, 2026

Risk Orchestration now includes API Security findings alongside SAST, SCA, and IaC risks in a single unified table. Users can filter and group by API Security as an engine, with the asset column showing the affected API endpoint and the source column indicating whether the finding originated from code or documentation.

This gives teams a complete, single view of risk across all their engines, including the endpoint-level context specific to API Security.

Support for Longer Preset Names

General Availability: October 18, 2026

Preset Manager now supports preset names up to 49 characters, matching on-prem SAST so names aren't truncated or lost during migration. Names over the new limit will be rejected with an error and won't be silently truncated or auto-renamed.

This applies across the UI and API for creating, cloning, and updating presets.

AI Conversation in PR Comments for ADO and Bitbucket

General Availability: October 18, 2026

Developers can now have a fluent AI-powered conversation directly in pull request comments in Azure DevOps and Bitbucket Cloud, bringing these integrations to parity with the existing GitHub experience.

Developers can write natural-language requests as PR comments, and responses appear as new comments, maintaining the flow of a real conversation. This lets teams interact with AI naturally during code review across all their supported SCMs, without switching tools or learning different workflows per platform.

Asset-Level Triage in AI Supply Chain

General Availability: October 18, 2026

Users can now triage an entire AI asset - such as a specific model - rather than triaging individual findings one by one. Available from both the Global Inventory and scan results, asset-level triage supports Mute, Snooze, and Monitored actions, and applies to all current and future findings associated with that asset. The triage state takes precedence over individual finding states. 

This makes it easier to consistently manage known or approved assets across all projects and scans, without having to re-triage the same asset repeatedly.

External MCP Server Detection

General Availability: October 18, 2026

AI Supply Chain scanning now identifies external MCP servers a project depends on, including those referenced through client configuration, dependency manifests, or remote endpoints, and resolves each to a unique, web-resolvable coordinate such as a package, image, or URL.

These are captured under the existing MCP Server asset type, alongside self-declared SDK usage, and appear in both the scan results table and the Global Inventory.

IaC

The IaC version included in this release of Checkmarx One is 2.1.21.

IaC updates are documented in the IaC changelog.

DAST

Attach Screenshots to Scan Results

General Availability: October 18, 2026

Users can now upload screenshots directly to a scan result. You can upload multiple screenshots per result in the following image formats: PNG, SVG, JPG, WebP, TIFF, and EPS, and delete or replace them after upload.

This is available via API only and requires the same Update scan permission used for editing scan result severity and status in addition to access to the relevant environment.

Reports for Failed and No-Risk DAST Scans

General Availability: October 11, 2026

DAST scans with a Failed, Partial, or Complete status (including those that found no risks) now generate a scan report, including for past scans, so you have evidence even when a scan doesn’t produce results.

These reports include Scan Summary and Executive Summary sections, plus a new Scan Diagnostics section showing insights that likely explain what went wrong.

Expanded Onboarding Options

General Availability: October 18, 2026

Onboarding now includes authentication and scan configuration options that were previously only available in Settings, so you can complete setup without leaving onboarding.

New additions include TOTP input alongside two-factor authentication, app load wait time, verification fields, custom headers, and scan options like slow running application and included paths. Authentication failure messages now link directly to the authentication report.

Obfuscated Headers in DAST Settings

General Availability: October 18, 2026

Sensitive header values in DAST settings are now obfuscated in the UI and in exported reports, so credentials aren’t displayed in plain text where other users could see them.

Resolved Issues

Item

Description

AST-181578

The /api/scan-summary endpoint returned a 500 error.

AST-181426

Scans list endpoints ran a tenant-wide count on every request, driving database CPU spikes.

AST-180540

The “API Discovered” date filter in Global API Inventory showed “Invalid Date” after a date was selected.

AST-178289

Policy evaluation returned a false negative when queried before the async evaluation write completed, due to a race condition in policy-manager.

AST-177470

Scan Tag filtering in Analytics was not working correctly.

AST-177067

Scans ran for a long time following a “Too Many Requests” failure on SAST-RM.

AST-171915

Secret Detection’s Results view sent a noEngine sentinel (“-”) as the engine path segment, causing intermittent 500 errors when fetching groups.

AST-170544

IaC scans ran for a long time due to .cache files.

AST-169654

Query Editor showed an incorrect query recommendation.

AST-169203

The ‘Copy With More Than Two Arguments Not Ending With Slash’ KICS query did not account for Windows Dockerfiles using a custom escape directive.

AST-165021

Dockerfile scans had a false negative for “Last User is root” due to incomplete coverage.

AST-163901

The Preset Manager REST API returned the id field as a string, while the OpenAPI spec defined it as an integer.

AST-160444

IaC had a false negative for “Trusted Microsoft Services Not Enabled.”

AST-158080

Opening the Application Overview returned 404 API responses for Compliance Analytics and Results State Summary.

AST-156360

Secret Detection results incorrectly reported a revoked GitHub PAT as “Valid.”

SCA-28010

SCA Auto-PR failed for delta scans when dependency resolution was skipped.

SCA-27892

In Resolver 2.15.5 (pnpm), transitive dependencies of dev dependencies did not inherit Dev scope and were instead reported as Runtime.

AST-177020

IDP configuration accepted “Max inactivity days” values greater than 365, contradicting the documented valid range of 1–365.

Issues resolved in 3.68.1

AST-181580

The description for the “Unchecked Array Index” (CPP) query was missing.

AST-181447

The Scan Configuration panel showed the project’s default branch instead of the actual branch scanned for ZIP/TAR uploads.

SCA-28239

The SCA Global Inventory API returned fewer package records than the UI.

AST-180242

Incremental scan duration was affected by a full-table pagination retry in the APISEC SAST results fetch (GetSastResults).

AST-185431

The AI Assist tab in Global Settings showed a “No Data” error.

AST-182227

The /api/repos-manager/project-conversion endpoint failed to run the first scan when autoScanCxProjectAfterConversion was set to true for Azure repos.

AST-181817

The Container Security “Exclude Non-Final Stages” filter excluded the actual shipped image in multi-stage Dockerfiles built with --target.

AST-180619

Base-image remediation suggestions were incorrect or outdated.

AST-178802

Deleting a tenant-level override removed the query from custom presets.

AST-175803

Legacy PUT query override failed with a “presets not found” error when overriding a Cx-level query included in a tenant-level preset.

AST-171837

Container Security scans did not report CVE-2024-47554 for commons-io:commons-io 2.8.0, despite the package being in the affected range.

AST-165916

Rescanning a project did not trigger SCS scans.

AST-165206

SAST results from override queries showed “Failed to Retrieve Query Description.”

AST-164604

A scans-flow service error caused 2ms scans to become stuck.

AST-159624

Tenant-level imports reported critical severity even when CVSS was disabled.

AST-158838

SAST findings got stuck in PNE due to out-of-order predicate event processing.

AST-154957

Loading a ZIP file larger than 2GB returned 499 errors.

AST-120561

Scans failed due to “Remote backend is unreachable.”

AST-94959

SAST-RM failed to provision a worker.

AST-87114

SAST scans failed, with the canceling action originating from sast-rm.

AST-181085

GET sast-results recomputed per-scan query hashes on every result row, causing massive log and database volume.

AST-177020

IDP configuration accepted “Max inactivity days” values greater than 365, contradicting the documented valid range of 1–365.

AST-164726

The SAST scan summary’s stateCounters were not updated when reverting a finding to “To Verify” with no prior predicate record.

SCA-28332

The SCA Results Packages viewer behaved incorrectly.

AST-180217

GET /api/sast-results-predicates/{similarityId}/latest returned a 504 Gateway Timeout after approximately 3 minutes.

AST-178787

Containers Policy silently returned SUCCEEDED (0 violations) instead of failing when the image-risks data fetch failed.