Skip to content

Drop the zstd 0.13 exceptions: move DataFusion to arrow 60 (zstd 0.14.3) #1366

Open

Description

@seeker89

On 26 October 2026 RustSec published 13 advisories against zstd 0.13.3 and zstd-safe 7.3.0. Three are vulnerabilities and ten are unsoundness warnings:

  • Vulnerabilities:
    • RUSTSEC-2026-0391: data from an abandoned stream leaks into the next stream on a reused context.
    • RUSTSEC-2026-0398: Seekable::decompress sets a Vec's length beyond its capacity.
    • RUSTSEC-2026-0403: uninitialised memory is exposed when streaming decompression of a legacy frame fails.
  • Unsound: RUSTSEC-2026-0395, 0396, 0397, 0399, 0400, 0401, 0402, 0404, 0405 and 0406.

zstd 0.14.3 and zstd-safe 8.2.0 fix all of them. But parquet, arrow-ipc, datafusion and datafusion-datasource 55.2.0 and include-flate-compress still require zstd 0.13. Arrow 60 moves to 0.14, and DataFusion 55.2.0 requires arrow ^59.2.

0.2.3 ships with a time-boxed exception, decided by the maintainer on 26 October 2026 during 0.2.3's gate. The record is docs/qualification/2026-10-26-dependency-exceptions.md.

Task

  • Move to a DataFusion release that uses arrow 60 or later once one exists, so Cargo.lock holds only zstd 0.14.3 or later.
  • Check what include-flate-compress needs as well.
  • Remove the 13 IDs from .cargo/audit.toml.
  • Add a dependency_audit check that fails if zstd < 0.14.3 or zstd-safe < 8.2.0 is locked again.

Done when

  • make audit passes without any of these IDs.
  • The exception record says how they were removed.
  • This is done by the 18 November 2026 review at the latest. If DataFusion still hasn't moved by then, the review decides what happens next.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions