https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 15 Oct 2026 20:22:18 +0000 https://cve.radiocsirt.org/vuln/cnvd-2020-19503 cnvd-2020-19503 https://cve.radiocsirt.org/vuln/cnvd-2020-19503 https://cve.radiocsirt.org/vuln/euvd-2026-36523 EUVD-2026-36523 https://cve.radiocsirt.org/vuln/euvd-2026-36523 https://cve.radiocsirt.org/vuln/fkie_cve-2020-5262 <p>In EasyBuild before version 4.1.2, the GitHub Personal Access Token (PAT) used by EasyBuild for the GitHub integration features (like `--new-pr`, `--fro,-pr`, etc.) is shown in plain text in EasyBuild debug log files. This issue is fixed in EasyBuild v4.1.2, and in the `master`+ `develop` branches of the `easybuild-framework` repository.</p> <p>In EasyBuild before version 4.1.2, the GitHub Personal Access Token (PAT) used by EasyBuild for the GitHub integration features (like `--new-pr`, `--fro,-pr`, etc.) is shown in plain text in EasyBuild debug log files. This issue is fixed in EasyBuild v4.1.2, and in the `master`+ `develop` branches of the `easybuild-framework` repository.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2020-5262 https://cve.radiocsirt.org/vuln/ghsa-2wx6-wc87-rmjm <p><strong>Affected:</strong> PyPI: easybuild-framework</p> <p>### Impact</p> <p>The GitHub Personal Access Token (PAT) used by EasyBuild for the GitHub integration features (like `--new-pr`, `--from-pr`, etc.) is shown in plain text in EasyBuild debug log files.</p> <p>Scope:</p> <p>* the log message only appears in the top-level log file, *not* in the individual software installation logs (see https://easybuild.readthedocs.io/en/latest/Logfiles.html); - as a consequence, tokens are *not* included in the partial log files that are uploaded into a gist when using `--upload-test-report` in combination with `--from-pr`, nor in the installation logs that are copied to the software installation directories; * the message is only logged when using `--debug`, so it will not appear when using the default EasyBuild configuration (only info messages are logged by default); * the log message is triggered via `--from-pr`, but also via various other GitHub integration options like `--new-pr`, `--merge-pr`, `--close-pr`, etc., but usually only appears in the temporary log file that is cleaned up automatically as soon as eb completes successfully; * you may have several debug log files that include your GitHub token in `/tmp` (or a different location if you&#39;ve set the `--tmpdir` EasyBuild configuration option) on the systems where you use EasyBuild, but they are located in a subdirectory that is only accessible to your account (permissions set to 700); * the only way that a log file that may include your token could have been made public is *if you shared it yours…</p> <p><strong>Affected:</strong> PyPI: easybuild-framework</p> <p>### Impact</p> <p>The GitHub Personal Access Token (PAT) used by EasyBuild for the GitHub integration features (like `--new-pr`, `--from-pr`, etc.) is shown in plain text in EasyBuild debug log files.</p> <p>Scope:</p> <p>* the log message only appears in the top-level log file, *not* in the individual software installation logs (see https://easybuild.readthedocs.io/en/latest/Logfiles.html); - as a consequence, tokens are *not* included in the partial log files that are uploaded into a gist when using `--upload-test-report` in combination with `--from-pr`, nor in the installation logs that are copied to the software installation directories; * the message is only logged when using `--debug`, so it will not appear when using the default EasyBuild configuration (only info messages are logged by default); * the log message is triggered via `--from-pr`, but also via various other GitHub integration options like `--new-pr`, `--merge-pr`, `--close-pr`, etc., but usually only appears in the temporary log file that is cleaned up automatically as soon as eb completes successfully; * you may have several debug log files that include your GitHub token in `/tmp` (or a different location if you&#39;ve set the `--tmpdir` EasyBuild configuration option) on the systems where you use EasyBuild, but they are located in a subdirectory that is only accessible to your account (permissions set to 700); * the only way that a log file that may include your token could have been made public is *if you shared it yours…</p> https://cve.radiocsirt.org/vuln/ghsa-2wx6-wc87-rmjm https://cve.radiocsirt.org/vuln/gsd-2020-5262 gsd-2020-5262 https://cve.radiocsirt.org/vuln/gsd-2020-5262 https://cve.radiocsirt.org/vuln/pysec-2020-268 <p><strong>Affected:</strong> PyPI: easybuild</p> <p>In EasyBuild before version 4.1.2, the GitHub Personal Access Token (PAT) used by EasyBuild for the GitHub integration features (like `--new-pr`, `--fro,-pr`, etc.) is shown in plain text in EasyBuild debug log files. This issue is fixed in EasyBuild v4.1.2, and in the `master`+ `develop` branches of the `easybuild-framework` repository.</p> <p><strong>Affected:</strong> PyPI: easybuild</p> <p>In EasyBuild before version 4.1.2, the GitHub Personal Access Token (PAT) used by EasyBuild for the GitHub integration features (like `--new-pr`, `--fro,-pr`, etc.) is shown in plain text in EasyBuild debug log files. This issue is fixed in EasyBuild v4.1.2, and in the `master`+ `develop` branches of the `easybuild-framework` repository.</p> https://cve.radiocsirt.org/vuln/pysec-2020-268