USN-9110-1: libjackson-json-java vulnerabilities

Published Nov 17, 2026
·
Updated

Liao Xinxi discovered that Jackson incorrectly handled the deserialization of certain classes. An attacker could possibly use this issue to execute arbitrary code. (CVE-2017-7525)

It was discovered that the fix for CVE-2017-7525 was incomplete, as Jackson still allowed the deserialization of certain dangerous classes. An attacker could possibly use this issue to execute arbitrary code. (CVE-2017-15095)

It was discovered that Jackson incorrectly handled XML external entities. An attacker could possibly use this issue to obtain sensitive information or cause a denial of service. (CVE-2019-10172)

Affected Software

6 affected componentsFixes available
ubuntu/libjackson-json-java<1.9.13-1~18.04.1~esm1
1.9.13-1~18.04.1~esm1
ubuntu/libjackson-json-java<1.9.13-1ubuntu0.1~esm1
1.9.13-1ubuntu0.1~esm1
All of the following
ubuntu/libjackson-json-java<Ubuntu Pro
Ubuntu Pro
Ubuntu Ubuntu=20.04
All of the following
ubuntu/libjackson-json-java<Ubuntu Pro
Ubuntu Pro
Ubuntu Ubuntu=18.04

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade ubuntu/libjackson-json-java to a version that resolves this vulnerability.

    Fixed in 1.9.13-1~18.04.1~esm1
  2. Upgrade

    Upgrade ubuntu/libjackson-json-java to a version that resolves this vulnerability.

    Fixed in 1.9.13-1ubuntu0.1~esm1
  3. Upgrade

    Upgrade ubuntu/libjackson-json-java to a version that resolves this vulnerability.

    Fixed in Ubuntu Pro

Event History

Nov 17, 2026
Advisory Published
via Ubuntu·12:00 AM
Data Sourced
via Ubuntu·12:00 AM
DescriptionAffected Software
Advisory Published
via OSV·12:02 AM
Data Sourced
via OSV·12:02 AM
DescriptionAffected Software

Frequently Asked Questions

1

What attack paths are described by these issues?

The deserialization flaws could allow arbitrary code execution when certain classes are deserialized. The XML external-entity flaw could allow sensitive-information disclosure or denial of service.

2

Is the original deserialization fix sufficient on its own?

No. The data states that the fix for CVE-2017-7525 was incomplete because dangerous classes could still be deserialized, which is tracked as CVE-2017-15095.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203