CVE-2016-5018

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 10.3%, top 5% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 10%CVSS: 9.1Exploit: NoneExposed: 0

A fix is available — apply it.

In Apache Tomcat 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36, 7.0.0 to 7.0.70 and 6.0.0 to 6.0.45 a malicious web application was able to bypass a configured SecurityManager via a Tomcat utility method that was accessible to web applications.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
61(Track*)
EG Risk 61/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
95.2%
KEV
Not listed

Published

August 10, 2017

Last Modified

May 13, 2026

Advisory Details (9)

Auto-updated May 19, 2026
Patch available. Sources: redhat.
redhat Patch Available

Affected: Red Hat Enterprise Linux 7.

https://access.redhat.com/errata/RHSA-2017:1548
redhat Patch Available

Affected: Red Hat Enterprise Linux 7. These packages provide a number of enhancements over the previous version of Red Hat JBoss Web Ser

https://access.redhat.com/errata/RHSA-2017:0456
redhat Patch Available

Affected: Red Hat Enterprise Linux 6. These packages provide a number of enhancements over the previous version of Red Hat JBoss Web Ser

https://access.redhat.com/errata/RHSA-2017:0455
generic
http://www.securitytracker.com/id/1038757
generic
http://www.securitytracker.com/id/1037142
generic
http://www.securityfocus.com/bid/93942
generic

[SECURITY] [DSA 3720-1] tomcat8 security update

http://www.debian.org/security/2016/dsa-3720
generic
http://rhn.redhat.com/errata/RHSA-2017-1551.html
generic
http://rhn.redhat.com/errata/RHSA-2017-0457.html

Vendor Advisories for CVE-2016-5018(5)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(11)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntutomcat6 (6.0.35-1ubuntu3.9) @ precise2026-05-22ubuntu
ubuntulibservlet2.5-java-doc (6.0.45+dfsg-1ubuntu0.1) @ xenial2026-05-22ubuntu
redhattomcat-0:7.0.76-2.el72017-08-01redhat
redhatresteasy-0:2.3.20-1.Final_redhat_1.1.ep6.el72017-06-20redhat
redhatpatch2017-06-20redhat
redhatresteasy-0:2.3.20-1.Final_redhat_1.1.ep6.el52017-06-20redhat
redhatresteasy-0:2.3.20-1.Final_redhat_1.1.ep6.el62017-06-20redhat
redhatjboss-ec2-eap-0:7.5.16-1.Final_redhat_1.ep6.el62017-06-20redhat
redhattomcat-vault-0:1.0.8-9.Final_redhat_2.1.ep7.el62017-03-07redhat
redhatpatch2017-03-07redhat
redhattomcat-vault-0:1.0.8-9.Final_redhat_2.1.ep7.el72017-03-07redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 1 ecosystem)
Maven(3)
PackageVulnerable rangeFixed inDependents
org.apache.tomcat.embed:tomcat-embed-jasper—6.0.47—
org.apache.tomcat:jasper6.0.13 ... 6.0.45 (20 versions)6.0.47—
org.apache.tomcat:tomcat-jasper7.0.0 ... 7.0.8 (48 versions)7.0.72—

Additional Vendor Advisories

(6)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 13× in last 7d / 42× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 01:23 UTCEG score recompute
  2. 2026-07-22 22:02 UTCEG score recompute
  3. 2026-07-22 14:04 UTCEPSS rescore
  4. 2026-07-21 15:21 UTCEPSS rescore
  5. 2026-07-21 15:21 UTCEPSS rescore
  6. 2026-07-20 17:03 UTCEPSS rescore
  7. 2026-07-19 14:27 UTCEPSS rescore
  8. 2026-07-19 02:26 UTCEPSS rescore
  9. 2026-07-19 02:26 UTCEPSS rescore
  10. 2026-07-18 10:00 UTCEPSS rescore
  11. 2026-07-18 10:00 UTCEPSS rescore
  12. 2026-07-16 16:59 UTCEPSS rescore
  13. 2026-07-16 16:59 UTCEPSS rescore
  14. 2026-07-15 16:54 UTCEPSS rescore
  15. 2026-07-15 16:54 UTCEPSS rescore
  16. 2026-07-15 01:56 UTCEPSS rescore
  17. 2026-07-15 01:56 UTCEPSS rescore
  18. 2026-07-13 22:26 UTCEPSS rescore
  19. 2026-07-13 06:09 UTCEPSS rescore
  20. 2026-07-12 05:43 UTCEPSS rescore
  21. 2026-07-12 05:43 UTCEPSS rescore
  22. 2026-07-11 19:22 UTCOSV refresh
  23. 2026-07-11 08:23 UTCEPSS rescore
  24. 2026-07-09 19:05 UTCEPSS rescore
  25. 2026-07-08 15:10 UTCEPSS rescore
