TechDeveloper toolsMajor

DuckDB 2.0.1 LTS ships security fixes and changes how secret scopes, MERGE and UPDATE ... FROM behave

The first patch release of the 2.0 LTS line patches CVE-2026-97945 in the bundled allocator and lists breaking changes to review before upgrading. DuckDB 1.4 LTS left community support on November 17.

Promptea Editorial2 min read

The DuckDB team released DuckDB 2.0.1 on November 20, 2026. According to the announcement on the DuckDB blog, it is the first patch release in the 2.0 LTS line (codename Cyanoptera), arrives one month after 2.0.0, and "ships bugfixes, performance improvements, and security patches." The v2.0.1 release is also published on the project's GitHub repository, which describes it as "a bug fix release for various issues discovered after we released v2.0.0." Both sources are DuckDB's own.

Security fixes

The blog post lists CVE-2026-97945: some Linux kernels can silently zero memory that was freed lazily with MADV_FREE. DuckDB's bundled jemalloc now sets muzzy_decay_ms to 0. For users who cannot upgrade yet, the post says to set the environment variable DUCKDB_JE_MALLOC_CONF to muzzy_decay_ms:0. The release also includes a fix for a remote path traversal in configurations with enable_external_access=false (#28684) and the Brotli decoder fix for CVE-2026-111497 (#27791).

Breaking changes to review before upgrading

  • SECRET scopes: a host or bucket scope no longer matches a URL that only shares its prefix. The post's example: s3://bucket- no longer matches s3://bucket-1/. Scopes must use the full host or bucket name, including any explicit port.
  • UPDATE ... FROM and MERGE again apply every match, as in 1.x. In 2.0.0, MERGE raised an error on multiple matches and UPDATE ... FROM updated once. The post warns the final value can be non-deterministic.
  • allow_extension_repositories now takes hosts (the new default), allowed, hosts_only or forbidden. The old undecided value is no longer accepted.
  • iceberg_rewrite_data_files now returns Spark's output column names, and the wasm_mvp platform was discontinued.

Data-correctness fixes

Among the bug fixes, the post lists silent NULL-row loss when filtering tables in database files written by DuckDB 1.x (#28355), lost index entries after automatic checkpoints following WAL replay (#26814), lost rows after restarts following a reverted commit (#28190), and wrong results for lateral joins reading from a CTE (#28698). Teams that moved 1.x database files to 2.0.0 are the most exposed to the first one.

The release also adds Parquet page index support for skipping pages (#27326), filter pushdown into views used in subqueries (#27760), which the post says can be "orders of magnitude faster", and registration of extension repositories by host, for example CREATE EXTENSION REPOSITORY duckdb.org;.

Support timeline and what is not said

Community support for DuckDB 1.4 LTS (Andium) ended on November 17, 2026, and the post recommends upgrading to 2.0 LTS, which it says is "supported until at least October 2027." DuckDB 2.1.0 is planned for the first half of 2027. The post does not give a severity score for CVE-2026-97945 or list which Linux kernel versions are affected, and no independent coverage of the release was available when this was written.

Why this matters

  • DuckDB is embedded in many data and AI pipelines, notebooks and agents that query local or S3 data; the SECRET scope change can stop credentials from applying to URLs that matched before.
  • Teams still on 1.4 LTS lost community support three days ago, so this patch is the version DuckDB points them to.
  • Restoring the 1.x semantics of MERGE and UPDATE ... FROM means queries that errored on 2.0.0 now run, possibly with non-deterministic results.

Key takeaways

  • DuckDB 2.0.1 is the first patch release of the 2.0 LTS line, released November 20, 2026.
  • It fixes CVE-2026-97945 by setting jemalloc's muzzy_decay_ms to 0; DUCKDB_JE_MALLOC_CONF is the stopgap.
  • SECRET scopes now require the full host or bucket name; prefix matches no longer work.
  • DuckDB 1.4 LTS community support ended November 17, 2026; 2.0 LTS is supported until at least October 2027.

Sources

  1. DuckDBPrimary
    Announcing DuckDB 2.0.1 LTS
    duckdb.org
  2. DuckDBPrimary
    DuckDB v2.0.1 release on GitHub
    github.com
  3. DuckDBPrimary
    DuckDB release calendar
    duckdb.org

How we choose and verify sources

Tags:
  • duckdb
  • databases
  • security
  • breaking-changes
  • lts
Companies:
  • DuckDB
DuckDB 2.0.1 LTS: security fixes and breaking changes · Promptea