CVE-2018-11788

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 7.5%, top 6% 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
Trending — 3 sources updated this weekElevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 7%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Apache Karaf provides a features deployer, which allows users to "hot deploy" a features XML by dropping the file directly in the deploy folder. The features XML is parsed by XMLInputFactory class. Apache Karaf XMLInputFactory class doesn't contain any mitigation codes against XXE. This is a potential security risk as an user can inject external XML entities in Apache Karaf version prior to 4.1.7 or 4.2.2. It has been fixed in Apache Karaf 4.1.7 and 4.2.2 releases.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
—
EPSS
93.8%
KEV
Not listed

Published

January 7, 2019

Last Modified

November 21, 2024

Advisory Details (2)

Auto-updated May 28, 2026
No patch confirmed yet.
generic
http://www.securityfocus.com/bid/106479
generic
http://karaf.apache.org/security/cve-2018-11788.txt

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.apache.karaf.specs:org.apache.karaf.specs.java.xml—4.1.7—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 41× 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-07-22 22:12 UTCEG score recompute
  2. 2026-07-22 14:04 UTCEPSS rescore
  3. 2026-07-21 15:21 UTCEPSS rescore
  4. 2026-07-21 00:47 UTCOSV refresh
  5. 2026-07-20 17:04 UTCEPSS rescore
  6. 2026-07-20 17:04 UTCEPSS rescore
  7. 2026-07-19 14:28 UTCEPSS rescore
  8. 2026-07-19 02:26 UTCEPSS rescore
  9. 2026-07-19 02:26 UTCEPSS rescore
  10. 2026-07-16 16:59 UTCEPSS rescore
  11. 2026-07-16 16:59 UTCEPSS rescore
  12. 2026-07-15 16:55 UTCEPSS rescore
  13. 2026-07-15 01:56 UTCEPSS rescore
  14. 2026-07-13 22:26 UTCEPSS rescore
  15. 2026-07-13 06:10 UTCEPSS rescore
  16. 2026-07-12 05:43 UTCEPSS rescore
  17. 2026-07-11 08:24 UTCEPSS rescore
  18. 2026-07-09 19:06 UTCEPSS rescore
  19. 2026-07-08 15:11 UTCEPSS rescore
  20. 2026-07-07 13:42 UTCEPSS rescore
  21. 2026-07-07 13:42 UTCEPSS rescore
  22. 2026-07-06 16:24 UTCEPSS rescore
  23. 2026-07-06 16:24 UTCEPSS rescore
  24. 2026-07-06 02:20 UTCEPSS rescore
  25. 2026-07-05 02:27 UTCEPSS rescore
Show 61 more
  1. 2026-07-04 06:28 UTCEPSS rescore
  2. 2026-07-03 19:56 UTCOSV refresh
  3. 2026-07-02 16:54 UTCEPSS rescore
  4. 2026-07-01 15:03 UTCEPSS rescore
  5. 2026-07-01 15:03 UTCEPSS rescore
  6. 2026-06-30 23:19 UTCEPSS rescore
  7. 2026-06-30 23:19 UTCEPSS rescore
  8. 2026-06-29 14:03 UTCEPSS rescore
  9. 2026-06-28 04:53 UTCEPSS rescore
  10. 2026-06-28 04:53 UTCEPSS rescore
  11. 2026-06-27 03:06 UTCEPSS rescore
  12. 2026-06-25 13:47 UTCEPSS rescore
  13. 2026-06-25 13:47 UTCEPSS rescore
  14. 2026-06-24 14:02 UTCEPSS rescore
  15. 2026-06-24 14:02 UTCEPSS rescore
  16. 2026-06-23 21:30 UTCEPSS rescore
  17. 2026-06-22 14:23 UTCEPSS rescore
  18. 2026-06-21 01:57 UTCEPSS rescore
  19. 2026-06-21 01:57 UTCEPSS rescore
  20. 2026-06-19 19:23 UTCEPSS rescore
  21. 2026-06-18 17:50 UTCEPSS rescore
  22. 2026-06-18 17:50 UTCEPSS rescore
  23. 2026-06-17 17:50 UTCEPSS rescore
  24. 2026-06-17 17:50 UTCEPSS rescore
  25. 2026-06-16 17:50 UTCEPSS rescore
  26. 2026-06-16 17:50 UTCEPSS rescore
  27. 2026-06-15 17:45 UTCEPSS rescore
  28. 2026-06-15 08:13 UTCOSV refresh
  29. 2026-06-14 23:14 UTCEPSS rescore
  30. 2026-06-14 23:14 UTCEPSS rescore
  31. 2026-06-13 22:58 UTCEPSS rescore
  32. 2026-06-13 22:58 UTCEPSS rescore
  33. 2026-06-12 23:09 UTCEPSS rescore
  34. 2026-06-11 13:57 UTCEPSS rescore
  35. 2026-06-10 22:16 UTCEPSS rescore
  36. 2026-06-10 13:19 UTCEPSS rescore
  37. 2026-06-07 15:22 UTCEPSS rescore
  38. 2026-06-07 15:22 UTCEPSS rescore
  39. 2026-06-06 13:45 UTCEPSS rescore
  40. 2026-06-06 13:45 UTCEPSS rescore
  41. 2026-06-05 22:45 UTCEPSS rescore
  42. 2026-06-05 22:44 UTCEPSS rescore
  43. 2026-06-05 06:08 UTCEPSS rescore
  44. 2026-06-05 06:08 UTCEPSS rescore
  45. 2026-06-04 13:10 UTCEPSS rescore
  46. 2026-06-04 13:10 UTCEPSS rescore
  47. 2026-06-02 20:11 UTCEPSS rescore
  48. 2026-06-02 20:11 UTCEPSS rescore
  49. 2026-06-01 13:49 UTCEPSS rescore
  50. 2026-05-31 00:14 UTCEPSS rescore
  51. 2026-05-31 00:14 UTCEPSS rescore
  52. 2026-05-29 13:41 UTCEPSS rescore
  53. 2026-05-28 13:42 UTCEPSS rescore
  54. 2026-05-28 13:42 UTCEPSS rescore
  55. 2026-05-27 23:43 UTCEG score recompute
  56. 2026-05-27 13:38 UTCEPSS rescore
  57. 2026-05-27 13:38 UTCEPSS rescore
  58. 2026-05-26 13:42 UTCEPSS rescore
  59. 2026-05-26 13:42 UTCEPSS rescore
  60. 2026-05-26 07:17 UTCEPSS rescore
  61. 2026-05-26 07:17 UTCEPSS rescore

Publicly available exploits

(1 reference)

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

  • GitHub PoCbrianwrf/CVE-2018-11788
    First seen Jan 6, 2019

    Apache Karaf XXE Vulnerability (CVE-2018-11788)

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2018-11788?
CVE-2018-11788 is a critical vulnerability published on January 7, 2019. Apache Karaf provides a features deployer, which allows users to "hot deploy" a features XML by dropping the file directly in the deploy folder. The features XML is parsed by XMLInputFactory class. Apache Karaf XMLInputFactory class doesn't contain any mitigation codes against XXE. This is a…
When was CVE-2018-11788 disclosed?
CVE-2018-11788 was first published in the National Vulnerability Database on January 7, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-11788 actively exploited?
CVE-2018-11788 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 93.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-11788?
CVE-2018-11788 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2018-11788?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-11788, 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-2018-11788

Explore →

Is Your Infrastructure Affected by CVE-2018-11788?

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

Start Free Scan →Browse All CVEs