Show 71 more
  1. 2026-07-07 13:42 UTCEPSS rescore
  2. 2026-07-06 16:24 UTCEPSS rescore
  3. 2026-07-06 16:24 UTCEPSS rescore
  4. 2026-07-05 02:27 UTCEPSS rescore
  5. 2026-07-04 06:28 UTCEPSS rescore
  6. 2026-07-01 15:02 UTCEPSS rescore
  7. 2026-06-30 23:19 UTCEPSS rescore
  8. 2026-06-29 14:03 UTCEPSS rescore
  9. 2026-06-28 14:04 UTCEPSS rescore
  10. 2026-06-28 04:53 UTCEPSS rescore
  11. 2026-06-27 03:05 UTCEPSS rescore
  12. 2026-06-27 03:05 UTCEPSS rescore
  13. 2026-06-25 13:47 UTCEPSS rescore
  14. 2026-06-25 13:47 UTCEPSS rescore
  15. 2026-06-24 14:02 UTCEPSS rescore
  16. 2026-06-24 14:02 UTCEPSS rescore
  17. 2026-06-23 21:30 UTCEPSS rescore
  18. 2026-06-23 02:00 UTCOSV refresh
  19. 2026-06-22 14:23 UTCEPSS rescore
  20. 2026-06-21 14:54 UTCEPSS rescore
  21. 2026-06-21 14:54 UTCEPSS rescore
  22. 2026-06-21 01:57 UTCEPSS rescore
  23. 2026-06-21 01:57 UTCEPSS rescore
  24. 2026-06-18 17:50 UTCEPSS rescore
  25. 2026-06-17 17:50 UTCEPSS rescore
  26. 2026-06-17 17:50 UTCEPSS rescore
  27. 2026-06-16 17:50 UTCEPSS rescore
  28. 2026-06-16 17:50 UTCEPSS rescore
  29. 2026-06-15 17:45 UTCEPSS rescore
  30. 2026-06-14 23:14 UTCEPSS rescore
  31. 2026-06-13 22:57 UTCEPSS rescore
  32. 2026-06-13 22:57 UTCEPSS rescore
  33. 2026-06-12 23:09 UTCEPSS rescore
  34. 2026-06-12 23:09 UTCEPSS rescore
  35. 2026-06-11 13:57 UTCEPSS rescore
  36. 2026-06-10 22:15 UTCEPSS rescore
  37. 2026-06-10 13:18 UTCEPSS rescore
  38. 2026-06-08 14:14 UTCEPSS rescore
  39. 2026-06-07 15:22 UTCEPSS rescore
  40. 2026-06-07 15:22 UTCEPSS rescore
  41. 2026-06-06 13:45 UTCEPSS rescore
  42. 2026-06-05 22:44 UTCEPSS rescore
  43. 2026-06-05 21:27 UTCOSV refresh
  44. 2026-06-05 06:08 UTCEPSS rescore
  45. 2026-06-05 06:08 UTCEPSS rescore
  46. 2026-06-04 13:10 UTCEPSS rescore
  47. 2026-06-04 13:10 UTCEPSS rescore
  48. 2026-06-02 20:10 UTCEPSS rescore
  49. 2026-06-01 13:49 UTCEPSS rescore
  50. 2026-06-01 13:49 UTCEPSS rescore
  51. 2026-05-31 22:28 UTCEPSS rescore
  52. 2026-05-31 22:28 UTCEPSS rescore
  53. 2026-05-31 00:14 UTCEPSS rescore
  54. 2026-05-29 13:41 UTCEPSS rescore
  55. 2026-05-28 13:42 UTCEPSS rescore
  56. 2026-05-28 13:42 UTCEPSS rescore
  57. 2026-05-27 13:38 UTCEPSS rescore
  58. 2026-05-27 13:38 UTCEPSS rescore
  59. 2026-05-26 13:42 UTCEPSS rescore
  60. 2026-05-26 07:16 UTCEPSS rescore
  61. 2026-05-24 16:43 UTCEPSS rescore
  62. 2026-05-22 21:15 UTCEPSS rescore
  63. 2026-05-22 21:15 UTCEPSS rescore
  64. 2026-05-22 10:45 UTCEG score recompute
  65. 2026-05-22 10:45 UTCVendor advisory
  66. 2026-05-21 22:40 UTCEPSS rescore
  67. 2026-05-20 11:21 UTCEPSS rescore
  68. 2026-05-20 11:21 UTCEPSS rescore
  69. 2026-05-20 11:21 UTCEPSS rescore
  70. 2026-05-18 21:30 UTCEPSS rescore
  71. 2026-05-18 21:30 UTCEPSS rescore

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2016-5018?
CVE-2016-5018 is a critical vulnerability published on August 10, 2017. In Apache Tomcat 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36, 7.0.0 to 7.0.70 and 6.0.0 to 6.0.45 a malicious web application was able to bypass a configured SecurityManager via a Tomcat utility method that was accessible to web applications.
When was CVE-2016-5018 disclosed?
CVE-2016-5018 was first published in the National Vulnerability Database on August 10, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-5018 actively exploited?
CVE-2016-5018 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 95.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-5018?
CVE-2016-5018 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2016-5018?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-5018, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2016-5018

Explore →

Is Your Infrastructure Affected by CVE-2016-5018?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs