Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.3amended

GitHub personal access token leaking into temporary EasyBuild (debug) logs

CVE-2020-5262GHSA-2wx6-wc87-rmjm

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (easybuild-framework 4.1.2; easybuild 4.1.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
9.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2020-5262: 0.55% estimated exploitation activity in the next 30 days; percentile 45.80 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact 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. Scope: 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-2wx6-wc87-rmjm

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record PYSEC-2020-268

  4. Revision 1 · created ·

    Published from osv record GHSA-2wx6-wc87-rmjm

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-5262

Advisory: GitHub personal access token leaking into temporary EasyBuild (debug) logs
IDs: CVE-2020-5262, GHSA-2wx6-wc87-rmjm
Record: https://patchnext.com/advisories/cve-2020-5262 (revision 4, source checked 26 Oct 2026, 13:17 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: easybuild-framework 4.1.2; easybuild 4.1.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI easybuild-framework: affected < 4.1.2; fixed in 4.1.2
- PyPI easybuild: affected < 4.1.2; fixed in 4.1.2

## Suggested inspection (read-only)
- `python -m pip show easybuild-framework`: prints the installed version. Run with the environment that serves production active.
- `python -m pip show easybuild`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on easybuild-framework, easybuild.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-2wx6-wc87-rmjm (OSV record GHSA-2wx6-wc87-rmjm lists affected ranges: PyPI easybuild-framework >=0 <4.1.2 (fixed))
- Verified: https://osv.dev/vulnerability/PYSEC-2020-268 (OSV record PYSEC-2020-268 lists affected ranges: PyPI easybuild >=0 <4.1.2 (fixed))
- Verified: https://github.com/advisories/GHSA-2wx6-wc87-rmjm (GitHub-reviewed advisory GHSA-2wx6-wc87-rmjm lists affected ranges: PyPI easybuild-framework >=0 <4.1.2)

Commands are suggestions: review each one before running it.

Loading voting…