Version: v12

12.2.233 Platform Release

Released August 20, 2026

This release is a patch update for the 12.2 platform release.

Addressed issues

Remediation requests: Improved reliability of exception (remediation) requests by resolving an issue where request status could lag a step behind and newly created requests could be saved without a status or computed attributes.
Platform resilience: Improved platform resilience by resolving an issue where consolidation work interrupted by a service restart could be left incomplete; interrupted work is now redelivered and resumed.
Data consolidation: Improved reliability of ticket consolidation by resolving an issue where loading very large relationship sets could exceed the query timeout and fail; relationship data is now loaded in bounded batches.
Platform stability: Improved platform stability by resolving an issue where transient database replication events could stall scheduled jobs and time out risk-score computation; computation now recovers from these events without failing.
Query performance: The regex-match (=~) operator now delivers consistent results across every query engine, no matter where the query runs.
Explorer: Findings exports are now more reliable — when an added Asset attribute expands to multiple related values, exports include all matching records instead of coming back empty.
Indicators and Dashboards: Indicator list pages and dashboard widgets now load reliably, thanks to a fix for a query-quoting path in the analytics store.

Integrations may display as running while the logs show underlying failures.
Large consolidation scans may drop their database connection, interrupting consolidation on large environments.
The writer queue can stall after a database catalog change, causing vulnerability ticket consolidation to fail until processing is restarted.
Multiple files may not load as attachments.
The platform may incorrectly cancel large connector agent syncs.
A scheduled orchestration that starts while another orchestration instance is already running fails immediately instead of being queued or skipped.
SLA definition values may revert after being saved.