Yes. org.apache.tomcat:jasper (Maven): upgrade to 6.0.47 or later; org.apache.tomcat:tomcat-jasper (Maven): upgrade to 9.0.0.M10 or later; org.apache.tomcat.embed:tomcat-embed-jasper (Maven): upgrade to 9.0.0.M10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2016-5018?
Check whether you run org.apache.tomcat:jasper (Maven), org.apache.tomcat:tomcat-jasper (Maven) or org.apache.tomcat.embed:tomcat-embed-jasper (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
org.apache.tomcat:jasper (Maven): upgrade to 6.0.47 or later
# set org.apache.tomcat:jasper to 6.0.47 in your pom.xml or build.gradle
org.apache.tomcat:tomcat-jasper (Maven): upgrade to 9.0.0.M10 or later
# set org.apache.tomcat:tomcat-jasper to 9.0.0.M10 in your pom.xml or build.gradle
org.apache.tomcat.embed:tomcat-embed-jasper (Maven): upgrade to 9.0.0.M10 or later
# set org.apache.tomcat.embed:tomcat-embed-jasper to 9.0.0.M10 in your pom.xml or build.gradle