• Concept
  • Release notes

6.0.1 Secure release notes

What's new

Compromised eMudhra certificates removed

No more Java heap space errors on large schemas

Security vulnerability report

CVE summary

Full list of changes

  • Security(SECURE-1170, NTT-2077) Removed the compromised eMudhra root certificates from the Java runtime bundled with the Docker image and the Windows installer, and from the Liquibase Secure Server migrate container. This resolves CVE-2026-91403 and CVE-2026-114820.
  • Security(SECURE-1172) Updated snowflake-jdbc from 4.3.3 to 4.3.4, resolving CVE-2026-86597. With Snowflake driver debug logging on, the earlier driver logged the query result key in clear text.
  • Security(SECURE-1242) Updated mariadb-java-client from 3.5.10 to 3.5.11, resolving CVE-2026-119210, CVE-2026-119276, CVE-2026-119280, and CVE-2026-119281. On Liquibase Secure 6.0.0 and earlier, a malicious MariaDB server or a network attacker could read files from the machine running Liquibase. If you can't upgrade yet, add allowLocalInfile=false to your MariaDB JDBC URL and connect over TLS with server certificate verification.
  • Security(SECURE-1171) Updated Liquibase Package Manager (LPM) in the Docker image to 0.3.8, resolving CVE-2026-78663.
  • Performance(SECURE-1075) Commands that check Liquibase's tracking tables, such as update, status, update-sql, validate and list-locks, no longer run out of Java heap space on large Oracle, SQL Server, DB2, MySQL and MariaDB schemas. This issue was present in Liquibase Secure 6.0.0.