CVE-2017-12629

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 92% (99th percentile of EPSS-scored CVEs). 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
Weaponized
9.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 92%
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 92%CVSS: 9.8Exploit: Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed services: Not assessed

A fix is available — apply it.

Remote code execution occurs in Apache Solr before 7.1 with Apache Lucene before 7.1 by exploiting XXE in conjunction with use of a Config API add-listener command to reach the RunExecutableListener class. Elasticsearch, although it uses Lucene, is NOT vulnerable to this. Note that the XML external entity expansion vulnerability occurs in the XML Query Parser which is available, by default, for any query request with parameters deftype=xmlparser and can be exploited to upload malicious data to the /upload request handler or as Blind XXE using ftp wrapper in order to read arbitrary local files from the Solr server. Note also that the second vulnerability relates to remote code execution using the RunExecutableListener available on all affected versions of Solr.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
85
EG Risk 85/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation92% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
92%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 14, 2017

Last Modified

June 17, 2026

Advisory Details (9)

Auto-updated Oct 6, 2026
Patch available. Sources: redhat.
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2018:0003
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 6.

https://access.redhat.com/errata/RHSA-2018:0002
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2017:3452
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2017:3451
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2017:3244
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2017:3124
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 6 and 7.

https://access.redhat.com/errata/RHSA-2017:3123
generic

CVE-2017-12629 - PSIRT.COM

http://www.securityfocus.com/bid/101261
generic

oss-security - CVE-2017-12629 Solr: Code execution via entity expansion

http://openwall.com/lists/oss-security/2017/10/13/1

Vendor Advisories for CVE-2017-12629(7)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntusolr-tomcat (3.6.2+dfsg-8ubuntu0.1) @ xenial2026-05-20ubuntu
redhatlucene2023-03-20redhat
redhateap7-jboss-ec2-eap-0:7.0.9-2.GA_redhat_2.ep7.el72018-01-03redhat
redhateap7-wildfly-javadocs-0:7.0.9-2.GA_redhat_3.1.ep7.el72018-01-03redhat
redhatlucene-core2018-01-03redhat
redhateap7-wildfly-javadocs-0:7.0.9-2.GA_redhat_3.1.ep7.el62018-01-03redhat
redhatrh-java-common-lucene-0:4.8.0-6.9.el72017-12-12redhat
redhatrh-java-common-lucene5-0:5.4.1-2.4.el72017-12-12redhat
redhatpatch2017-11-16redhat
redhatpatch2017-11-06redhat
redhateap7-lucene-solr-0:5.3.1-4.redhat_2.1.ep7.el72017-11-06redhat

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

