Safeguard
Vulnerability Analysis•

CVE-2020-36771: High Token Exposure in CloudLinux CageFS

CVE-2020-36771 is a high token exposure flaw in CloudLinux CageFS 7.1.1-1 and below, readable in the process list. Upgrade to 7.1.2-2 or later to fix it.

Safeguard Security Team
3 min read

CVE-2020-36771 is a high severity (CVSS 7.8) flaw in CloudLinux CageFS 7.1.1-1 and below. It passes an authentication token as a command line argument, so local users can read it in the process list and gain code execution as another user. The fix is CageFS 7.1.2-2.

What's affected

  • CloudLinux CageFS 7.1.1-1 or below, per the record and the researchers' advisory.
  • Fixed: 7.1.2-2, released to production on 2020-09-28 per the SBA Research timeline.
  • The CVE itself was assigned in January 2024, long after the fix.

The record scores it 7.8 (High) with vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. The record does not flag it as a CISA Known Exploited Vulnerability, and none of the pages I read report exploitation in the wild.

How to check if you're exposed

On RPM based systems, for example run rpm -q cagefs to read the package version, and compare it with 7.1.2-2.

What to do now

  1. Check the CageFS version on each CloudLinux host.
  2. Update to 7.1.2-2 or later through your package manager.
  3. Rotate any tokens that might have been exposed on shared hosts.
  4. Review multi tenant hosts for unexpected processes owned by other users.

After you patch, record the new version for CloudLinux CageFS in your asset inventory, and confirm it with the same check you used above. A fix that was never verified is easy to forget, and an inventory that shows versions is what lets you answer the next advisory in minutes instead of days.

Why it matters

The record maps the flaw to CWE-214, invocation of a process with sensitive information, and CWE-200, exposure of sensitive information. Command line arguments are visible to other local users through the process list, so secrets do not belong there.

Shared hosting is the setting where this matters, since many users share one machine. Because the fix was released in 2020, most current systems should be past it, but old images deserve a look.

To check open source components in your own projects for known CVEs like this one, try the free in-browser dependency scan at gold.safeguard.sh/scan, or look the CVE up in the Gold directory.

Quick check

Why is a 2020 fix tagged in 2024?

The researchers' timeline shows the CVE request was declined once and then assigned by Red Hat in January 2024. The fix itself shipped in September 2020.

How do I find every place CloudLinux CageFS is used?

Start with an inventory of installed software and versions, because you cannot patch what you have not found. Check servers, build hosts, test copies and anything a vendor bundles. For open source libraries, a dependency scan or SBOM gives the same list for your code.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.