---
title: "TigerGraph DB Release Notes"
description: "Release notes for TigerGraph 4.3"
component: "tigergraph-server"
version: "4.3"
module: "release-notes"
html_url: "/tigergraph-server/4.3/release-notes/"
canonical_url: "https://www.tigergraph.com/docs/tigergraph-server/4.3/release-notes/"
markdown_url: "https://www.tigergraph.com/docs/tigergraph-server/4.3/release-notes/index.md"
---

[View as HTML](https://www.tigergraph.com/docs/tigergraph-server/4.3/release-notes/)

# TigerGraph DB Release Notes

Table of Contents

* [Key New Features](https://www.tigergraph.com/docs/tigergraph-server/4.3/release-notes/index.md#_key_new_features)
* [Detailed List of New and Modified Features](https://www.tigergraph.com/docs/tigergraph-server/4.3/release-notes/index.md#_detailed_list_of_new_and_modified_features)  
   * [System Management Enhancements](https://www.tigergraph.com/docs/tigergraph-server/4.3/release-notes/index.md#_system_management_enhancements)  
   * [Security and Access Control Enhancements](https://www.tigergraph.com/docs/tigergraph-server/4.3/release-notes/index.md#_security_and_access_control_enhancements)  
   * [Output to Cloud Enhancements](https://www.tigergraph.com/docs/tigergraph-server/4.3/release-notes/index.md#_output_to_cloud_enhancements)  
   * [API Enhancements](https://www.tigergraph.com/docs/tigergraph-server/4.3/release-notes/index.md#_api_enhancements)  
   * [Query Language Enhancements](https://www.tigergraph.com/docs/tigergraph-server/4.3/release-notes/index.md#_query_language_enhancements)  
   * [Data Streaming/Connector Enhancements](https://www.tigergraph.com/docs/tigergraph-server/4.3/release-notes/index.md#_data_streamingconnector_enhancements)  
   * [GraphStudio, Admin Portal, and Insights](https://www.tigergraph.com/docs/tigergraph-server/4.3/release-notes/index.md#_graphstudio_admin_portal_and_insights)
* [Fixed issues](https://www.tigergraph.com/docs/tigergraph-server/4.3/release-notes/index.md#_fixed_issues)  
   * [Fixed and Improved in 4.3.0-rc2](https://www.tigergraph.com/docs/tigergraph-server/4.3/release-notes/index.md#_fixed_and_improved_in_4_3_0_rc2)  
   * [Fixed and Improved in 4.3.0-rc1](https://www.tigergraph.com/docs/tigergraph-server/4.3/release-notes/index.md#_fixed_and_improved_in_4_3_0_rc1)
* [Known Issues and Limitations](https://www.tigergraph.com/docs/tigergraph-server/4.3/release-notes/index.md#_known_issues_and_limitations)  
   * [Compatibility Issues](https://www.tigergraph.com/docs/tigergraph-server/4.3/release-notes/index.md#_compatibility_issues)  
   * [Deprecations and Removals](https://www.tigergraph.com/docs/tigergraph-server/4.3/release-notes/index.md#_deprecations_and_removals)
* [Release notes for previous versions](https://www.tigergraph.com/docs/tigergraph-server/4.3/release-notes/index.md#_release_notes_for_previous_versions)

[TigerGraph Server 4.3.0-rc2 Preview](https://dl.tigergraph.com/?tab=enterprise) was released on October 20, 2026.

[TigerGraph Server 4.3.0-rc1 Preview](https://dl.tigergraph.com/?tab=enterprise) was released on July 8, 2026.

> [!NOTE]
> TigerGraph 4.3.0-rc1 is the first release candidate (rc) preview build of TigerGraph 4.3.0\. TigerGraph 4.3's feature set builds upon the capabilities introduced in 4.2.2.

## Key New Features

* **[Mutual TLS (mTLS) Authentication](https://www.tigergraph.com/docs/tigergraph-server/4.3/security/encrypting-connections.md)**: Enables both the client and server to authenticate each other using certificates, improving connection security for external applications and services.
* **[Kerberos SSO Authentication](https://www.tigergraph.com/docs/tigergraph-server/4.3/user-access/sso-with-kerberos.md)**: Enables Single Sign-On (SSO) using Kerberos for seamless and secure user authentication.  
   * Supports ticket-based authentication using Kerberos  
   * Integrates with existing SSO configurations alongside SAML and OIDC  
   * Supports role mapping using proxy groups for flexible access control
* **[NULL Value Support](https://www.tigergraph.com/docs/gsql-ref/4.3/ddl-and-loading/null-value.md)**: Allows vertex and edge attributes defined as `NULLABLE` to accept `NULL` values.  
   * Enables loading of `NULL` values for primitive and collection data types  
   * Supports `NULL` value ingestion through loading jobs and DML statements  
   * Allows `NULL` values to be returned in query results
* **[Load Data from Apache Iceberg (Preview)](https://www.tigergraph.com/docs/tigergraph-server/4.3/data-loading/load-from-iceberg.md)**: Load data from Iceberg-based data lakehouses using a built-in connector with support for Iceberg REST Catalogs and S3 or MinIO storage backends.
* **[Proxy User Management](https://www.tigergraph.com/docs/tigergraph-server/4.3/user-access/user-management.md#_show_proxy_users)**: Proxy users can now be explicitly created, dropped, and listed, rather than being created implicitly at **[first login](https://www.tigergraph.com/docs/tigergraph-server/4.3/API/gsql-endpoints.md#_create_a_proxy_user)**. This allows administrators to pre-provision and manage proxy user accounts as part of standard user lifecycle management.
* **[Audit Log Improvements](https://www.tigergraph.com/docs/tigergraph-server/4.3/troubleshooting/audit-log.md)**: Enhances GSQL audit logging for easier parsing and traceability.  
   * Added `System.Audit.DiscreteJsonFormat` to print each entry as a standalone JSON object for easier parsing  
   * Added new fields for actions, objects, graphs, and REST/GSQL request details  
   * Removed `databaseName` from the log header by default, with an option to re-enable it
* **[CRR Monitoring](https://www.tigergraph.com/docs/tigergraph-server/4.3/cluster-and-ha-management/crr-monitoring.md)** and **[Simplified DR Failover](https://www.tigergraph.com/docs/tigergraph-server/4.3/cluster-and-ha-management/fail-over.md)**: Added CRR status monitoring and simplified DR failover for faster recovery.  
   * Introduced `gadmin crr status` for CRR replication and replay lag metrics  
   * Consolidated DR failover into a single `gadmin crr stop --promote` command  
   * Introduced **[fast-switch](https://www.tigergraph.com/docs/tigergraph-server/4.3/cluster-and-ha-management/fail-over.md#_principle_checkpoint_validation_for_fast_switch)** to convert the former Primary cluster into the new DR cluster

## Detailed List of New and Modified Features

### System Management Enhancements

* Improved **[proxy user management](https://www.tigergraph.com/docs/tigergraph-server/4.3/user-access/user-management.md#_show_proxy_users)** by introducing support to create, drop, and view proxy users directly, providing better control over externally authenticated users.
* New **[open metric](https://www.tigergraph.com/docs/tigergraph-server/4.3/API/built-in-endpoints.md#_license_expiration_metric)** `tigergraph_license_days_left` for days remaining until license expiration.
* Added support for **[Amazon Linux 2023](https://www.tigergraph.com/docs/tigergraph-server/4.3/installation/hw-and-sw-requirements.md#_certified_operating_systems)** and **[Ubuntu 24.04](https://www.tigergraph.com/docs/tigergraph-server/4.3/installation/hw-and-sw-requirements.md#_certified_operating_systems)**.  
   * Installation on Ubuntu 24.04 and later requires the `binutils` package.
* GSQL audit-log improvements with **[new configuration](https://www.tigergraph.com/docs/tigergraph-server/4.3/troubleshooting/audit-log.md#_configuration_parameters)** `System.Audit.DiscreteJsonFormat` and additional **[log fields](https://www.tigergraph.com/docs/tigergraph-server/4.3/troubleshooting/audit-log.md#_gsql_service_audit_log_fields)** (actionType, objectType, graphName).
* Enhanced **[audit logs](https://www.tigergraph.com/docs/tigergraph-server/4.3/troubleshooting/audit-log.md#_audit_log_format)** by adding a `duration` field to record the execution time of GSQL operations and introducing audit log entries for user logout events initiated from GSQL Shell and GraphStudio.
* Increased the default maximum HTTP request header size from 20 KB to 64 KB to better support large request headers (such as LDAP/SSO scenarios). The new configuration parameter [GSQL.MaxHttpRequestHeaderSizeKB](https://www.tigergraph.com/docs/tigergraph-server/4.3/reference/configuration-parameters.md#_gsql) allows customization.  
   * When set to `0` (default), the system uses the default value of 64 KB.  
   * Requests exceeding the configured limit now return HTTP status `431 Request Header Fields Too Large` instead of `400 Bad Request`.
* **[Query installation logs](https://www.tigergraph.com/docs/gsql-ref/4.3/querying/run-manage-queries.md#_log_output)** now include a completion summary, elapsed time, and a failure report listing any skipped or failed queries. These logs are also shown during a TigerGraph upgrade.
* Added support for **[IAM role-based authentication](https://www.tigergraph.com/docs/tigergraph-server/4.3/backup-and-restore/configurations.md#_configuration_parameters)** and **[region-aware AWS S3 backup and restore](https://www.tigergraph.com/docs/tigergraph-server/4.3/backup-and-restore/configurations.md#_backup_to_aws_s3)**.  
   * New configuration parameter `System.Backup.S3.IAMAuth` enables authentication using an AWS EC2 Instance Profile for S3 backup and restore as an alternative to access keys.  
   * New configuration parameter `System.Backup.S3.Region` specifies the AWS Region used to sign requests to the S3 bucket. This value should match the Region where the S3 bucket is located.
* \[4.3.0-rc2\] Added the **[gadmin backup verify](https://www.tigergraph.com/docs/tigergraph-server/4.3/system-management/management-commands.md#_gadmin_backup_verify)** command to verify the integrity of a backup by validating the checksum of every archive file.  
   * Supports verifying all base backups in an incremental backup chain using the `--chain` option.

### Security and Access Control Enhancements

* **[Mutual TLS (mTLS) Authentication](https://www.tigergraph.com/docs/tigergraph-server/4.3/security/encrypting-connections.md)** enables certificate-based mutual authentication between clients and the server, strengthening connection security for external applications and services.
* **[Internal Kafka TLS Encryption](https://www.tigergraph.com/docs/tigergraph-server/4.3/security/encrypting-connections.md#_configuring_tls_for_internal_kafka)** enables SSL/TLS encryption for data in transit between TigerGraph services and internal Kafka, enhancing security for communications within the cluster.
* Added **[Kerberos](https://www.tigergraph.com/docs/tigergraph-server/4.3/user-access/sso-with-kerberos.md)** as an SSO authentication option, alongside existing SAML, OIDC, and LDAP methods. Added a new endpoint `GET /gsql/v1/sso/authnrequest` to retrieve available SSO authentication methods.
* **[S3 Authentication via AWS Role ARN](https://www.tigergraph.com/docs/gsql-ref/4.3/querying/write-output-to-cloud.md#_use_gsql_session_parameters)**: Added support for AWS Role Assumption when writing query output to S3 storage, enabling authentication via the `s3_assume_role` session parameter as an alternative to AWS access keys.
* **[ACL privilege migrations](https://www.tigergraph.com/docs/tigergraph-server/4.3/user-access/query-privilege-migration.md#_migrate_acl_privileges)** are prevented if the ACL catalog contains the query contents.
* **[SAML SSO](https://www.tigergraph.com/docs/gui/4.3/admin-portal/security/sso.md#_x509_certificate_and_private_key)** now supports full X.509 certificate chains for both Service Provider (SP) and Identity Provider (IdP) certificates. Certificate chains can include server, intermediate, and root certificates in a single uploaded file.
* Added the `Security.JWT.UserClaim` **[configuration parameter](https://www.tigergraph.com/docs/tigergraph-server/4.3/user-access/jwt-token.md#_optional_configurations)** to specify which JWT claim resolves the TigerGraph username during JWT/OIDC authentication.
* Nginx now supports TLS 1.3 hybrid [post-quantum key exchange](https://www.tigergraph.com/docs/tigergraph-server/4.3/security/encrypting-connections.md#_post_quantum_hybrid_tls_key_exchange) (`X25519MLKEM768`) through the bundled OpenSSL 3.5\. This support is enabled by default when SSL is enabled.

### Output to Cloud Enhancements

* Writing **[query output](https://www.tigergraph.com/docs/gsql-ref/4.3/querying/write-output-to-cloud.md)** to S3-compatible storage (such as Ceph, MinIO, and Wasabi) is now supported using a configurable `s3_endpoint`, enabling integration with non-AWS storage systems.
* Added support for specifying the S3 region using the **[s3\_region](https://www.tigergraph.com/docs/savanna/main/graph-development/advanced-features/write2-s3.md)** session parameter when writing **[query output](https://www.tigergraph.com/docs/gsql-ref/4.3/querying/write-output-to-cloud.md)** to S3-compatible storage.

### API Enhancements

* Added a **[REST endpoint GET /gsql/v1/schema/version](https://www.tigergraph.com/docs/tigergraph-server/4.3/API/gsql-endpoints.md#_get_latest_schema_version)** to retrieve the current committed schema version. The endpoint returns the latest schema version as an integer.
* **[RESTPP endpoints /query\_status, /query\_result, /showprocesslist/{graph\_name}, and /showprocesslistall](https://www.tigergraph.com/docs/tigergraph-server/4.3/API/built-in-endpoints.md)** now report query status and results across all server nodes in a distributed cluster, not just the node receiving the request. Use the optional `disallow_redirect` parameter to query only the local node, if desired.
* Added a **[new Informant endpoint](https://www.tigergraph.com/docs/tigergraph-server/4.3/API/built-in-endpoints.md#_get_license_info_and_usage)** `GET /informant/licenseinfo` to retrieve license information and usage.
* Added support for **[gzip-compressed query responses](https://www.tigergraph.com/docs/tigergraph-server/4.3/API/index.md#_compressed_responses)** from RESTPP to the client, reducing transfer size for large results over low-bandwidth connections.
* \[4.3.0-rc2\] Added support for **[zstd-compressed query responses](https://www.tigergraph.com/docs/tigergraph-server/4.3/API/index.md#_compressed_responses)** from RESTPP to the client. Zstd compression can be requested through the RESTPP query endpoint or the GSQL `RUN QUERY` command.
* Added a **[new query routing mode ](https://www.tigergraph.com/docs/tigergraph-server/4.3/system-management/workload-management.md#_query_routing_schemes)** `RESTPP.QueryRouting.Mode = 2` (LocalGPE) to route RESTPP requests directly to the co-located GPE on the same node. This reduces latency for high-QPS workloads by removing an extra network hop.
* \[4.3.0-rc2\] Enhanced the **[/echo RESTPP endpoint](https://www.tigergraph.com/docs/tigergraph-server/4.3/API/built-in-endpoints.md#_echo)** to check the status of a specific GPE by partition and replica, with a configurable response timeout.
* Added a **[new query routing mode ](https://www.tigergraph.com/docs/tigergraph-server/4.3/system-management/workload-management.md#_query_routing_schemes)** `RESTPP.QueryRouting.Mode = 2` (LocalGPE) to route RESTPP requests directly to the co-located GPE on the same node. This reduces latency for high-QPS workloads by removing an extra network hop.
* Added support for **[composite-key IDs](https://www.tigergraph.com/docs/tigergraph-server/4.3/API/built-in-endpoints.md#_composite_key_ids_in_restpp_endpoints)** in the `data_query`, `shortestpath`, and `allpaths` RESTPP endpoints. Composite-key IDs can be specified as JSON objects, arrays, or comma-separated strings.
* Added endpoints to **[list running queries](https://www.tigergraph.com/docs/tigergraph-server/4.3/API/gsql-endpoints.md#_list_running_queries)** and **[list running loading jobs](https://www.tigergraph.com/docs/tigergraph-server/4.3/API/gsql-endpoints.md#_list_running_loading_jobs)** for a specific graph. Each endpoint shows currently running queries or loading jobs, plus a `hasRunning` indicator.

### Query Language Enhancements

* **[INTERPRET QUERY \-mode option](https://www.tigergraph.com/docs/gsql-ref/4.3/querying/query-modes.md)**: Added support for a **[\-mode option](https://www.tigergraph.com/docs/gsql-ref/4.3/querying/run-manage-queries.md#_interpret_a_created_query)** to control how interpreted queries are executed.  
   * `instruction`: Uses a faster execution engine (may not support all features)  
   * `legacy`: Uses the original engine with full feature support  
   * `debug`: Generates debug files for troubleshooting

By default, TigerGraph automatically selects the appropriate mode.

* **[Configuration parameter GSQL.AllowInterpretedQueries](https://www.tigergraph.com/docs/tigergraph-server/4.3/reference/configuration-parameters.md#_gsql)** allows enabling or disabling interpreted queries, helping enforce an installed-queries-only policy in production environments.
* **[Bitwise Accumulators](https://www.tigergraph.com/docs/gsql-ref/4.3/querying/accumulators.md#_bitwiseandaccum_bitwiseoraccum)**: Added support for dynamic-length BitwiseAccums, allowing lengths to be defined using query parameters or variables. Also introduced a `.clear()` function for improved memory management during query execution.
* File objects can now be created with an optional [file permission parameter](https://www.tigergraph.com/docs/gsql-ref/4.3/querying/declaration-and-assignment-statements.md#_file_objects), allowing users to specify permissions using a Linux octal-encoded file permission code.

### Data Streaming/Connector Enhancements

* **[Load data from Apache Iceberg](https://www.tigergraph.com/docs/tigergraph-server/4.3/data-loading/load-from-iceberg.md)** (Preview) enables loading data from Iceberg-based data lakehouses using SQL-based queries and REST catalog integration.
* Added new **[SSL keystore configurations](https://www.tigergraph.com/docs/tigergraph-server/4.3/data-loading/read-to-spark-dataframe.md#_common_options)**(ssl.keystore, ssl.keystore.type, ssl.keystore.password) for the Spark Connector.
* Spark Connector now supports direct **[upsert of vertices and edges](https://www.tigergraph.com/docs/tigergraph-server/4.3/data-loading/load-from-spark-dataframe.md#_direct_upsert_from_spark_dataframe)** from a Spark DataFrame, without the need to define a GSQL loading job.

### GraphStudio, Admin Portal, and Insights

* Updated access control for the **[Query Monitoring](https://www.tigergraph.com/docs/gui/4.3/admin-portal/monitoring/queries.md#_access_control)** page to use privilege-based access instead of role-based access.  
   * `READ_DATA` privilege controls query visibility across all or specific graphs; users without access see an appropriate error message.  
   * Users with `DELETE_DATA` privilege can abort queries running on a graph.

## Fixed issues

### Fixed and Improved in 4.3.0-rc2

#### Functionality

* Fixed an issue where the Upsert Data API could report an incorrect number of accepted vertices when using atomic mode (CORE-6001).
* Fixed an issue where upgrades could fail when stale graph entries were encountered during role migration (GLE-13658).
* Fixed an issue where upgrades to 4.3.0 could fail when the pre-upgrade check attempted to save catalog changes (GLE-13472).
* Fixed an issue where NGINX and RESTPP failed to start after installing TigerGraph on RHEL 10 (CORE-5931).
* Fixed an issue where loading jobs using Azure Data Lake Storage Gen2 Service Principal authentication failed because the connector required a storage account key instead of using the configured Service Principal credentials (GLE-13380).
* Fixed an issue affecting record consistency following certain schema changes and subsequent GPE rebuild operations (CORE-5917).
* Fixed an issue where query creation could fail when queries used templated C++ UDF return types (GLE-13305).
* Added support for gzip-compressed query responses from RESTPP to the client, reducing data transfer size for large results over low-bandwidth connections.

#### Improvements

* Improved data integrity when stopping TigerGraph services that persist data to storage (TP-10954).

#### Security

* Fixed an issue where data source GET endpoints could return unmasked credential values in configuration responses (GLE-13530).
* Third-party Vulnerabilities NOT impacting TigerGraph:  
Fixed the following security vulnerabilities: CVE-2025-14813, CVE-2026-0636, CVE-2026-106449, CVE-2026-106450, CVE-2026-106452, CVE-2026-106453, CVE-2026-13506, CVE-2026-19032, CVE-2026-25680, CVE-2026-33818, CVE-2026-39821, CVE-2026-39822, CVE-2026-39824, CVE-2026-39827, CVE-2026-39828, CVE-2026-39829, CVE-2026-39830, CVE-2026-39831, CVE-2026-39832, CVE-2026-39833, CVE-2026-39834, CVE-2026-39835, CVE-2026-42055, CVE-2026-42505, CVE-2026-42508, CVE-2026-46595, CVE-2026-46597, CVE-2026-46598, CVE-2026-46600, CVE-2026-46917, CVE-2026-46968, CVE-2026-47010, CVE-2026-47021, CVE-2026-47027, CVE-2026-47059, CVE-2026-47063, CVE-2026-47838, CVE-2026-48142, CVE-2026-49844, CVE-2026-54291, CVE-2026-54399, CVE-2026-54428, CVE-2026-54516, CVE-2026-54517, CVE-2026-54518, CVE-2026-55831, CVE-2026-55833, CVE-2026-55856, CVE-2026-55857, CVE-2026-55858, CVE-2026-5588, CVE-2026-56740, CVE-2026-56741, CVE-2026-56746, CVE-2026-56852, CVE-2026-56853, CVE-2026-56854, CVE-2026-56855, CVE-2026-56857, CVE-2026-56858, CVE-2026-56859, CVE-2026-56860, CVE-2026-56862, CVE-2026-56866, CVE-2026-59889, CVE-2026-59901, CVE-2026-59903, CVE-2026-59949, CVE-2026-60147, CVE-2026-62574, CVE-2026-64607, CVE-2026-65182, CVE-2026-65905, CVE-2026-68497, CVE-2026-68525, CVE-2026-75595, CVE-2026-75596, CVE-2026-78659, CVE-2026-78660, CVE-2026-78662, CVE-2026-78663, CVE-2026-78667, CVE-2026-78669, CVE-2026-83557, CVE-2026-86597, CVE-2026-8763, CVE-2026-89407, CVE-2026-89425, CVE-2026-91776, CVE-2026-91777, CVE-2026-94439, CVE-2026-94440, and CVE-2026-97031.  
Third-party Vulnerability impacting TigerGraph: None

### Fixed and Improved in 4.3.0-rc1

#### Functionality

* Fixed incorrect latency values in RESTPP logs when a request returned an error (CORE-5046).
* Fixed an issue where the username was not displayed on the home page after SSO login (APPS-4376).
* Fixed an issue where `/query_status`, `/query_result`, `/showprocesslist/{graph_name}`, and `/showprocesslistall` did not return complete results when requests were routed to different RESTPP nodes in a cluster (CORE-5200).
* Fixed an issue where style configuration and the detail panel did not update correctly after selecting a vertex in GraphStudio Explore Graph (APPS-4369).
* Fixed an issue where upgrade runtime logs displayed misleading completion messages before the upgrade process had fully completed (TP-8429).
* Fixed an issue where GUI CORS settings could not be configured from the Admin Portal (APPS-3602).
* Fixed an issue where tooltips in GraphStudio could be partially hidden when hovering near the edge of the viewport (APPS-4378).
* Fixed an issue where log access in the Admin Portal required both `APP_ACCESS_LOG` and `APP_ACCESS_DATA` privileges instead of `APP_ACCESS_LOG` exclusively (APPS-3253).
* Fixed an issue where binary files were written during segment rebuild even when the segment had already been deleted (CORE-4578).
* Fixed an issue where repeated backups took progressively longer despite minimal data growth, caused by inefficient processing of schema changes (CORE-5000).
* Fixed an issue where failure signal handling in engine services prevented expected core dump generation (CORE-5061).
* Fixed an issue where partition configuration recovery could result in schema inconsistencies when `config.yaml` was missing but segment data existed (CORE-5322).
* Fixed an issue where schema change validation failures provided unclear error messages during DSCDrain or DSCValidation (GLE-9913).
* Fixed an issue where certain `PRINT TO_CSV` syntax patterns were not supported when printing query results (GLE-10524).
* Fixed an issue where Kafka retention could be blocked by a remote segment associated with a deleted vertex type (CORE-5409).
* Fixed an issue where password policies intended for native users were incorrectly enforced on LDAP proxy users (GLE-9533).
* Added the `Security.JWT.JWKS.URL` configuration parameter to fetch JWT certificates using the Key ID (`kid`) from a JWKS URL, ensuring compliance with the JWKS standard (GLE-10289).
* Fixed an issue where `LastSuccessLogin` and `NextValidLogin` were not updated after successful authentication of LDAP proxy users (GLE-10646).
* Fixed an issue where Spark JDBC connections could experience unexpected socket timeouts when `queryTimeout` was not passed to the TigerGraph JDBC driver (TP-8385).
* Fixed an issue where requests on port `14240` could not be routed directly to a specific RESTPP node when direct node-level access was required (TP-9166).
* Fixed an issue where certain upgrade validation checks were performed after upgrade instead of during pre-upgrade checks (GLE-10562).
* Fixed an issue that caused intermittent errors during legacy token validation (GLE-11683).
* Fixed an issue where token generation could become unresponsive during schema change operations by optimizing the workflow (GLE-11699).
* Fixed an issue where the system would throw a `NullPointerException` and fail to create or install a query during code validation (GLE-10502).

#### Improvements

* Improved security for namespace-scoped TigerGraph Operator installations by separating required cluster roles and namespace roles (TP-7857).
* Improved file permission handling by supporting string literals in file variable declarations used with `PRINT TO_CSV` (GLE-10956).

#### Security

* Refined loading job summary output by replacing detailed error information with line numbers for invalid entries (TP-8628).
* Improved configuration security by masking AWS credential values in `gadmin` outputs (TP-8533).
* Third-party Vulnerabilities NOT impacting TigerGraph:  
Fixed the following security vulnerabilities: CVE-2024-31033, CVE-2024-6763, CVE-2024-8184, CVE-2024-9823, CVE-2025-11143, CVE-2025-67030, CVE-2025-67721, CVE-2025-68161, CVE-2026-1002, CVE-2026-22007, CVE-2026-22013, CVE-2026-22016, CVE-2026-22018, CVE-2026-22021, CVE-2026-22732, CVE-2026-22735, CVE-2026-22737, CVE-2026-2332, CVE-2026-24051, CVE-2026-24281, CVE-2026-24308, CVE-2026-24734, CVE-2026-24880, CVE-2026-25679, CVE-2026-25854, CVE-2026-27139, CVE-2026-27142, CVE-2026-27145, CVE-2026-29145, CVE-2026-29146, CVE-2026-29181, CVE-2026-32280, CVE-2026-32281, CVE-2026-32282, CVE-2026-32283, CVE-2026-32288, CVE-2026-32289, CVE-2026-3293, CVE-2026-32990, CVE-2026-33186, CVE-2026-33810, CVE-2026-33811, CVE-2026-33814, CVE-2026-33870, CVE-2026-33871, CVE-2026-34268, CVE-2026-34282, CVE-2026-34478, CVE-2026-34480, CVE-2026-34483, CVE-2026-34487, CVE-2026-34500, CVE-2026-39820, CVE-2026-39823, CVE-2026-39825, CVE-2026-39826, CVE-2026-39836, CVE-2026-39883, CVE-2026-41284, CVE-2026-41293, CVE-2026-41417, CVE-2026-42198, CVE-2026-42498, CVE-2026-42499, CVE-2026-42504, CVE-2026-42507, CVE-2026-42577, CVE-2026-42578, CVE-2026-42579, CVE-2026-42580, CVE-2026-42581, CVE-2026-42583, CVE-2026-42584, CVE-2026-42585, CVE-2026-42587, CVE-2026-42945, CVE-2026-43512, CVE-2026-43513, CVE-2026-43514, CVE-2026-43515, CVE-2026-44249, CVE-2026-45205, CVE-2026-45416, CVE-2026-45536, CVE-2026-45673, CVE-2026-45674, CVE-2026-47244, CVE-2026-47691, CVE-2026-48043, CVE-2026-50010, CVE-2026-50020, CVE-2026-50560, CVE-2026-54512, CVE-2026-54513, CVE-2026-54514, CVE-2026-54515, and CVE-2026-6860.  
Third-party Vulnerability impacting TigerGraph: None

## Known Issues and Limitations

| Description | Found In | Workaround | Fixed In |
| --- | --- | --- | --- |
| GraphStudio may over-enforce `READ_DATA` access controls, preventing users from executing path/search built-ins in Explore Graph when the traversal includes intermediate vertex or edge types for which they do not have `READ_DATA` access. | 4.2.3 | Use GSQL as a workaround, as it supports type-level `READ_DATA` access controls and is not subject to this over-enforcement. |  |
| The presence of a forward slash (`/`) in a vertex ID can prevent certain operations, including editing vertex attributes, deleting vertices in Explore Graph, and adding edges to or from vertices containing `/`. In some cases, the UI may also freeze. | 4.2.2 | When calling RESTPP endpoints that include vertex IDs containing URL characters, percent-encode the characters in the vertex ID (for example, `%2F` for `/`). There is no workaround for the other affected operations. | TBD |
| When performing a rolling upgrade from a version between 4.2.0 and 4.2.2 to a later 4.2.x version with `Nginx.SSL.Enable=true`, the upgrade may fail while blocking GSQL long-running operations due to an internal HTTPS request failure. | 4.2.0\~4.2.2 | Since rolling upgrade is a preview feature in 4.2.x, users with `Nginx.SSL.Enable=true` should use a regular upgrade as the recommended upgrade path. Regular upgrade works with SSL enabled and does not require disabling any security configuration. If users still choose to use rolling upgrade, temporarily disable `Nginx.SSL.Enable`, apply the configuration, and restart GSQL and NGINX services before performing the rolling upgrade. After the upgrade completes successfully, re-enable SSL, apply the configuration, and restart GSQL and NGINX services. | 4.2.3 |
| If a non-procedural query has a syntax error, the GSQL interpreter ignored the invalid portion and executed the partial query before the error, without raising an error. | 4.2.0 | Check the full query before accepting it. | 4.2.1 |
| A NullPointerException occurs when performing a code check for queries using statements other than a = vt.\* or a = {vt.\*}, causing query creation to fail. | 4.1.3 | TBD | TBD |
| When `pulldict` fails, an empty debug log is generated, as the log level for debug is not enabled by default. | 4.1.3 | TBD | TBD |
| After upgrading, the system fails to detect `to_string()` in the UDF file, leading to query compilation errors. This issue occurs because the system doesn't report parsing errors during file uploads. | 4.1.3 | TBD | TBD |
| When using `set(index, value)` and `flip(index)` with BitwiseOrAccum<1000>, the task fails due to lack of support for bit operators `(&, \|, ~)` in bitwise accumulation. | 4.1.3 | TBD | TBD |
| Using [.flip()](https://www.tigergraph.com/docs/gsql-ref/4.3/querying/accumulators.md#_bitwiseandaccum_bitwiseoraccum) on `BitwiseAndAccum` or `BitwiseOrAccum` inside a `PRINT` block may produce different results in UDF mode versus Single/Distributed mode. | 4.1.3 | Move the `.flip()` logic to the POST-ACCUM block for consistent behavior. | TBD |
| After a cluster expansion, the GPE service may remain in the warmup state. | 4.1.1 | If this happens, run `gadmin restart gse -y` to release the GPE. | TBD |
| When upgrading or performing cross-version database export/import from a version earlier than 4.1.0 to 4.1.0 or later, existing graph-level secrets are migrated to global-level secrets, and tokens associated with those secrets are removed. Cross-version database export/import across this version boundary is not recommended. | 4.1.0+ | TBD | TBD |
| The `EXECUTE_QUERY` privilege is not enforced on RESTPP endpoints. That is, users who lack `EXECUTE_QUERY` can still run a query via `POST /restpp/query/{graph_name}/{query_name}` | 4.1 | Use legacy methods for access control: Define separate graphs which span the same data but have different queries and users. | TBD |
| If a RESTPP request is for a graph operation and thus sent to the GPE then fails inside the GPE, the RESTPP will interpret the response from the GPE as success and report SUCCEED in the audit log. | 4.1 | Use a `/gsql` endpoint instead of a `/restpp` endpoint. | TBD |
| When [upgrading](https://www.tigergraph.com/docs/tigergraph-server/4.3/installation/upgrade.md#_upgrading_from_3_x), possible permission error for destination folder. | 3.10.1 | Manually grant permission to `/var/tmp` | TBD |
| [Export](https://www.tigergraph.com/docs/tigergraph-server/4.3/backup-and-restore/database-import-export.md) does not include LDAP proxy groups | 3.9+ | Manually recreate the proxy groups on the imported database. |  |

### Compatibility Issues

> [!NOTE]
> These Release Notes describe changes in this release.
> 
> For upgrade checks across versions, see the [Compatibility and Migration](https://www.tigergraph.com/docs/home/compatibility/index.md) pages.

| Description | Version Introduced |
| --- | --- |
| Many REST API endpoints were updated, including consolidation, path prefix changes, and token authentication support. See the [REST API reference](https://www.tigergraph.com/docs/tigergraph-server/4.1/API/index.md) page. | v4.1.0 |
| To apply a [File Input Policy](https://www.tigergraph.com/docs/tigergraph-server/4.3/security/gsql-file-input-policy.md) or [File Output Policy](https://www.tigergraph.com/docs/tigergraph-server/4.3/security/file-output-policy.md) change, now both `gsql` and `restpp` servers must be restarted: `gadmin restart gsql restpp -y` | v4.1.3, v4.2.0 |
| The [\--incremental option for backup](https://www.tigergraph.com/docs/tigergraph-server/4.3/backup-and-restore/incremental-backup.md) now performs a true incremental backup instead of a differential backup. | v4.2.0 |
| In [CDC messages](https://www.tigergraph.com/docs/tigergraph-server/4.3/system-management/change-data-capture/cdc-message-example.md#_message_examples), the format of **tuple values** has changed. | v4.2.0 |
| SelectVertex() may not be used with a relative filepath but previously this was not enforced. It is now enforced. | v4.2.0 |
| The 'graph' field is now included in [CDC messages](https://www.tigergraph.com/docs/tigergraph-server/4.3/system-management/change-data-capture/cdc-message-example.md#_message_examples) generated by the TigerGraph CDC service. | v3.11.0, v4.1.1 |
| In [CDC messages](https://www.tigergraph.com/docs/tigergraph-server/4.3/system-management/change-data-capture/cdc-message-example.md#_message_examples), the format of **map values** has changed. | v3.11.0, v4.1.1 |
| A full export package now includes access policies and template queries. | v4.1.0 |
| Users could encounter file input/output policy violations when upgrading a TigerGraph version. See [Input policy backward compatibility.](https://www.tigergraph.com/docs/tigergraph-server/4.3/security/gsql-file-input-policy.md#_backward_compatibility) | v3.10.0 |
| When a PRINT argument is an expression, the output uses the expression as the key (label) for that output value. To better support Antlr processing, PRINT now removes any spaces from that key. For example, `count(DISTINCT @@ids)` becomes `count(DISTINCT@@ids)`. | v3.9.3+ |
| Betweenness Centrality algorithm: `reverse_edge_type (STRING)` parameter changed to `reverse_edge_type_set (SET<STRING>)`, to be consistent with `edge_type_set` and similar algorithms. | v3.9.2+ |
| For vertices with string-type primary IDs, vertices whose ID is an empty string will now be rejected. | v3.9.2+ |
| The default mode for the Kafka Connector changed from EOF="false" to EOF="true". | v3.9.2+ |
| The default retention time for two monitoring services `Informant.RetentionPeriodDays` and `TS3.RetentionPeriodDays` has reduced from 30 to 7 days. | v3.9.2+ |
| The filter for `/informant/metrics/get/cpu-memory` now accepts a list of ServiceDescriptors instead of a single ServiceDescriptor. | v3.9.2+ |
| Some user-defined functions (UDFs) may no longer be accepted due to [increased security screening](https://www.tigergraph.com/docs/tigergraph-server/4.3/security/index.md#_udf_file_scanning). * UDFs may no longer be called `to_string()`. This is now a built-in GSQL function. * UDF names may no longer use the `tg_` prefix. Any user-defined function that began with `tg_` must be renamed or removed in `ExprFunctions.hpp`. | v3.9+ |

### Deprecations and Removals

| Description | Deprecated | Removed |
| --- | --- | --- |
| The `--meta` option for backup is no longer needed because metadata is now included automatically with backup files. | 3.9.2 | 4.2.0 |
| Streaming connector for external Kafka (3.6 to 3.9.2 version) | 3.9.3 | 4.2.0 |
| The format for tuple structures in CDC messages will change in a future version. The future format is likely to be similar to the[new format for maps](https://www.tigergraph.com/docs/tigergraph-server/4.3/system-management/change-data-capture/cdc-message-example.md#_cdc_message_with_type_edge). | 4.1.1 | 4.2 |
| Access Control Lists (ACLs) are no longer supported. When upgrading from 3.x to 4.x, [ACL privileges will be automatically migrated to object-based privileges](https://www.tigergraph.com/docs/tigergraph-server/4.3/user-access/query-privilege-migration.md). | 4.1.0 | 4.1.0 |
| The use of plaintext tokens in [authentication](https://www.tigergraph.com/docs/tigergraph-server/4.3/API/authentication.md) is deprecated. Use [OIDC JWT Authentication](https://www.tigergraph.com/docs/tigergraph-server/4.3/user-access/jwt-token.md) instead. | 3.10.0 | TBD |
| **Vertex-level Access Control** (VLAC) and VLAC Methods are removed and are no longer available. | 3.10.0 | 4.1.0 |
| The command `gbar` is removed and is no longer available. It has been replaced by `gadmin backup`. | 3.7 | 3.10 |
| [Spark Connection via JDBC Driver](https://www.tigergraph.com/docs/tigergraph-server/4.3/data-loading/spark-connection-via-jdbc-driver.md) is now deprecated and will no longer be supported. | 3.10.0 | TBD |
| `Build Graph Patterns` is deprecated and will not be updated or supported and instead we are focusing on [Insights](https://www.tigergraph.com/docs/insights/4.3/widgets/index.md) as the tool of choice for building visual queries. | 3.9.3 | TBD |
| Kubernetes classic mode (non-operator) is deprecated. | 3.9 | TBD |
| The `WRITE_DATA` RBAC privilege is deprecated. | 3.7 | 4.1 |

## Release notes for previous versions

* [Release notes - TigerGraph 4.2](https://www.tigergraph.com/docs/tigergraph-server/4.2/release-notes/index.md)
* [Release notes - TigerGraph 4.1](https://www.tigergraph.com/docs/tigergraph-server/4.1/release-notes/index.md)
* [Release notes - TigerGraph 3.11](https://www.tigergraph.com/docs/tigergraph-server/3.11/release-notes/index.md)
* [Release notes - TigerGraph 3.10](https://www.tigergraph.com/docs/tigergraph-server/3.10/release-notes/index.md)