(8 across 8 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
lucene-solr—
  • every version up to 3.6.2+dfsg-11: fixed in 3.6.2+dfsg-11
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
lucene-solr—
  • every version up to 3.6.2+dfsg-11: fixed in 3.6.2+dfsg-11
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
lucene-solr—
  • every version up to 3.6.2+dfsg-11: fixed in 3.6.2+dfsg-11
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
lucene-solr—
  • every version up to 3.6.2+dfsg-11: fixed in 3.6.2+dfsg-11
—
Debian:7(1)
PackageVulnerable rangeFix by version rangeDependents
lucene-solr3.6.0+dfsg-1, 3.6.0+dfsg-1+deb7u1, 3.6.0+dfsg-1+deb7u2
  • every version up to 3.6.0+dfsg-1+deb7u3: fixed in 3.6.0+dfsg-1+deb7u3
—
Debian:8(1)
PackageVulnerable rangeFix by version rangeDependents
lucene-solr3.6.2+dfsg-5
  • every version up to 3.6.2+dfsg-5+deb8u1: fixed in 3.6.2+dfsg-5+deb8u1
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
lucene-solr3.6.2+dfsg-10
  • every version up to 3.6.2+dfsg-10+deb9u1: fixed in 3.6.2+dfsg-10+deb9u1
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.apache.solr:solr-core5.5.0, 5.5.1, 5.5.2, 5.5.3, 5.5.4
  • 7.0.0 up to 7.1.0: fixed in 7.1.0
  • 6.0.0 up to 6.6.2: fixed in 6.6.2
  • 5.5.0 up to 5.5.5: fixed in 5.5.5
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(5)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 2× in last 7d / 9× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-08 16:35 UTCEPSS rescore
  2. 2026-10-04 02:14 UTCOSV refresh
  3. 2026-09-30 14:58 UTCEPSS rescore
  4. 2026-09-30 09:24 UTCEG score recompute
  5. 2026-09-24 13:59 UTCEPSS rescore
  6. 2026-09-19 15:36 UTCEPSS rescore
  7. 2026-09-17 19:22 UTCEPSS rescore
  8. 2026-09-14 16:14 UTCOSV refresh
  9. 2026-09-12 14:55 UTCEPSS rescore
  10. 2026-09-10 09:26 UTCEPSS rescore
  11. 2026-08-30 19:13 UTCEPSS rescore
  12. 2026-08-28 21:36 UTCEPSS rescore
  13. 2026-08-26 16:13 UTCOSV refresh
  14. 2026-08-24 14:10 UTCEPSS rescore
  15. 2026-08-10 06:09 UTCOSV refresh
  16. 2026-08-05 19:12 UTCEPSS rescore
  17. 2026-07-30 16:24 UTCEPSS rescore
  18. 2026-07-25 06:41 UTCOSV refresh
  19. 2026-07-23 14:15 UTCEPSS rescore
  20. 2026-07-23 01:26 UTCEG score recompute
  21. 2026-07-22 22:05 UTCEG score recompute
  22. 2026-07-19 14:28 UTCEPSS rescore
  23. 2026-07-19 14:28 UTCEPSS rescore
  24. 2026-07-13 06:09 UTCEPSS rescore
  25. 2026-07-12 05:43 UTCEPSS rescore
Show 30 more
  1. 2026-07-11 08:24 UTCEPSS rescore
  2. 2026-07-08 01:05 UTCOSV refresh
  3. 2026-07-01 15:02 UTCEPSS rescore
  4. 2026-07-01 15:02 UTCEPSS rescore
  5. 2026-06-25 13:47 UTCEPSS rescore
  6. 2026-06-25 13:47 UTCEPSS rescore
  7. 2026-06-23 21:30 UTCEPSS rescore
  8. 2026-06-19 12:55 UTCOSV refresh
  9. 2026-06-16 17:50 UTCEPSS rescore
  10. 2026-06-15 17:45 UTCEPSS rescore
  11. 2026-06-04 13:10 UTCEPSS rescore
  12. 2026-06-04 13:10 UTCEPSS rescore
  13. 2026-05-31 00:14 UTCEPSS rescore
  14. 2026-05-30 20:53 UTCOSV refresh
  15. 2026-05-28 13:42 UTCEPSS rescore
  16. 2026-05-28 13:42 UTCEPSS rescore
  17. 2026-05-26 13:42 UTCEPSS rescore
  18. 2026-05-26 13:42 UTCEPSS rescore
  19. 2026-05-20 08:21 UTCVendor advisory
  20. 2026-05-20 04:12 UTCVendor advisory
  21. 2026-05-20 00:03 UTCVendor advisory
  22. 2026-05-19 19:55 UTCVendor advisory
  23. 2026-05-19 15:46 UTCVendor advisory
  24. 2026-05-19 11:38 UTCVendor advisory
  25. 2026-05-19 07:22 UTCVendor advisory
  26. 2026-05-19 03:12 UTCVendor advisory
  27. 2026-05-18 23:04 UTCEG score recompute
  28. 2026-05-18 23:04 UTCVendor advisory
  29. 2026-05-18 21:30 UTCEPSS rescore
  30. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-43009✓ verified
    First seen Oct 17, 2017

    Apache Solr 7.0.1 - XML External Entity Expansion / Remote Code Execution

    Open source ↗
  • Nucleihttp/cves/2017/CVE-2017-12629.yaml
    First seen Jan 1, 2017

    Apache Solr <= 7.1 - XML Entity Injection

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2017-12629?
CVE-2017-12629 is a critical vulnerability published on October 14, 2017. Remote code execution occurs in Apache Solr before 7.1 with Apache Lucene before 7.1 by exploiting XXE in conjunction with use of a Config API add-listener command to reach the RunExecutableListener class. Elasticsearch, although it uses Lucene, is NOT vulnerable to this. Note that the XML external…
When was CVE-2017-12629 disclosed?
CVE-2017-12629 was first published on October 14, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-12629 actively exploited?
CVE-2017-12629 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 92% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-12629?
CVE-2017-12629 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-12629?
A fix for CVE-2017-12629 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2017-12629 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-12629

Explore →

Is Your Infrastructure Affected by CVE-2017-12629?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs