Skip to content
Fencer Vulns
high 8.6

CVE-2016-7051 json

jackson-dataformat-xml vulnerable to server side request forgery (SSRF)

published 2017-04-14 9 y ago modified 2026-06-17 4 mo ago also GHSA-7c2r-3jqf-c9rw , EUVD-2018-0536

cvss
8.6
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.4%
EPSS 2.4% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

XmlMapper in the Jackson XML dataformat component (aka jackson-dataformat-xml) before 2.7.8 and 2.8.x before 2.8.4 allows remote attackers to conduct server-side request forgery (SSRF) attacks via vectors related to a DTD.

Patch / fix

  • maven com.fasterxml.jackson.dataformat:jackson-dataformat-xml 2.7.8, 2.8.4
  • fasterxml jackson-dataformat-xml 2.7.8
  • jackson-dataformat-xml Debian 14, Debian 13, Debian 12 2.8.5-1

debian advisories DEBIAN-CVE-2016-7051

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2016-7051 updated cvss 5.8

jackson-dataformat-xml: XmlMapper is vulnerable to SSRF attack

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.36% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N
GitHub 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
maven com.fasterxml.jackson.dataformat:jackson-dataformat-xml
<2.7.8
>=2.8.0, <2.8.4
2.7.8
2.8.4

Classification

Weakness
  • CWE-611 Improper Restriction of XML External Entity Reference
  • CWE-918 Server-Side Request Forgery

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.