CVE-2019-17267: Improper Input Validation in jackson-databind

Summary

15/06/2020
Yes i
Critical
9.8

CVE-2019-17267: Improper Input Validation in jackson-databind. Affects com.fasterxml.jackson.core:jackson-databind across 2 version ranges.

< 2.8.11.5 >= 2.9.0, < 2.9.10

Fixed in 2.8.11.5 or 2.9.10, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2019-17267 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package under scrutiny is jackson-databind, a library for converting Java objects to and from JSON. It is widely used in various applications and frameworks. This vulnerability, identified as CVE-2019-17267, is a Polymorphic Typing issue in FasterXML jackson-databind before version 2.9.10. It is related to net.sf.ehcache.hibernate.EhcacheJtaTransactionManagerLookup.

Vulnerability Detail

The vulnerability arises due to improper input validation in jackson-databind. An attacker can exploit this issue to execute arbitrary code by sending a specially crafted JSON payload. This can lead to various consequences, including remote code execution, data tampering, and unauthorized access to sensitive information. The vulnerability has a CVSS score of 9.8, indicating its critical severity.

How To Fix

Latest published version: 2.22.4 as of 23 Oct 2026

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • < 2.8.11.5 2.8.11.5
  • >= 2.9.0, < 2.9.10 2.9.10

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no known workaround for this vulnerability. It is crucial to apply the recommended fix by upgrading jackson-databind to the patched version.

Conclusion

In conclusion, CVE-2019-17267 is a critical vulnerability in jackson-databind that allows for arbitrary code execution. It is crucial to upgrade to version 2.9.10 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for com.fasterxml.jackson.core:jackson-databind →

Share this vulnerability

FAQ

Jackson-databind is a library for converting Java objects to and from JSON. It is commonly used in applications and frameworks for data serialization and deserialization.

A Polymorphic Typing issue refers to a vulnerability where the type of an object is determined dynamically at runtime, allowing an attacker to manipulate the type and potentially execute arbitrary code.

The vulnerability can lead to remote code execution, data tampering, and unauthorized access to sensitive information. It poses a significant risk to the security and integrity of affected systems.

To fix this vulnerability, you need to upgrade jackson-databind to version 2.9.10 or later. This can be done by updating the library in your application's dependencies and rebuilding the project.

No, there is no known workaround for this vulnerability. It is essential to apply the recommended fix by upgrading jackson-databind.

Related vulnerabilities

Recent vulnerabilities recorded for com.fasterxml.jackson.core:jackson-databind.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

Latest published version: 2.22.4 as of 23 Oct 2026

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • < 2.8.11.5 2.8.11.5
  • >= 2.9.0, < 2.9.10 2.9.10

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback