Advisory record · GHSA-mrfm-jxgf-2h6v

Elasticsearch Improper Access Control vulnerability

CVSS 8.1 HighCriticalIn CISA KEVEPSS 0.89 · 99th percentile

Critical, because:

  • In CISA’s KEV catalogue since 25 Mar 2022: it is known to be exploited.
  • CVSS score 8.1 (7.0 or more) and EPSS 0.89 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical

Published by the GitHub Advisory Database at 17 May 2022, 03:28 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.elasticsearch:elasticsearchMaven<1.4.0.Beta11.4.0.Beta1
Identifiers
GHSA-mrfm-jxgf-2h6v · CVE-2014-3120
Weakness (CWE)
CWE-284
Published
17 May 2022
Updated
22 Oct 2025

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Elasticsearch versions before 1.4.0.Beta1 enable dynamic scripting by default. A remote attacker can use the source parameter of the _search endpoint to run arbitrary MVEL expressions and Java code. The source notes this breaks the vendor's intended security policy only if Elasticsearch does not run in its own isolated virtual machine. Upgrade to version 1.4.0.Beta1 or later.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.1 High 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N/E:H GitHub Advisory Database
  • CISA KEV Listed since 25 Mar 2022: known to be exploited.
  • EPSS 0.89, the 99th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:10 UTC First seen by agentprime
  2. 31 Oct 2026, 15:10 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.