Apache BuildStream 2.8.1 Blocks Tar Extraction Escape
Tech GuruQuick Answer
The authority published CVE-2026-82331 for Apache BuildStream through 2.8.0 when the tar source plugin runs on Python before 3.12. 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 Affected deployments should be matched to the authority's exact scope and moved to the supported fixed release.
Confirm Scope And Apply The Supported Fix
What to do now: Inventory Apache BuildStream through 2.8.0 when the tar source plugin runs on Python before 3.12, match the exact affected release or feature, apply the authority-supported fixed build or service remediation, validate the dependent workflow, and preserve evidence.
Last verified: 2026-09-23 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Apache BuildStream through 2.8.0 when the tar source plugin runs on Python before 3.12 |
|---|---|
| Advisory | CVE-2026-82331 |
| CVE | CVE-2026-82331 |
| Authoritative release date | 2026-09-23 06:58:21.546 UTC |
| Authority revision date | 2026-09-23 16:08:58.171 UTC |
| Affected versions | Apache BuildStream through 2.8.0 when the tar source plugin runs on Python before 3.12 |
| Fixed version | Apache BuildStream 2.8.1 |
| CVSS base score | Not provided by the authority |
| CVSS severity | Moderate |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
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
What To Validate Now
- Inventory. Locate Apache BuildStream through 2.8.0 when the tar source plugin runs on Python before 3.12 deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Compare each deployment with the authority's affected-version statement: Apache BuildStream through 2.8.0 when the tar source plugin runs on Python before 3.12 Do not infer applicability from product family or severity alone.
- Remediate. Apply Apache BuildStream 2.8.1 through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. Confirm the resulting version or managed-service state, exercise representative functionality and recovery paths, monitor for regressions, and document exceptions.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
