How severe is CVE-2019-7609?

CVE-2019-7609 has a CVSS score of 10/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-7609?

Affected package information for CVE-2019-7609 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2019-7609?

Upgrade the affected component to the fixed release for CVE-2019-7609, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.

How do I detect CVE-2019-7609 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2019-7609 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2019-7609 actively exploited in the wild?

Yes. There are 16 known exploit references for CVE-2019-7609, including 10 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-7609?

CVE-2019-7609 has an EPSS (Exploit Prediction Scoring System) score of 95.3%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2019-7609 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2019-7609 (Kibana Arbitrary Code Execution) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-01-10. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-07-10. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2019-7609?

CVE-2019-7609 is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2019-7609?

A Nuclei detection template exists for CVE-2019-7609, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2019-7609 published, and has it been updated?

CVE-2019-7609 was published on March 25, 2019 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

CISA KEV · ACTIVELY EXPLOITED

CRITICAL severity

CVE-2019-7609 — elasticsearch

CRITICAL

CVE-2019-7609 is a critical-severity (CVSS 10) Code Injection vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2022-01-10) — treat it as actively exploited and patch now. A fix is available — see the affected versions and patch details below.

Published

Mar 25, 2019

Updated

Oct 20, 2026

Affected

2 products

Patched

See advisory

Exploits

16 known

Exploitation data as of Oct 21, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2022-01-10. Federal agencies were required to remediate by 2022-07-10.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2019-7609.

EPSS Exploitation Probability

via FIRST.org ↗

95.3%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2019-7609 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 394,415 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.

Description

Kibana versions before 5.6.15 and 6.6.1 contain an arbitrary code execution flaw in the Timelion visualizer. An attacker with access to the Timelion application could send a request that will attempt to execute javascript code. This could possibly lead to an attacker executing arbitrary commands with permissions of the Kibana process on the host system.

Affected Products

2 products · 4 configurations

Application

kibanaelastic

≥ 6.0.0 && < 6.6.1

range

Application

openshift container platformredhat

2 versions

3.114.1

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.