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
Elevated
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
65(Track*)
EG Risk 65/100SSVC: Track*

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%
Exploitation40% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
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.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.apache.karaf.specs:org.apache.karaf.specs.java.xml4.1.7

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 ↗

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.