Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2018-8014: The defaults settings for the CORS filter provided in Apache Tomcat 9.0.0.M1 to 9.0.8, 8.5.0 to 8.5.31, 8.0.0.

69
This week
CRITICAL 9.8REMOTEWATCHLISTUPGRADEMITIGATEMITIGATE

CVE-2018-8014 is a critical-severity flaw (CVSS 9.8) affecting tomcat, ubuntu linux, debian linux. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The defaults settings for the CORS filter provided in Apache Tomcat 9.0.0.M1 to 9.0.8, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, 7.0.41 to 7.0.88 are insecure and enable 'supportsCredentials' for all origins. It is expected that users of the CORS filter will have configured it appropriately for their environment rather than using it in the default configuration. Therefore, it is expected that most users will not be impacted by this issue.

Why this priority

  • Critical severity
  • EPSS top 2%: very likely to be exploited
  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance20.9% (top 2%)
CISA exploited listNo
WeaknessCWE-1188
Published2018-05-16
Last modified2026-10-15
Publisher (CNA): Apache Software Foundation · Vendor: apache · canonical · debian · netapp

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

apache tomcat UPGRADE
Affected: >= 7.0.41 and <= 7.0.88 · >= 8.0.0 and <= 8.0.52 · >= 8.5.0 and <= 8.5.31 · >= 9.0.0 and <= 9.0.8 · 8.0.0 rc1 · 9.0.0 milestone1
Fixed in: newer than 9.0.8
Safe to downgrade to: a release before 7.0.41
1. Check installed version
apt-cache policy tomcat || rpm -q tomcat || tomcat --version
2. UPGRADE to newer than 9.0.8 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade tomcat
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade tomcat
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 7.0.41 (Debian / Ubuntu)
apt-cache madison tomcat sudo apt install tomcat=<VERSION_BEFORE_7.0.41> sudo apt-mark hold tomcat
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list tomcat sudo dnf downgrade tomcat-<VERSION_BEFORE_7.0.41> sudo dnf versionlock add tomcat
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.
canonical ubuntu linux MITIGATE
Affected: 14.04 · 16.04 · 17.10 · 18.04
Fixed in: no fixed release known
Safe to downgrade to: a release before 14.04
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
debian debian linux MITIGATE
Affected: 8.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 8.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
netapp oncommand insight MITIGATE
Affected: all versions
Fixed in: no fixed release known
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy oncommand-insight || rpm -q oncommand-insight || oncommand-insight --version
No fixed or unaffected release known
Apply the vendor mitigation from the advisory, disable the affected feature, or restrict network access.
netapp oncommand unified manager DOWNGRADE
Affected: >= 9.4
Fixed in: no fixed release known
Safe to downgrade to: a release before 9.4
1. Check installed version
apt-cache policy oncommand-unified-manager || rpm -q oncommand-unified-manager || oncommand-unified-manager --version
2. No fixed release: DOWNGRADE to a release before 9.4 (Debian / Ubuntu)
apt-cache madison oncommand-unified-manager sudo apt install oncommand-unified-manager=<VERSION_BEFORE_9.4> sudo apt-mark hold oncommand-unified-manager
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list oncommand-unified-manager sudo dnf downgrade oncommand-unified-manager-<VERSION_BEFORE_9.4> sudo dnf versionlock add oncommand-unified-manager
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.
netapp oncommand workflow automation MITIGATE
Affected: all versions
Fixed in: no fixed release known
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy oncommand-workflow-automation || rpm -q oncommand-workflow-automation || oncommand-workflow-automation --version
No fixed or unaffected release known
Apply the vendor mitigation from the advisory, disable the affected feature, or restrict network access.

Exact fixes by distribution

A distro patch exists: prefer upgrading over downgrading.
Maven · org.apache.tomcat.embed:tomcat-embed-core · FIXED · 8.5.32 · vulnerable: >= 8.5.0, < 8.5.32 · source
Set org.apache.tomcat.embed:tomcat-embed-core to 8.5.32 or later in pom.xml or build.gradle, then rebuild and redeploy.
Fedora 46 · librepo · FIXED · 1.21.3-1.fc46 · FEDORA-2026-c502136ca7 · source
sudo dnf upgrade --advisory=FEDORA-2026-c502136ca7
Debian 12 · tomcat9 · NOT AFFECTED
Debian 13 · tomcat9 · NOT AFFECTED
RHEL 7 · tomcat · FIXED · tomcat-7.0.76-9.el7
sudo dnf upgrade --advisory=RHSA-2019:2205 rpm -q tomcat
RHEL 6 · tomcat6 · NOT AFFECTED
Amazon Linux 2 · see advisory · FIXED · ALAS2-2020-1402 · source
sudo yum update --advisory=ALAS2-2020-1402
Amazon Linux 1 · see advisory · FIXED · ALAS-2018-1056 · source
sudo yum update --advisory=ALAS-2018-1056

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

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-2018-8014?

tomcat: upgrade to newer than 9.0.8; ubuntu linux: mitigate or apply the listed mitigation; debian linux: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2018-8014 being exploited?

CVE-2018-8014 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-2018-8014 affect?

CVE-2018-8014 affects tomcat, ubuntu linux, debian linux. Severity is critical (CVSS 9.8). The defaults settings for the CORS filter provided in Apache Tomcat 9.0.0.M1 to 9.0.8, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, 7.0.41 to 7.0.88 are insecure and enable 'supportsCredentials' for all origins. It is expected that users of the CO

How urgent is CVE-2018-8014?

Priority 69/100. Critical severity; EPSS top 2%: very likely to be exploited; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Apache Tomcat vulnerabilities · Ubuntu vulnerabilities · Debian vulnerabilities

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.