What is CVE-2017-15095?

CVE-2017-15095 is a critical-severity insecure deserialization vulnerability in com.fasterxml.jackson.core:jackson-databind (maven), affecting versions >= 2.9.0, < 2.9.4. It is fixed in 2.9.4, 2.8.11, 2.6.7.3, 2.7.9.2. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.

How severe is CVE-2017-15095?

CVE-2017-15095 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of com.fasterxml.jackson.core:jackson-databind are affected by CVE-2017-15095?

com.fasterxml.jackson.core:jackson-databind (maven) versions >= 2.9.0, < 2.9.4 is affected.

Is there a fix for CVE-2017-15095?

Yes. CVE-2017-15095 is fixed in 2.9.4, 2.8.11, 2.6.7.3, 2.7.9.2. Upgrade to this version or later.

Is CVE-2017-15095 exploitable, and should I be worried?

Whether CVE-2017-15095 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2017-15095 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2017-15095

Q: How severe is CVE-2017-15095?

CVE-2017-15095 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of com.fasterxml.jackson.core:jackson-databind are affected by CVE-2017-15095?

com.fasterxml.jackson.core:jackson-databind (maven) versions >= 2.9.0, < 2.9.4 is affected.

Q: Is there a fix for CVE-2017-15095?

Yes. CVE-2017-15095 is fixed in 2.9.4, 2.8.11, 2.6.7.3, 2.7.9.2. Upgrade to this version or later.

Q: Is CVE-2017-15095 exploitable, and should I be worried?

Whether CVE-2017-15095 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2017-15095 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2017-15095?

Upgrade: com.fasterxml.jackson.core:jackson-databind to 2.9.4 or later, com.fasterxml.jackson.core:jackson-databind to 2.8.11 or later, com.fasterxml.jackson.core:jackson-databind to 2.6.7.3 or later, com.fasterxml.jackson.core:jackson-databind to 2.7.9.2 or later.

Summary

jackson-databind vulnerable to deserialization flaw leading to unauthenticated remote code execution

jackson-databind in versions prior to 2.8.11 and 2.9.4 contain a deserialization flaw which allows an unauthenticated user to perform code execution by sending maliciously crafted input to the readValue method of the ObjectMapper. This issue extends the previous flaw CVE-2017-7525, blacklisting additonal vulnerable classes.

Impact

Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.

CVE-2017-15095 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.9.4, 2.8.11, 2.6.7.3, 2.7.9.2); upgrading removes the vulnerable code path.

Affected versions

com.fasterxml.jackson.core:jackson-databind (>= 2.9.0, < 2.9.4) com.fasterxml.jackson.core:jackson-databind (>= 2.8.0, < 2.8.11) com.fasterxml.jackson.core:jackson-databind (>= 2.0.0, < 2.6.7.3) com.fasterxml.jackson.core:jackson-databind (>= 2.7.0, < 2.7.9.2)

Security releases

com.fasterxml.jackson.core:jackson-databind → 2.9.4 (maven) com.fasterxml.jackson.core:jackson-databind → 2.8.11 (maven) com.fasterxml.jackson.core:jackson-databind → 2.6.7.3 (maven) com.fasterxml.jackson.core:jackson-databind → 2.7.9.2 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

com.fasterxml.jackson.core:jackson-databind to 2.9.4 or later; com.fasterxml.jackson.core:jackson-databind to 2.8.11 or later; com.fasterxml.jackson.core:jackson-databind to 2.6.7.3 or later; com.fasterxml.jackson.core:jackson-databind to 2.7.9.2 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2017-15095? CVE-2017-15095 is a critical-severity insecure deserialization vulnerability in com.fasterxml.jackson.core:jackson-databind (maven), affecting versions >= 2.9.0, < 2.9.4. It is fixed in 2.9.4, 2.8.11, 2.6.7.3, 2.7.9.2. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
How severe is CVE-2017-15095? CVE-2017-15095 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of com.fasterxml.jackson.core:jackson-databind are affected by CVE-2017-15095? com.fasterxml.jackson.core:jackson-databind (maven) versions >= 2.9.0, < 2.9.4 is affected.
Is there a fix for CVE-2017-15095? Yes. CVE-2017-15095 is fixed in 2.9.4, 2.8.11, 2.6.7.3, 2.7.9.2. Upgrade to this version or later.
Is CVE-2017-15095 exploitable, and should I be worried? Whether CVE-2017-15095 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2017-15095 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2017-15095?
- Upgrade com.fasterxml.jackson.core:jackson-databind to 2.9.4 or later
- Upgrade com.fasterxml.jackson.core:jackson-databind to 2.8.11 or later
- Upgrade com.fasterxml.jackson.core:jackson-databind to 2.6.7.3 or later
- Upgrade com.fasterxml.jackson.core:jackson-databind to 2.7.9.2 or later

Other vulnerabilities in com.fasterxml.jackson.core:jackson-databind

CVE-IDSeverityPackage summary

CVE-2026-54517Mediumcom.fasterxml.jackson.core:jackson-databind: jackson-databind has @JsonView bypass for setterless creator properties CVE-2026-54516Mediumcom.fasterxml.jackson.core:jackson-databind: jackson-databind's renamed @JsonIgnore'd setters can deserialize via private fields CVE-2026-54515Mediumcom.fasterxml.jackson.core:jackson-databind: jackson-databind has case-insensitive deserialization bypasses per-property @JsonIgnoreProperties CVE-2026-54514Mediumcom.fasterxml.jackson.core:jackson-databind: jackson-databind: InetSocketAddress deserialization triggers eager DNS resolution (SSRF)CVE-2026-54513Highcom.fasterxml.jackson.core:jackson-databind: jackson-databind has an array subtype allowlist bypass in BasicPolymorphicTypeValidator (allowIfSubTypeIsArray)