Resolved issues
Resolved issues release notes for 26.1.x.
26.1.0-1
Updated 2/26/2026
| Issue Key | Application Module | Description |
|---|---|---|
| 5181096 | DDL - Table | This fix resolves an issue where temporary relation (TempRel) decoding could lead to data corruption, specifically affecting string data within recursive Common Table Expressions (CTEs). The fix ensures proper handling of character encoding and VARCHAR length constraints, preventing the occurrence of non-UTF8 data and oversized strings, thereby restoring data integrity and eliminating the need for performance-impacting workarounds. |
| 5196883 | Installation Program |
Previously, the install_vertica and update_vertica scripts would fail to correctly apply the --ssh-password option, leading to unresponsiveness or hanging during installations and upgrades when passwordless SSH was not configured. This fix ensures that the --ssh-password option is now properly recognized and utilized, allowing for successful script execution without requiring temporary passwordless SSH. |
| 5215373 | Node Management Agent, Vcluster | This update addresses multiple security vulnerabilities, including critical and high severity CVEs, identified in the Golang binaries shipped with Vertica 26.1.0-0 container images. These vulnerabilities previously impacted deployment in Kubernetes environments utilizing vulnerability-based admission controllers. The fix enhances the security posture of Vertica container images and ensures compliance for seamless integration and deployment. |
26.1.0-0
Updated 1/30/2026
| Issue Key | Application Module | Description |
|---|---|---|
| 4341124 | Catalog Engine | An issue was discovered with Vertica clusters, where a node attempting to join would fail with an 'Invalid buffer enlargement request size' error during the cluster invitation process, specifically during catalog serialization. This issue has been resolved, and the fix ensures successful node integration and cluster stability. |
| 4348762 | UI - Management Console | This fix addressed an issue where Management Console (MC) was sending spurious 'Failed Query Number' email alerts and failing to provide rejection details for certain queries, such as EXPORT TO VERTICA statements, leading to false positives and unnecessary email notifications. This issue has been resolved. |
| 4404849 | Client Drivers - Python | Fixed an issue that occurred when users attempted to import the stumpy Python library within User Transform Functions (UTDFs). With this fix, users can now successfully import and utilize the stumpy library and its dependencies within their Python UTDFs. |
| 4524035 | System: Performance | Query Performance Improvement for RLE-Encoded Data: Addresses a performance degradation issue that was observed, specifically for queries involving tables with RLE and non-RLE segmented columns. This fix optimizes the query planner's handling of data subdivisions, resulting in improved execution times for affected queries. |
| 4536627 | EON | This release addresses an issue where cluster nodes experienced frequent crashes due to out-of-memory (OOM) errors. The problem was observed across primary and secondary subclusters, with RSS memory usage growing constantly, even on idle secondary subclusters. The fix resolves a memory leak that was affecting all hosts, regardless of hardware specifications or operating system. |
| 4812173 | Security | Addressed a security vulnerability (ID: 4812173) related to an outdated WSGIServer component (version 0.5) identified during security scans on AIOps servers, specifically impacting Vertica. This update enhances the system's security posture. |
| 4830176 | Optimizer | Previously when comparing string literals cast to array with LIKE ANY/ALL (i.e. select 'foo' like any ('bar'::Array[varchar]);) Vertica would improperly locate string array data in memory and cause a fatal crash. This no longer happens. |
| 4847984 | System: Performance | We’ve optimized the behavior of the STRPOS function to significantly improve performance in specific scenarios. What changed: Previously, all inputs to STRPOS were converted to UTF-16 to leverage the ICU (International Components for Unicode) library for string comparison. While ICU provides robust support for complex locale-aware comparisons, this conversion introduced overhead—especially for simple use cases. Now, for simple locales with 1-to-1 character mappings (such as en_US, de_DE, and other locales where each character maps directly between UTF-8 and UTF-16 without requiring normalization or multi-codepoint handling), STRPOS uses a UTF-8 based comparison. This avoids the need for conversion to UTF-16 and bypasses the ICU library entirely, resulting in much faster execution. |
| 4862319 | Optimizer | Internal Optimizer Error with Complex View Joins:Resolved an issue where UPDATE statements, when joining with multi-level views (views referencing other views and tables across different schemas), could incorrectly trigger an 'Internal Optimizer Error (11)'. Update queries involving these complex view structures now execute as expected without error. |
| 4864875 | Optimizer | Database Stability Improvement for LIKE ANY Queries: A critical issue that could cause Vertica databases to crash when executing queries containing the pattern LIKE ANY ('%string%'::ARRAY[Varchar]) has been resolved. This fix enhances database stability and prevents unexpected outages, particularly for complex queries involving explicit array casting with LIKE ANY. |
| 4880668 | DDL - Table |
Fixed an issue where functions, such as regexp_substr, used within stored procedures would incorrectly return NULL when the stored procedure was executed via a schedule. This behavior was observed despite the functions working as expected when the stored procedure was called directly or through EXECUTE_TRIGGER. |
| 4917190 | Optimizer | An issue with performance degradation was observed in queries utilizing WITH clauses when migrating from Vertica 10.x to newer versions (24.x and 25.x) in an EON mode database environment. This issue has been resolved. |
| 4990806 | Admin Tools |
Fixed an issue where the fjsonparser() function in FlexTableLib became incompatible (SDK version mismatch) after upgrading to Vertica 25.3. |
| 4990862 | Vcluster |
Vcluster CLI now supports kill_host and kill_node commands, enabling users to terminate database processes on specified hosts directly from the command line. This enhancement is part of the ongoing effort to transition Vcluster into a comprehensive replacement for AdminTools. |
| 5001398 | Client Drivers - JDBC | The Vertica JDBC driver has been updated to enable full support for TLS 1.3, ensuring compliance with security requirements. |
| 5008290 | Security |
Introduced a new database parameter, OAuth2JITConflictPolicy, to control OAuth2 JIT login for existing users. MERGE, the default, allows OAuth2 login for existing Vertica users and grants them the appropriate auth method. This is identical to the existing behavior. If set to IGNORE then existing users require an OAuth2 client authentication granted to log in with an OAuth2 token, no automatic granting is performed. Users with psuedosuperuser are always treated as if OAuth2JITConflictPolicy is set to IGNORE, ie. they can only use authentication methods that have been explicitly granted. |
| 5022179 | Backup/DR |
Previously, customers attempting to replicate data from Azure-based Vertica clusters to on-premise environments experienced failures with an "Error deserializing objects" (Code: 3196) during the REPLICATE command. This fix resolves the underlying deserialization problem, ensuring successful and reliable data synchronization between Vertica clusters. |
| 5028767 | UI - Management Console | Addressed an issue where Vertica agents failed to start, leading to Management Console dashboards not loading and 'Error occurred while getting database thresholds null'.The fix ensures agents start successfully, restoring full Management Console functionality. |
| 5040970 | License | Resolved an issue where the audit system inaccurately reported data utilization, leading to inflated license usage figures. The audit now correctly reflects actual data size. |
| 5046044 | Data Networking |
Resolved an issue where Vertica databases, after upgrading to version 25.3.0-2, would experience hangs, causing all SQL queries on nodes to become stuck. This instability was particularly observed when TLS 1.3 was configured (ALTER DATABASE DEFAULT SET MinTLSVersion = 3;). This fix addresses the database hanging behavior, improving overall system stability post-upgrade. |
| 5051561 | UI - Management Console | Resolved an issue where the "Upload From File" caption would disappear, appearing as a blank blue area, after uploading a query file in the Database Designer (DBD). This display anomaly was particularly observed following an upgrade to MC version 25.2.0-3, and no longer occurs. |
| 5051975 | UI - Management Console |
The Management Console has been updated to no longer query the EnableSSL configuration parameter, eliminating the daily error messages and false alarms. |
| 5062092 | Backup/DR | Int-String comparison in table expression used to fail VBR and VBR5 restore. This issue has been fixed. |
| 5079472 | UI - Management Console | Resolved an issue that prevented successful provisioning of Vertica nodes from the Management Console portal in Google Cloud Platform (GCP). Users encountered errors such as 'No inventory was parsed' or 'provided hosts list is empty' during cluster creation, even for single nodes. This fix ensures reliable node provisioning in affected GCP regions. |
| 5079567 | Catalog Engine | Replicated tables used to error out when performing cross namespace ILM operations. This issue has been fixed. |
| 5080026 | Security, Third Party Tools Integration | Addressed multiple critical and high-severity vulnerabilities (CVEs) identified by image security scanners in Vertica server v25.3.0-2 and Vertica Operator v25.3.0-0, enhancing the overall security posture of the system. |
| 5080185 | Execution Engine |
Fixed an issue where a database node could crash unexpectedly when importing a malformed directed query file using the IMPORT_DIRECTED_QUERIES function. Previously, truncated files or those missing critical delimiters (like a semicolon) could lead to a node crash. This fix enhances the robustness of the IMPORT_DIRECTED_QUERIES function, improving system stability when handling improperly formatted input files. |
| 5080219 | Vcluster |
Resolved an issue where the vcluster stop_db command would get stuck in a verification loop, leading to timeouts and an incomplete database shutdown. The command now correctly processes node status during the shutdown sequence. |
| 5080801 | Data Networking | Resolved a potential deadlock scenario where TS callback destructors (dtors) were executing while holding a lock. This fix ensures that callback dtors now run outside the lock, preventing deadlocks that could occur, for example, with async Messenger notifiers |
| 5082078 | Vcluster | The vcluster CLI has been updated to properly handle SIGINT (CTRL-C) signals. Previously, interrupting a vcluster command with CTRL-C would cause the terminal cursor to disappear, requiring a 'reset' or 'clear' command to restore it. This fix ensures that the cursor is reset to normal upon exiting vcluster with CTRL-C, preventing terminal display issues. |
| 5088984 | UI - Management Console | Previously, the 'Upgrade MC' option within the management console did not display versions 25.2 and later as available for upgrade. This issue has been resolved, and users can now access the latest versions for upgrading their management console. |
| 5090189 | UI - Management Console | Addressed a critical defect where users were unable to log in to the Vertica Management Console (MC) after upgrading from version 12.X to 25.4. Previously, users encountered 'invalid username and password' errors post-upgrade. This fix ensures that users can successfully authenticate and log in to the MC following an upgrade to version 25.4, restoring full access and functionality. |