CVE-2018-14721

FasterXML jackson-databind 2.x before 2.9.7 might allow remote attackers to conduct server-side request forgery (SSRF) attacks by leveraging failure to block the axis2-jaxws class from polymorphic deserialization.

If you're running Jackson-Databind and Axis2 is also on your classpath, you better upgrade this one! If Axis2 is not on your classpath (a relatively rare situation these days - who uses SOAP anymore, anyway!?!), then you are safe, but it's always a good idea to stay on the latest version of jackson-databind if you can.
 

git clone https://github.com/FasterXML/jackson-databind.git
git log -p --first-parent jackson-databind-2.9.6..jackson-databind-2.9.7 -- src/main

+        // [databind#2097]: some 3rd party, one JDK-bundled
+        s.add("org.slf4j.ext.EventData");
+        s.add("flex.messaging.util.concurrent.AsynchBeansWorkManagerExecutor");
+        s.add("com.sun.deploy.security.ruleset.DRSHelper");
+        s.add("org.apache.axis2.jaxws.spi.handler.HandlerResolverImpl");
+

Jackson-databind probably has more CVEs than any other open source Java library on the planet. But that is a bit misleading, because the CVE's tend to be associated with blacklist "gadget" entries added to jackson-databind's list of Java objects it will refuse to deserialize against. A good blog post at cowtowncoder.medium.com explains this in more detail.