Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2019-15631: Remote Code Execution vulnerability in MuleSoft Mule CE/EE 3.x and API Gateway 2.x released before October 31,

60
This week
CRITICAL 9.8REMOTEUPGRADEUPGRADEUPGRADE

CVE-2019-15631 is a critical-severity flaw (CVSS 9.8) affecting api gateway, mule runtime, mule runtime. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Remote Code Execution vulnerability in MuleSoft Mule CE/EE 3.x and API Gateway 2.x released before October 31, 2019 allows remote attackers to execute arbitrary code.

Why this priority

  • Critical severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance2.3% (top 16%)
CISA exploited listNo
Published2019-12-02
Last modified2026-06-17
Publisher (CNA): Salesforce, Inc. · Vendor: mulesoft

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

mulesoft api gateway UPGRADE
Affected: >= 2.0.0 and <= 2.2.12
Fixed in: newer than 2.2.12
Safe to downgrade to: a release before 2.0.0
1. Check installed version
apt-cache policy api-gateway || rpm -q api-gateway || api-gateway --version
2. UPGRADE to newer than 2.2.12 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade api-gateway
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade api-gateway
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 2.0.0 (Debian / Ubuntu)
apt-cache madison api-gateway sudo apt install api-gateway=<VERSION_BEFORE_2.0.0> sudo apt-mark hold api-gateway
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list api-gateway sudo dnf downgrade api-gateway-<VERSION_BEFORE_2.0.0> sudo dnf versionlock add api-gateway
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
mulesoft mule runtime UPGRADE
Affected: >= 3.0.0 and <= 3.9.3
Fixed in: newer than 3.9.3
Safe to downgrade to: a release before 3.0.0
1. Check installed version
apt-cache policy mule-runtime || rpm -q mule-runtime || mule-runtime --version
2. UPGRADE to newer than 3.9.3 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade mule-runtime
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade mule-runtime
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 3.0.0 (Debian / Ubuntu)
apt-cache madison mule-runtime sudo apt install mule-runtime=<VERSION_BEFORE_3.0.0> sudo apt-mark hold mule-runtime
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list mule-runtime sudo dnf downgrade mule-runtime-<VERSION_BEFORE_3.0.0> sudo dnf versionlock add mule-runtime
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
mulesoft mule runtime UPGRADE
Affected: >= 3.0.0 and <= 3.9.3
Fixed in: newer than 3.9.3
Safe to downgrade to: a release before 3.0.0
1. Check installed version
apt-cache policy mule-runtime || rpm -q mule-runtime || mule-runtime --version
2. UPGRADE to newer than 3.9.3 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade mule-runtime
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade mule-runtime
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 3.0.0 (Debian / Ubuntu)
apt-cache madison mule-runtime sudo apt install mule-runtime=<VERSION_BEFORE_3.0.0> sudo apt-mark hold mule-runtime
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list mule-runtime sudo dnf downgrade mule-runtime-<VERSION_BEFORE_3.0.0> sudo dnf versionlock add mule-runtime
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
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-2019-15631?

api gateway: upgrade to newer than 2.2.12; mule runtime: upgrade to newer than 3.9.3; mule runtime: upgrade to newer than 3.9.3. Exact commands for each OS are on this page.

Is CVE-2019-15631 being exploited?

CVE-2019-15631 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-2019-15631 affect?

CVE-2019-15631 affects api gateway, mule runtime, mule runtime. Severity is critical (CVSS 9.8). Remote Code Execution vulnerability in MuleSoft Mule CE/EE 3.x and API Gateway 2.x released before October 31, 2019 allows remote attackers to execute arbitrary code.

How urgent is CVE-2019-15631?

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

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.