The xsltAddTextString function in transform.c in libxslt 1.1.29, as used in Blink in Google Chrome prior to 57.0.2987.98 for Mac, Windows, and Linux and 57.0.2987.108 for Android, lacked a check for integer overflow during a size calculation, which allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page.
CVE-2017-5029
HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence
This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 2.1%, top 20% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 2%CVSS: 8.8Exploit: NoneExposed: 0
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 8.8(medium)
- EPSS
- 80.0%
- KEV
- Not listed
Published
April 24, 2017
Last Modified
May 13, 2026
References (14)
- chrome-cve-admin@googlehttp://rhn.redhat.com/errata/RHSA-2017-0499.html
- chrome-cve-admin@googlehttp://www.debian.org/security/2017/dsa-3810
- chrome-cve-admin@googlehttp://www.securityfocus.com/bid/96767
- chrome-cve-admin@googlehttp://www.securitytracker.com/id/1038157
- chrome-cve-admin@googlehttps://chromereleases.googleblog.com/2017/03/stable-channel-update-for-desktop.html
- chrome-cve-admin@googlehttps://crbug.com/676623
- chrome-cve-admin@googlehttps://git.gnome.org/browse/libxslt/commit/?id=08ab2774b870de1c7b5a48693df75e8154addae5
- af854a3a-2127-422b-91ae-364da2661108http://rhn.redhat.com/errata/RHSA-2017-0499.html
- af854a3a-2127-422b-91ae-364da2661108http://www.debian.org/security/2017/dsa-3810
- af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/96767
- af854a3a-2127-422b-91ae-364da2661108http://www.securitytracker.com/id/1038157
- af854a3a-2127-422b-91ae-364da2661108https://chromereleases.googleblog.com/2017/03/stable-channel-update-for-desktop.html
- af854a3a-2127-422b-91ae-364da2661108https://crbug.com/676623
- af854a3a-2127-422b-91ae-364da2661108https://git.gnome.org/browse/libxslt/commit/?id=08ab2774b870de1c7b5a48693df75e8154addae5
Patch Availability(3)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | liboxideqtcore0 (1.21.5-0ubuntu0.16.10.1) @ yakkety | 2026-05-22 | ubuntu |
| ubuntu | xsltproc (1.1.28-2.1ubuntu0.1) @ xenial | 2026-05-22 | ubuntu |
| redhat | chromium-browser-0:57.0.2987.98-1.el6 | 2017-03-14 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
RubyGems(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nokogiri | 1.0.0 ... 1.7.1 (98 versions) | 1.7.2 | — |
Frequently asked(5)
What is CVE-2017-5029?
CVE-2017-5029 is a high vulnerability published on April 24, 2017. The xsltAddTextString function in transform.c in libxslt 1.1.29, as used in Blink in Google Chrome prior to 57.0.2987.98 for Mac, Windows, and Linux and 57.0.2987.108 for Android, lacked a check for integer overflow during a size calculation, which allowed a remote attacker to perform an out of…
When was CVE-2017-5029 disclosed?
CVE-2017-5029 was first published in the National Vulnerability Database on April 24, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-5029 actively exploited?
CVE-2017-5029 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 80.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-5029?
CVE-2017-5029 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2017-5029?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-5029, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-5029
Is Your Infrastructure Affected by CVE-2017-5029?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.