https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 18:23:56 +0000 https://db.gcve.eu/vuln/cve-2026-82331 <p><strong>Affected:</strong> Apache Software Foundation Apache BuildStream</p> <p>Improper link resolution before file access (&#39;link following&#39;) vulnerability in the `tar` source plugin of Apache BuildStream running on Python &lt; 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:</p> <p>* 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 &gt;= 3.12, BuildStream &gt;= 2.3.0 already makes use of the Python `tarfile` filter functionality, which blocks the symlink escape</p> <p>Users are recommended to upgrade to version 2.8.1, which fixes this issue.</p> <p><strong>Affected:</strong> Apache Software Foundation Apache BuildStream</p> <p>Improper link resolution before file access (&#39;link following&#39;) vulnerability in the `tar` source plugin of Apache BuildStream running on Python &lt; 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:</p> <p>* 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 &gt;= 3.12, BuildStream &gt;= 2.3.0 already makes use of the Python `tarfile` filter functionality, which blocks the symlink escape</p> <p>Users are recommended to upgrade to version 2.8.1, which fixes this issue.</p> https://db.gcve.eu/vuln/cve-2026-82331