Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
9.8

CVE-2026-82331: Apache BuildStream tar plugin can write files via malicious archive

CVE-2026-82331 · published 2 months ago
Summary

BuildStream versions before 2.8.1 that run on Python earlier than 3.12 may follow symlinks inside a source tarball and create or overwrite files on the machine where the build runs. An attacker who supplies a crafted archive could place unwanted files with the same rights as the user running BuildStream. Upgrade BuildStream to version 2.8.1 (or later) and use Python 3.12 or newer, and always fetch source tarballs from trusted locations with their hashes verified.

What to do
  • Update debian buildstream to version 2.8.1-1.
  • Update debian buildstream to version 1.6.9-2+deb13u1.
Affected software
Ecosystem VendorProductAffected versions
– apache software foundation apache buildstream <= 2.8.0
Debian:12 debian buildstream All versions
Ubuntu:20.04:LTS canonical buildstream All versions
Debian:14 debian buildstream < 2.8.1-1
Fix: upgrade to 2.8.1-1
Debian:13 debian buildstream < 1.6.9-2+deb13u1
Fix: upgrade to 1.6.9-2+deb13u1
Original advisory text
DEBIAN-CVE-2026-82331
Improper link resolution before file access ('link following') vulnerability in the `tar` source plugin of Apache BuildStream running on Python < 3.12 allows malicious source tarballs to write files on the host, with the privileges of the user running BuildStream, via symlinks as part of source fetching. The impact of this issue is mitigated by: * BuildStream projects should only use trusted sources in their elements as otherwise the build output can also not be trusted * Tracking a source tarball pins its SHA256 hash, which prevents MITM attacks of users that are fetching an already tracked project * When running on Python >= 3.12, BuildStream >= 2.3.0 already makes use of the Python `tarfile` filter functionality, which blocks the symlink escape Users are recommended to upgrade to version 2.8.1, which fixes this issue.
Fix within
Internet-facing 3 days
Internal 60 days
  • Not known to be exploited
  • Can be exploited automatically
  • Gives an attacker full control
Severity
9.8 Critical
Exploitation
<1% chance of attack within 30 days
Type
CWE-59Link Following
Timeline
Published23 Sep 2026
Updated22 Nov 2026
First seen23 Sep 2026
Track software like this
Free during beta