Android SVG vulnerable to XML External Entity (XXE)

published 2018-01-03 8y ago modified 2026-06-17 4mo ago also GHSA-g556-x5vx-qh59 , EUVD-2018-0597

cvss: 7.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.6%; EPSS 1.6% chance of exploitation in 30 days, percentile 75%
public exploits: 0; none known

AndroidSVG version 1.2.2 is vulnerable to XXE attacks in the SVG parsing component resulting in denial of service and possibly remote code execution

Patch / fix

fixed in 1

maven com.caverock:androidsvg 1.3

Is CVE-2017-1000498 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.57% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	7.8	CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD	2.0	6.8	AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub	3.1	7.8	CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
maven	com.caverock:androidsvg	<1.3	1.3

Classification

Weakness

CWE-611 Improper Restriction of XML External Entity Reference

References

github.com /BigBadaboom/androidsvg/issues/122
web, issue-tracking, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2017-1000498
advisory
github.com /BigBadaboom/androidsvg
package
github.com /advisories/GHSA-g556-x5vx-qh59
advisory

Sources

Fencer Intel 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.