CVE-2020-5426: Scheduler for TAS prior to version 1.4.0 was permitting plaintext transmission of UAA client token by sending

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

pivotal scheduler: upgrade to 1.4.0. Exact commands for each OS are on this page.

Q: Is CVE-2020-5426 being exploited?

CVE-2020-5426 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-5426 affect?

CVE-2020-5426 affects pivotal scheduler. Severity is critical (CVSS 9.8). Scheduler for TAS prior to version 1.4.0 was permitting plaintext transmission of UAA client token by sending it over a non-TLS connection. This also depended on the configuration of the MySQL server which is used to cache a UAA client toke

Q: How urgent is CVE-2020-5426?

Priority 53/100. Critical severity; Remotely exploitable, no login, no user action

This month

CRITICAL 9.8REMOTEUPGRADE

CVE-2020-5426 is a critical-severity flaw (CVSS 9.8) affecting pivotal scheduler. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Scheduler for TAS prior to version 1.4.0 was permitting plaintext transmission of UAA client token by sending it over a non-TLS connection. This also depended on the configuration of the MySQL server which is used to cache a UAA client token used by the service. If intercepted the token can give an attacker admin level access in the cloud controller.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.7% (top 47%)
CISA exploited list	No
Weakness	CWE-319
Published	2020-11-11
Last modified	2026-06-17

Publisher (CNA): Pivotal Software, Inc. · Vendor: vmware

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

Am I affected?

Timeline

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

vmware pivotal scheduler UPGRADE

Affected: < 1.4.0

Fixed in: 1.4.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy pivotal-scheduler || rpm -q pivotal-scheduler || pivotal-scheduler --version

2. UPGRADE to 1.4.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade pivotal-scheduler

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade pivotal-scheduler

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-5426?

pivotal scheduler: upgrade to 1.4.0. Exact commands for each OS are on this page.

Is CVE-2020-5426 being exploited?

CVE-2020-5426 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-5426 affect?

CVE-2020-5426 affects pivotal scheduler. Severity is critical (CVSS 9.8). Scheduler for TAS prior to version 1.4.0 was permitting plaintext transmission of UAA client token by sending it over a non-TLS connection. This also depended on the configuration of the MySQL server which is used to cache a UAA client toke

How urgent is CVE-2020-5426?

Priority 53/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

MySQL vulnerabilities · VMware vulnerabilities

References

← Back to latest CVEs