CVE-2020-5262

CVE-2020-5262 is a high-severity vulnerability in Easybuild Project Easybuild with a CVSS 3.x base score of 7.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-922.

Key facts

Description

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.

Frequently asked questions

What is CVE-2020-5262?
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.
How severe is CVE-2020-5262?
CVE-2020-5262 has a CVSS 3.x base score of 7.7, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2020-5262 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (41st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-5262?
CVE-2020-5262 affects Easybuild Project Easybuild. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-5262?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2020-5262 published?
CVE-2020-5262 was published on 2020-03-19 and last updated on 2026-06-17.

References

Affected products (1)

Other CWE-922 vulnerabilities

Browse all CWE-922 vulnerabilities →