Release Notes
Abstract
This technical note provides guidance for installing IBM Guardium Data Protection 12.2.4, including any new features or enhancements, resolved or known issues, or associated notices for Guardium patch update (GPU) 12.0p7240.
Content
On Passport Advantage, you can find the Guardium Product Image - ISO file, licenses, product keys, and manuals. You can download only the products that your site is entitled. If you need assistance to find or download a product from the Passport Advantage site, contact the Passport Advantage team at 800-978-2246 (8:00 AM - 8:00 PM ET) or by email at paonline@us.ibm.com.
On Fix Central, you can find upgrades, Guardium Patch Update (GPU) files, individual patches, and the current versions of database agents, such as Software TAP (S-TAP) and Guardium Installation Manager (GIM). If you need assistance to find a product on Fix Central, contact IBM Support.
- Fix ID: SqlGuard_12.0p7240_GPU_Oct_2026_V12.2.4_FC
- File name: SqlGuard-12.0p7240_GPU_Oct_2026_V12.2.4_FC.tgz.enc.sig
- MD5 checksum: 790929901560ae32b9fd566d7707a914
Note: GPU 12.0p7240 is a replacement for GPU 12.0p240, which was initially released on 30 September 2026. Customers who already upgraded environments to 12.0p240 should not install 12.0p7240. Instead, you should install patch 12.0p1064 (see release notes). For more information, see Remote syslog issues after upgrading to Guardium appliance patch 12.0p240.
Install Guardium 12.2.4
Guardium 12.2.4 is available as an ISO product image on Passport Advantage. If the downloaded package is in .zip format, extract it outside of the Guardium appliance before you upload or install it. Review the latest version of these release notes just before you install. Install Guardium across all the appliances, such as the central manager, aggregators, and collectors. For detailed steps, see Installing your Guardium Data Protection system.
Before you upgrade, confirm that your appliance meets the minimum requirements. Upgrade your firmware to the latest versions provided by your vendor. If you use a Guardium appliance, check Fix Central for the latest firmware.
Prerequisites
- Guardium Data Protection 12.2.0 (GPU 12.0p200, see release notes)
- The latest Guardium Data Protection health check patch 12.0p9997 (see release notes)
You can upgrade to Guardium 12.2.4 (GPU 12.0p7240) from Guardium systems that are running on version 12.2.0 (GPU 12.0p200, see release notes). The best approach for upgrading Guardium depends on the version you are upgrading from, the hardware of your system, and any special partitioning requirements you might have. See Identifying the correct upgrade path to review upgrade scenarios and identify the correct upgrade path for your Guardium systems. Review the latest version of these release notes just before you install.
Note: The Guardium system will restart during the upgrade process for all of the patch installations, so schedule the upgrades in batches during low database traffic times to minimize audit gaps. Do not reboot the appliance while the patch installations are in progress. Contact IBM Support if there is an issue with patch installation.
License key administration
Guardium Data Protection license keys changed for administrative reasons.
- Existing deployments are not affected. If you previously activated Guardium Data Protection by using a key, your deployment will continue to operate normally. Activated keys are already redeemed and no disruption is expected.
- New deployments using affected keys will be blocked. If you attempt to apply one of the revoked keys to a new Guardium Data Protection instance, you will see the following message in the Guardium product UI: "License key has been rotated, please retrieve an updated key from Passport Advantage." If you encounter the message during a new deployment, take the following steps:
- Log in to your IBM Passport Advantage account.
- Retrieve your replacement activation key.
- Apply the new key to complete your deployment.
If you have trouble retrieving the license key from Passport Advantage, contact Passport Advantage Support. If you have questions about this notice or need assistance with key replacement, reach out to IBM Support through your standard support channel.
Feature flags
Guardium supports feature flags to help you control when new capabilities are activated in your environment. For Guardium 12.2.4, the following feature patches are available in Fix Central for download/installation:
- Data lake (long-term retention) patch 12.0p90240 (see release notes)
- Edge patch 12.0p15005 (see release notes)
- Gen AI patch 12.0p81240 (see release notes)
- Small Language Model patch 12.0p85240 (see release notes)
For more information, see Applying feature flags.
Single stream agent releases
Most of the Linux-UNIX and Windows agents for Guardium Data Protection versions 12.0 and later are now released in a single stream. This simplifies maintenance, reduces version divergence, and ensures consistent feature and fix availability across all supported 12.x environments. For more information, see Single-stream agent releases.
Special Guardium Database Protection Service update (for Vulnerability Assessment only)
A special Guardium Database Protection Service (DPS) update, Guardium_12.X_DPS-Special-Q3-2026, which is available for download from Fix Central, must be applied after you upgrade to Guardium 12.2.4 (GPU 12.0p7240) from previous versions. See release notes for detailed file information. Be sure to also check Fix Central for the latest Rapid Response DPS release and apply it after uploading the Special DPS file.
Secured CAS connections require IBM Semeru Runtimes 17.0.14.0 or later
Starting with Guardium Linux-UNIX CAS 12.0px103 r125006 (see release notes) and Windows CAS 12.xp102 r120204351 (see release notes), a CAS client can only connect to a CAS server by using secured connections with certification authentication (CA). The default CA certificate is now packaged with the CAS client installer. The CAS server and CAS client require IBM Semeru Runtimes 17.0.14.0 or later.
Intelligent appliance patch management
Redesigned patch management experience with automated downloads, at-a-glance impact indicators for reboots and schema changes, and a direct link to Fix Central documentation. Administrators can configure, track, and act on available patches from a single, consolidated view to reduce manual effort and minimizing security exposure windows.
Automation enablement for Application TAP (A-TAP) activation and deactivation
Guardium now enables non-root database users and automation pipelines to script A-TAP activation, deactivation, and configuration updates during database patching without elevated root access—backed by continuous state detection, automatic collector alerting, and a kernel-verified audit trail.
Modernized API framework ad self-service key management
A modernized REST API v2 framework featuring a centralized API key management console and an interactive, Swagger-based API documentation interface.
Self-service API key management. Independently create, revoke, and manage expiration lifecycles for REST API keys directly within the Guardium user interface—eliminating the need to contact IBM Support. Administrators can manage all user keys, while individual users only manage their own API keys.
Interactive API explorer and tooling. Developers can browse, test, and execute APIs from a single location, with automatically generated cURL and Guardium CLI syntax examples to accelerate integration.
REST API v2 is recommended for all new integrations and automation workflows, while v1 APIs remain fully supported for existing deployments and accessible through the same interface. Together, these enhancements improve API security, governance, and developer time-to-value.
Active threat detection and analytics
Improved case correlation, database connection classification, generated reports, and policy-based outlier detection.
Build your own case module. Controls over how observations from Active threat analytics detection engines are correlated into cases. Rather than relying on vendor-defined logic, encode your own threat models and thresholds, define multi-stage detection expressions, and control exactly when and why a case is raised.
Generated reports for Active threat analytics cases. Provides richer contextual information for more visibility into case details, associated observations, sources, and investigation outcomes. These reports can be sent to Syslog/SIEM by using Audit Process Builder.
New connection logbook. View, assign, and modify the classification of every database connection profile observed across all active cases and observations. Classify connections as trusted, untrusted, or batch to accelerate triage of Active threat analytics cases. Real-time Trust Evaluator (RTTE) trust score provides rolled-up recommendations. Cases are then tagged based on these classifications.
Active threat analytics user experience modernization
Modernized dashboard with interactive charts and a configurable layout to visualize the distribution of active threat cases across multiple dimensions, including severity, threat category, database, database user, and server IP, without exporting data or building views manually.
Aggregator performance improvements
Speed up report generation and reduce latency during concurrent workloads with the new Parallel Query option in Guardium aggregators, which uses partition-aware routing and temporary staging tables to minimize data scans and optimize memory at runtime. Note: The Parallel Query option is only available for newly created or cloned reports in the Access, Exception, and Policy Violation domains.
Audit process user experience modernization
Audit Process Builder UI is modernized with clear workflow visibility, role-based actions, and a scalable review interface. Tabbed pages, expandable rows, and side panels reduce visual clutter, enabling analysis to review, comment on, and track audit history from a single, consolidated view.
Data streams monitoring proxy support
Microsoft Entra ID authentication support for Azure Event Hubs data streaming with proxy.
Location-aware data activity monitoring
Pre-built session-level policy template that detects and responds to location-based database activity anomalies. Prove at query time that database sessions originated from permitted jurisdictions.
Distributed long term retention query support
Gain capacity on demand for retaining and querying historical data with a new distributed data lake environment. Attach external worker appliances to an existing, single-node, long term retention appliance so it becomes the core unit of your distributed deployment. For more information, see release notes for Data lake (long term retention) patch 12.0p90240.
Edge Gateway 2.3
Reduce fragmentation of database collection and monitoring by:
Streaming database traffic from a single Edge cluster to multiple aggregators.
Mapping Software TAP (S-TAP)-to-Aggregator to isolate sensitive database workloads.
Synchronizing security policy rule states across multiple collectors with session-level policies rules state service.
Supporting File Activity Monitoring (FAM) with Linux-UNIX S-TAP to satisfy compliance mandates.
For more information, see release notes for Edge patch 12.0p15005.
Operational improvements
Guardium appliances now support:
Mutual TLS authentication (mTLS) for SIEM forwarding.
Support for 3072-bit and 4096-bit certificate key lengths.
Real-time notification of high CPU utilization for Guardium appliances on Amazon Elastic Compute Cloud (EC2).
Small Language Model for AI use cases
Guardium gen AI appliance now includes a pre-packaged Small Language Model (SLM), enabling adoption of gen AI use cases without requiring integration with external language model providers. For more information, see release notes for Small Language Model patch 12.0p85240.
Universal connector
New universal connector features and enhancements:
Ability to add custom CA certificate chains for Syslog-based universal connectors and Oracle Unified Audit (OUA) universal connector.
Kafka-aware diagnostic agent that reads structured event data from each Kafka node and surfaces actionable diagnostics directly in the central manager troubleshooting interface.
Ability to temporarily disconnect an asset from a universal connector without uninstalling a profile.
Modernized Datasource Profile Management user interface with streamlined Manage, Actions, and Test connection functions.
Updated Datasource Profile Management reports include deployed collectors.
Support for dynamic extraction of account ID from AWS CloudTrail events payload for Amazon DynamoDB universal connector.
Support for Windows NT authentication added for On Prem Microsoft SQL Server universal connector.
Amazon Resource Name (Role ARN) support for AWS data sources with on-prem collectors.
Records Affected support for Azure PostgreSQL Logstash-based universal connector.
UC 2.0 features and enhancements include:
New Datasource support for AWS Athena Iceberg over Cloudwatch, PostgreSQL 17 and 18.4 over Syslog, Redis over Syslog, and NetAPP ONTAP NAS.
Additional UC 2.0 connectors available for MongoDB Atlas, MongoDB over Syslog, MySQL on prem over Syslog, and Neo4j over Syslog.
Restart communications for a single UC 2.0 connector while other asset communications remain unaffected.
Ability to create multiple datasource profiles with the same port for Syslog-based universal connectors.
Vulnerability Assessment
Scan databases for vulnerabilities by using a modernized user experience, new template-based assessment creation wizard, and data source tests based on the latest benchmarks.
Create and customize vulnerability assessments faster with a guided, step-by-step Assessment Builder wizard, which includes options for predefined templates.
Manage and monitor vulnerability assessments through a modernized Assessments user interface, which now displays error status more prominently.
Addition of Assessment Tests for Oracle 26ai based on latest CIS benchmarks.
Linux-UNIX and Windows Agents updates
More information about new features and enhancements to the Configuration Auditing System (CAS), Guardium Installation Manager (GIM), File Activity Monitor (FAM) for Windows (FamMonitor), and Software TAP (S-TAP) agents, see their corresponding release notes:
- Linux-UNIX CAS 12.xp103 r125006 (see release notes)
- Linux-UNIX GIM 12.xp103 r125006 (see release notes)
- Linux-UNIX S-TAP 12.xp103 r125006 (see release notes)
- Windows CAS 12.xp102 r120204351 (see release notes)
- Windows FamMonitor 12.xp102 r120204351 (see release notes)
- Windows GIM 12.xp102 r120204351 (see release notes)
- Windows S-TAP 12.xp102 r120204351 (see release notes)
Patch updates for the Linux-UNIX and Windows Agents are cumulative; they contain all previous patches for that major version.
Sniffer updates
The latest sniffer patch that is included in Guardium 12.2.4 (GPU 12.0p7240) is versions 12.0p4019 (see release notes) and 12.0p4018 (see release notes). Sniffer patches are cumulative; they contain all previous sniffer patches for that major version.
Unified Discovery and Classification updates
New features and enhancements are available for the Unified Discovery and Classification, an independent component of Guardium Data Protection that is included with your license. Details are available in the Unified Discovery and Classification version 1.4 release notes.
Operating systems
Linux-UNIX S-TAP: Red Hat Enterprise Linux (RHEL) 10 on ppc and s390x architectures
Data Activity Monitoring (DAM)
Linux-UNIX S-TAP:
- EDB Postgres 18.4
- Elasticsearch 9.2.3
- IBM DataStax Hyper-Converged Database (HCD)
- MariaDB 12.3.2
- MySQL 9.7
- MongoDB 8.3.3
- PostgreSQL 18.4
- Teradata Vantage 20.00.30.66
Windows S-TAP:
- EDB Postgres 18.4
- Elasticsearch 9.2.3
- MariaDB 12.3.2
- MySQL 9.7
- MongoDB 8.3.3
- PostgreSQL 18.4
Most supported platforms information is available in the Guardium Supported Datasources matrix. For all other supported platforms and system requirements information, including Vulnerability Assessment, platforms that are supported by External S-TAP, information about IBM i, and hardware or virtual machine requirements, see System Requirements for Guardium 12.2.x.
Deprecated functionality
In Vulnerability Assessment, IBM Db2 z/OS Test ID 360 “AUTHCACH subsystem parameter is set properly” is deprecated for DB2 z/OS v13 and later.
| Version | Issue key | Summary | Known issue (APAR) |
|---|---|---|---|
| 12.2.3 (GPU 12.0p230) | See release notes for Guardium 12.2.3 (GPU 12.0p230) | ||
| 12.2.4 (GPU 12.0p7240) | GRD-118747 | MongoDB over Syslog universal connector message format template issue | DT496523 |
| GRD-121950 | Backport MongoDB Vulnerability Assessment Test ID 897 | DT474738 | |
| GRD-122508 | Environment variables not ported from central manager to managed units | DT499110 | |
| GRD-124214 | Request for Amazon Machine Image with AWS Systems Manager (SSM) enabled | DT472214 | |
| GRD-124975 | Aggregators incorrectly displayed the "Investigation dashboard open issues" message in the deployment health table when investigation dashboard (quick search) was disabled | DT473860 | |
| GRD-126730 | Garbled characters appear in Audit Process results email subject line | DT474347 | |
| GRD-126997 | Incorrect disk space used by MySQL and free space in MySQL files calculation | DT473872 | |
| GRD-127426 | Vulnerability Assessment datasource connection error | ||
| GRD-127497 | Timestamp parsing error when storing custom sniffer certificate in CLI | DT494766 | |
| GRD-127653 | S-TAP clusters missing from S-TAP by cluster view of Deployment Health Table | DT498551 | |
| GRD-127788 | Add timeout parameter to UC Kafka and UC Kafka Connect Service | ||
| GRD-128181 | Update authentication configuration | DT496071 | |
| GRD-128297 | Classification scan halts after 30-minute timeout | DT498134 | |
| GRD-128318 | Support for 4096-bit certificate key length | DT495949 | |
| GRD-128749 | System backup failed transfer with Amazon S3 (Simple Storage Service) IAM instance profile | DT498020 | |
| GRD-128830 | Port 8081 issue | DT496770 | |
| GRD-128937 | Aggregation archive error: failed to copy files to S3 bucket | DT498486 | |
| GRD-129004 | Signature validation error when installing Qualys Cloud Agent | DT495319 | |
| GRD-129286 | Hard Disk Usage report tabular and graphical views show inconsistent temporary file system (tmpfs) usage results | DT495803 | |
| GRD-129310 | Query builder generated problematic query | ||
| GRD-129441 | Guardium 12.2.1 appliance with Neo4J datasource (SSL enabled) failed to connect after upgrading to Guardium 12.2.2. | DT496673 | |
| GRD-129809 | Add azure-identity-extensions for Azure token lifecycle | DT498021 | |
| GRD-129819 | Kafka rebalancing creates multiple sessions | ||
| GRD-130000 | Active threat analytics case details restricted to admin role only | DT498118 | |
| GRD-130119 | Server IP aliases defined in alias builder not displayed in S-TAP Control page | DT499099 | |
| GRD-130528 | Permissions bug prevented the grdapi pull_external_stap_keystore command from executing on managed units | DT496913 | |
| GRD-130574 | After installing GPU 12.0p230 on a Guardium version 12.2.x appliance, lightweight directory access protocol (LDAP) authentication might fail. The fix prevents GPU installation from corrupting or overwriting the LDAP truststore and preserves existing LDAP certificate trust relationships. | DT495636 | |
| GRD-130667 | On standalone collector, clicking Create Profile errors with “no privileges” message | DT498463 | |
| GRD-130763 | Add parameter for Parallel Query for all existing reports | ||
| GRD-130897 | Datamart extraction is appending backslash to DB and OS username | DT498290 | |
| GRD-130905 | Incorrect column mapping when tuple parameters are selected in a non-alphabetical order | DT498548 | |
| GRD-131095 | Health check 12.0p9997 provided warning that seem to be false positives | ||
| GRD-131231 | Issue with profile validation for AWS Postgres Over Cloudwatch Connect 2.0 universal connector | DT498426 | |
| GRD-131381 | Clicking in the Alerter SNMP configuration on "Test connection" resulted in "SNMP trap sink host is unreachable" message | DT498815 | |
| GRD-131412 | Warning in the CLI output caused by non-ASCII characters in usernames | DT498048 | |
| GRD-131827 | Hostname changed after applying 12.0p230 on cloud appliance | DT498487 | |
| GRD-132090 | bind-dyndb-ldap RPM dependency conflict | DT498055 | |
| GRD-132304 | GCP BigQuery universal connector created multiple S-TAPs | DT498188 | |
| GRD-132347 | Change permissions for Azure units | DT499891 | |
| GRD-132454 | Compare S-TAP and GIM versions report did not apply "STAP greater" filter correctly | DT499063 | |
| GRD-132728, GRD-133106 | SNMP traffic blocked after firewall rule change that migrated iptables to nftables | DT498574 | |
| GRD-132759 | CLI user authentication change from Local to LDAP silently reverts when SAML is enabled | DT500420 | |
| GRD-132847 | store system hostname command cleans manually added host entries | DT500048 | |
| GRD-132997 | AUDIT_TASK_PARAMETER.MODIFIED_FLAG not updated as expected | DT499066 | |
| GRD-133413 | Issue where after installing patch 12.0p231, systems using EFI as the bootloader might get stuck at the GRUB prompt during the boot process and not proceed to load the operating system | DT499053 | |
| GRD-133477 | Active threat analytics cases and custom categories missing after upgrade | DT499578 | |
| GRD-133713 | 'Recommendations' report for Entitlement Optimization not visible under Distributed Report | DT500162 | |
| GRD-133870 | Restore from Amazon S3 failed when using IAM instance profile | DT500084 | |
| GRD-133957 | Qualys scanner agent integration issues | DT500606 | |
| GRD-134125 | VA Scanner incorrectly returned ERROR scores instead of PASS_WITH_EXCEPTION for tests with exceptions | DT500430 | |
| GRD-134670 | After installing GPU 12.0p230 on a Guardium 12.2.x appliance, existing universal connector (UC) 1.0 profiles that were active prior to the upgrade did not function correctly |
This patch remediates multiple security vulnerabilities.
| Patch | CVE |
|---|---|
| 12.2.3 (GPU 12.0p230) | This patch includes security updates from Guardium 12.2.3 (GPU 12.0p230, see release notes) |
| 12.2.4 (12.0p7240) | CVE-2022-1941, CVE-2023-49083, CVE-2024-21090, CVE-2024-34459, CVE-2024-42516, CVE-2025-5278, CVE-2025-6170, CVE-2025-10263, CVE-2025-10911, CVE-2025-13151, CVE-2025-38004, CVE-2025-39797, CVE-2025-40026, CVE-2025-40064, CVE-2025-40168, CVE-2025-54518, CVE-2025-68211, CVE-2025-68214, CVE-2025-71066, CVE-2025-71113, CVE-2025-71147, CVE-2026-1933, CVE-2026-1965, CVE-2026-2340, CVE-2026-3012, CVE-2026-3783, CVE-2026-3832, CVE-2026-3833, CVE-2026-4408, CVE-2026-4480, CVE-2026-5260, CVE-2026-5419, CVE-2026-5435, CVE-2026-5450, CVE-2026-5928, CVE-2026-6238, CVE-2026-6477, CVE-2026-6653, CVE-2026-6893, CVE-2026-7383, CVE-2026-8177, CVE-2026-8286, CVE-2026-9076, CVE-2026-9538, CVE-2026-9547, CVE-2026-9698, CVE-2026-10723, CVE-2026-10805, CVE-2026-10879, CVE-2026-11331, CVE-2026-11622, CVE-2026-11721, CVE-2026-11822, CVE-2026-11824, CVE-2026-11940, CVE-2026-11979, CVE-2026-12912, CVE-2026-13204, CVE-2026-13321, CVE-2026-13757, CVE-2026-14164, CVE-2026-14380, CVE-2026-14474, CVE-2026-14476, CVE-2026-14739, CVE-2026-15308, CVE-2026-15588, CVE-2026-15816, CVE-2026-16118, CVE-2026-16313, CVE-2026-16524, CVE-2026-16526, CVE-2026-16527, CVE-2026-16529, CVE-2026-16730, CVE-2026-22979, CVE-2026-23002, CVE-2026-23003, CVE-2026-23110, CVE-2026-23415, CVE-2026-24072, CVE-2026-24880, CVE-2026-25679, CVE-2026-25681, CVE-2026-25854, CVE-2026-27136, CVE-2026-27145, CVE-2026-29145, CVE-2026-29146, CVE-2026-29167, CVE-2026-29169, CVE-2026-29518, CVE-2026-31411, CVE-2026-31474, CVE-2026-31488, CVE-2026-31530, CVE-2026-31669, CVE-2026-31772, CVE-2026-31787, CVE-2026-31790, CVE-2026-32280, CVE-2026-32281, CVE-2026-32283, CVE-2026-32990, CVE-2026-33006, CVE-2026-33416, CVE-2026-33636, CVE-2026-33818, CVE-2026-33845, CVE-2026-33846, CVE-2026-34180, CVE-2026-34181, CVE-2026-34182, CVE-2026-34183, CVE-2026-34355, CVE-2026-34356, CVE-2026-34483, CVE-2026-34487, CVE-2026-34500, CVE-2026-35177, CVE-2026-35406, CVE-2026-39821, CVE-2026-39822, CVE-2026-39829, CVE-2026-39830, CVE-2026-39832, CVE-2026-39835, CVE-2026-40170, CVE-2026-40985, CVE-2026-40986, CVE-2026-41284, CVE-2026-41293, CVE-2026-41411, CVE-2026-41989, CVE-2026-41991, CVE-2026-41992, CVE-2026-42009, CVE-2026-42010, CVE-2026-42011, CVE-2026-42012, CVE-2026-42013, CVE-2026-42014, CVE-2026-42015, CVE-2026-42496, CVE-2026-42498, CVE-2026-42508, CVE-2026-42535, CVE-2026-42536, CVE-2026-42764, CVE-2026-42766, CVE-2026-42767, CVE-2026-42768, CVE-2026-42769, CVE-2026-42770, CVE-2026-43038, CVE-2026-43074, CVE-2026-43112, CVE-2026-43114, CVE-2026-43116, CVE-2026-43158, CVE-2026-43198, CVE-2026-43206, CVE-2026-43233, CVE-2026-43237, CVE-2026-43260, CVE-2026-43276, CVE-2026-43279, CVE-2026-43303, CVE-2026-43329, CVE-2026-43414, CVE-2026-43450, CVE-2026-43499, CVE-2026-43512, CVE-2026-43513, CVE-2026-43514, CVE-2026-43515, CVE-2026-43618, CVE-2026-43951, CVE-2026-44083, CVE-2026-44119, CVE-2026-44185, CVE-2026-44186, CVE-2026-44431, CVE-2026-44432, CVE-2026-44631, CVE-2026-44950, CVE-2026-45409, CVE-2026-45445, CVE-2026-45446, CVE-2026-45447, CVE-2026-45878, CVE-2026-45898, CVE-2026-45970, CVE-2026-45984, CVE-2026-45991, CVE-2026-46054, CVE-2026-46056, CVE-2026-46086, CVE-2026-46090, CVE-2026-46113, CVE-2026-46116, CVE-2026-46117, CVE-2026-46120, CVE-2026-46125, CVE-2026-46135, CVE-2026-46145, CVE-2026-46150, CVE-2026-46152, CVE-2026-46155, CVE-2026-46166, CVE-2026-46173, CVE-2026-46176, CVE-2026-46185, CVE-2026-46189, CVE-2026-46209, CVE-2026-46215, CVE-2026-46227, CVE-2026-46242, CVE-2026-46243, CVE-2026-46244, CVE-2026-46259, CVE-2026-46316, CVE-2026-46323, CVE-2026-46331, CVE-2026-46483, CVE-2026-47162, CVE-2026-47167, CVE-2026-48864, CVE-2026-48914, CVE-2026-48962, CVE-2026-50031, CVE-2026-50219, CVE-2026-50229, CVE-2026-50256, CVE-2026-50257, CVE-2026-50258, CVE-2026-50259, CVE-2026-50260, CVE-2026-50261, CVE-2026-50262, CVE-2026-50263, CVE-2026-50264, CVE-2026-52858, CVE-2026-52920, CVE-2026-52923, CVE-2026-52924, CVE-2026-52933, CVE-2026-52950, CVE-2026-52973, CVE-2026-52976, CVE-2026-52991, CVE-2026-52993, CVE-2026-53000, CVE-2026-53006, CVE-2026-53016, CVE-2026-53059, CVE-2026-53071, CVE-2026-53073, CVE-2026-53131, CVE-2026-53136, CVE-2026-53143, CVE-2026-53185, CVE-2026-53189, CVE-2026-53202, CVE-2026-53264, CVE-2026-53266, CVE-2026-53268, CVE-2026-53281, CVE-2026-53329, CVE-2026-53356, CVE-2026-53359, CVE-2026-53374, CVE-2026-53391, CVE-2026-53392, CVE-2026-53397, CVE-2026-53399, CVE-2026-53404, CVE-2026-53434, CVE-2026-54369, CVE-2026-54370, CVE-2026-54371, CVE-2026-54411, CVE-2026-55276, CVE-2026-55653, CVE-2026-55654, CVE-2026-55655, CVE-2026-55693, CVE-2026-55831, CVE-2026-55833, CVE-2026-55955, CVE-2026-55956, CVE-2026-55999, CVE-2026-56001, CVE-2026-56002, CVE-2026-56132, CVE-2026-56745, CVE-2026-56746, CVE-2026-56819, CVE-2026-56858, CVE-2026-56860, CVE-2026-56862, CVE-2026-57231, CVE-2026-57455, CVE-2026-57456, CVE-2026-58010, CVE-2026-58011, CVE-2026-58012, CVE-2026-58013, CVE-2026-58014, CVE-2026-58015, CVE-2026-58016, CVE-2026-58055, CVE-2026-58471, CVE-2026-58472, CVE-2026-59083, CVE-2026-59084, CVE-2026-59296, CVE-2026-59679, CVE-2026-59843, CVE-2026-59844, CVE-2026-59845, CVE-2026-59846, CVE-2026-59847, CVE-2026-59848, CVE-2026-59850, CVE-2026-59856, CVE-2026-59858, CVE-2026-59886, CVE-2026-59898, CVE-2026-59899, CVE-2026-59900, CVE-2026-59901, CVE-2026-59921, CVE-2026-59996, CVE-2026-60002, CVE-2026-60075, CVE-2026-63800, CVE-2026-63808, CVE-2026-63824, CVE-2026-63879, CVE-2026-63884, CVE-2026-63886, CVE-2026-63887, CVE-2026-63888, CVE-2026-63952, CVE-2026-64002, CVE-2026-64007, CVE-2026-64017, CVE-2026-64018, CVE-2026-64048, CVE-2026-64136, CVE-2026-64189, CVE-2026-64191, CVE-2026-64219, CVE-2026-64268, CVE-2026-64276, CVE-2026-64277, CVE-2026-64287, CVE-2026-64298, CVE-2026-64304, CVE-2026-64319, CVE-2026-64320, CVE-2026-64368, CVE-2026-64379, CVE-2026-64382, CVE-2026-64384, CVE-2026-64386, CVE-2026-64387, CVE-2026-64438, CVE-2026-64490, CVE-2026-64530, CVE-2026-64531, CVE-2026-64560, CVE-2026-64561, CVE-2026-65182, CVE-2026-65183, CVE-2026-65637, CVE-2026-65905, CVE-2026-65927, CVE-2026-66299, CVE-2026-66422, CVE-2026-68145, CVE-2026-68166, CVE-2026-68343, CVE-2026-68388, CVE-2026-68480, CVE-2026-68525, CVE-2026-68569, CVE-2026-68763, CVE-2026-72069, CVE-2026-72130, CVE-2026-72693, CVE-2026-73180, CVE-2026-74581, CVE-2026-82900, CVE-2026-84057, CVE-2026-84209, CVE-2026-84272 |
More information is available in the following IBM Security Bulletin published by the IBM Product Security Incident Response Team (PSIRT):
- https://www.ibm.com/support/pages/node/7284102
- https://www.ibm.com/support/pages/node/7293412
- https://www.ibm.com/support/pages/node/7293466
- https://www.ibm.com/support/pages/node/7293824
- https://www.ibm.com/support/pages/node/7295784
- https://www.ibm.com/support/pages/node/7295785
| Component | Issue key | Summary |
|---|---|---|
| Active Threat Analytics | GRD-136271 | Within the Active Threat Analytics Setup user interface, when a managed unit group filter is selected, the Managed Unit, Unit Status, and Engines count values for all unit groups are displayed instead of values for only the selected group. A fix will be available in an upcoming release. |
| Audit Process Builder | GRD-133977 | When creating an audit process, date and time pickers are not available to select or modify values. Workaround: Manually edit the Period From field in the Select Task tab as a text field. |
| Audit Process Builder | GRD-134887 | When an audit process is configured with a report task of type "All Roles - User" and run, the system writes one syslog entry per role to /var/log/messages. However, the All Roles - User report in the UI does not display the same list of role entries. Workaround: To view the complete set of results of an Audit Process run, download all of the results. |
| Audit Process Builder | GRD-136415 | In the new Audit Process Builder UI, comparing results is not supported for Task categories of type Discover sensitive data and Security Assessment. Workaround: To show the Results view correctly without the compare option, enable the legacy Audit Process Builder UI with the following command: grdapi modify_guard_param paramName=LEGACY_AUDIT_PROCESS_ENABLED paramValue=1 |
| Audit Process Builder | GRD-136914 | For an audit process with Calculate Embedding enabled, the Options drop-down list corresponding to an already mapped ticket in the AI Recommendation view does not open when clicked. Workaround: To complete this flow, enable the legacy Audit Process Builder UI with the following command: grdapi modify_guard_param paramName=LEGACY_AUDIT_PROCESS_ENABLED paramValue=1 |
| Audit Process Builder | GRD-136924 | The Respond link in the Ticket Matching popup does not perform an action when clicked. Workaround: To complete this flow, enable the legacy Audit Process Builder UI with the following command: grdapi modify_guard_param paramName=LEGACY_AUDIT_PROCESS_ENABLED paramValue=1 |
| Audit Process Builder | GRD-137114 | Event and Additional columns are missing in new Audit Process Builder user interface. Workaround: To add a new column or events, enable the legacy Audit Process Builder UI with the following command: grdapi modify_guard_param paramName=LEGACY_AUDIT_PROCESS_ENABLED paramValue=1 The columns added within the legacy UI will then appear in the new UI results. |
| Backup | GRD-135933 | When a backup central manager (Aggregator) is converted to a primary central manager, the conversion process appears to complete successfully. However, the UI continues to display a rotating/progress indicator indefinitely and does not automatically exit the operation. A fix will be available in an upcoming release. |
| Long term retention | GRD-136393 | The long term retention ingestion error "Not authorized: {"error":"invalid_token","error_description":"Invalid access token"}" might occur on the central manager when the Guardium UI on the long term retention app node is restarted. Workaround: The error will persist until the central manager UI is restarted by using the restart gui command. |
| Patch installation | GRD-135760 | Patch installation might fail during upgrade if the environment contains custom reports named Report Summary, Report Statistics, or Workload Replay Users - credentials. When this issue occurs, the patch installation is aborted, and the upgrade does not complete successfully. Workaround: Prior to installing the patch, verify whether any custom reports exist with the names Report Summary, Report Statistics, or Workload Replay Users - credentials. If found, rename the custom reports to unique names before starting the patch installation. After the patch installation completes successfully, the custom reports can be renamed as needed, provided no naming conflict exists. A permanent fix is planned for a future release to prevent patch installation failures caused by report name conflicts with predefined reports. |
| Patch installation | GRD-136546 | Automated patch download service does not currently download Guardium Database Protection Service (DPS) updates. A fix will be available in an upcoming release. |
| Real-time Trust Evaluator | GRD-136963 | When the time frame is changed in the Real-time Trust Evaluator user interface, the following error appears: "Cannot read properties of undefined (reading 'length')”. All available data can be viewed, but cannot be filtered based on time frame. A fix will be available in an upcoming release. |
| Universal connector | GRD-135482 | Cross‑machine backup and restore is not supported for central manager deployments with Kafka nodes. A backup taken on one machine cannot be restored on a different machine if the system contains Kafka components. |
| Universal connector | GRD-136015 | After upgrading to 12.2.4 (GPU 12.0p7240), the universal connector project ID does not appear within name on S-TAP Status report or Resource Deployment interface. A fix will be available in an upcoming release. |
| Universal connector | GRD-136024 | After upgrading to 12.2.4 (GPU 12.0p7240), an inactive S-TAP entry might appear for the CockroachDB over Syslog Logstash universal connector. Workaround: To remove the inactive S-TAP, run the following command: grdapi delete_inactive_stap |
| Vulnerability Assessment | The GET /assessments API returns all entries (both executable assessments and non-executable templates) by default. If you use automated scripts to fetch assessments and trigger executions, you might inadvertently retrieve templates if your automation scripts are not updated. Attempting to execute a template might fail. Workaround: Existing automation scripts that list assessments for execution must be updated to include the filter parameter isTemplate=false to retrieve only runnable security assessments. |
Was this topic helpful?
Document Information
Modified date:
09 November 2026
UID
ibm17288587