CVE-2020-5262: In EasyBuild before version 4.1.2, the GitHub Personal Access Token (PAT) used by EasyBuild for the GitHub int

Q: How do I fix CVE-2020-5262?

easybuild: upgrade to 4.1.2. Exact commands for each OS are on this page.

Q: Is CVE-2020-5262 being exploited?

CVE-2020-5262 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-5262 affect?

CVE-2020-5262 affects easybuild. Severity is high (CVSS 7.7). 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

Q: How urgent is CVE-2020-5262?

Priority 43/100. High severity; Public exploit reference

This month

HIGH 7.7UPGRADE

CVE-2020-5262 is a high-severity flaw (CVSS 7.7) affecting easybuild. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.7 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 54%)
CISA exploited list	No
Weakness	CWE-532, CWE-922
Published	2020-03-19
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: easybuild project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-03-19 17:15 UTCPublished CVE record published
2026-06-17 03:21 UTCUpdated Record last modified

easybuild project easybuild UPGRADE

Affected: < 4.1.2

Fixed in: 4.1.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy easybuild || rpm -q easybuild || easybuild --version

2. UPGRADE to 4.1.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade easybuild

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade easybuild

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-5262?

easybuild: upgrade to 4.1.2. Exact commands for each OS are on this page.

Is CVE-2020-5262 being exploited?

CVE-2020-5262 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-5262 affect?

CVE-2020-5262 affects easybuild. Severity is high (CVSS 7.7). 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

How urgent is CVE-2020-5262?

Priority 43/100. High severity; Public exploit reference

Software pages

GitHub vulnerabilities

References

← Back to latest CVEs