Skip to main content
Version: v12

12.3.347 Platform Release

Released October 28, 2026

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

Addressed issues​

  • Administration: We've enhanced role-based access control so users with multiple cluster-related roles (such as Remediation Owner and Risk Owner) now get the combined permissions of every assigned role.

  • Automation flows: We've improved automation flow reliability by preventing a duplicate scheduled trigger on an in-progress flow step from terminating the entire flow when the original step was healthy and completed successfully.

  • BQL: We've improved result accuracy for BQL queries that combine GROUP BY with an aggregate over a related-entity traversal, which could previously undercount results.

  • BQL: We've improved performance for negated relationship conditions ("THAT NOT") on one-to-many relationships, which now stop at the first match so queries finish quickly.

  • BQL: We've enhanced the filter builder so multiple filters on attributes from related data models (for example, Asset Type alongside other Asset-related filters) work together smoothly.

  • BrinqaIQ: We've improved BrinqaIQ Assistant reliability so it consistently returns a response in the chat panel.

  • Dashboard reporting: We've enhanced list view charts so analytics widgets run successfully for users whose role access is defined through a relationship-based condition on a consolidated model.

  • Dashboard reporting: We've enhanced list view chart reliability — charts that group on a multi-value attribute now return results as expected, even with a page filter applied.

  • Dashboards: We've improved dashboard sharing so the access modal shows every user and role with access, and saving no longer affects access that was never removed.

  • Data consolidation: We've enhanced consolidation resilience so work is released cleanly when a processing worker is scaled down mid-message, and consolidation completes as expected.

  • Data consolidation: We've improved consolidation reliability with better handling of retry timing, helping consolidation keep moving.

  • Data consolidation: We've improved consolidation reliability by ensuring queued work messages always record a completion outcome, preventing consolidation from waiting indefinitely on rows that were never properly closed.

  • Data integration: We've improved connector agent resilience with automatic healing of connection state, so integration syncs keep running even if a monitoring entry is missing.

  • Data integration: We've enhanced sync reliability with improved database connection handling during data integration.

  • Data Warehouse: We've improved snapshot reliability so snapshots of very large vulnerability datasets complete successfully.

  • Dataset export: We've improved export accuracy so exporting from a list view with an active filter respects that filter, keeping large exports within row limits and time limits.

  • Dataset export: We've enhanced reliability for large analytical exports, which now select the right query engine once and complete smoothly.

  • Dataset export: We've improved export accuracy so a view's active filters, including those that can't be edited in the query text, are always applied for every user.

  • Dataset export: We've improved export accuracy for exports with many relationship joins, so columns are populated consistently.

  • Dataset export: We've enhanced export reliability with leaner access-control handling, so exports complete without hitting repeated query timeouts.

  • Deduplication: We've improved deduplication so aborting a flow now stops the underlying background job right away.

  • Detail views: We've enhanced the Assets tab on ownership cluster detail views so it loads consistently, even with asset attributes that don't apply to every asset type.

  • Exception requests: We've improved request status accuracy — requests now move to Approved or Rejected in both the All Requests list and the request detail page as soon as a reviewer makes a decision.

  • Exception requests: We've improved exception request reevaluation so existing requests are matched and updated, with no duplicates even as request counts grow.

  • List views: We've improved filter feedback — the selection count badge now appears consistently on every filter, including those on multi-value attributes.

  • List views: We've enhanced ticket list views so they load reliably for users holding several roles with overlapping access conditions.

  • List views: We've improved the basic filter builder so you can require all values on a relationship field to match (for example, assets that are both external-facing and actively exploited), not just any of them.

  • Performance: We've improved memory efficiency for BQL cluster-condition queries, preventing excessive database memory usage that could affect shared infrastructure during large relationship deletes.

  • Platform resilience: We've enhanced session reliability in multi-replica deployments with shared sessions across instances, so users stay signed in.

  • Security: We've strengthened account security with tighter scoping of password-reset capability for the Administrator role.

  • Tickets: We've improved vulnerability ticket automation with incremental per-record reconciliation and clear surfacing of any steps that fail.

  • Tickets: We've enhanced vulnerability ticket automation by processing tickets with a very large number of findings in bounded batches, so the automation completes reliably.

  • Tickets: We've enhanced the reliability of vulnerability ticket automation — ticket-creation steps now run to completion, even when their query traverses several relationships starting from the same record.

  • Tickets: We've improved ticketing automation reliability by changing how changed tickets are detected for incremental reconcile, preventing a scheduled job from running out of time before completing.

  • Vulnerability computation: We've improved compute reliability by ensuring a record with an invalid stored risk score automatically recomputes instead of repeatedly failing.