CVE-2023-49921: An issue was discovered by Elastic whereby Watcher search input logged the search query results on DEBUG log level.
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.44% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Elastic Elasticsearch 7.17.16, 8.11.2.
Low priority for now. Upgrade to Elastic Elasticsearch 7.17.16, 8.11.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An issue was discovered by Elastic whereby Watcher search input logged the search query results on DEBUG log level. This could lead to raw contents of documents stored in Elasticsearch to be printed in logs. Elastic has released 8.11.2 and 7.17.16 that resolves this issue by removing this excessive logging. This issue only affects users that use Watcher and have a Watch defined that uses the search input and additionally have set the search input’s logger to DEBUG or finer, for example using: org.elasticsearch.xpack.watcher.input.search, org.elasticsearch.xpack.watcher.input, org.elasticsearch.xpack.watcher, or wider, since the loggers are hierarchical.
- Published
- Jul 26, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 39th percentile
- CWE
- CWE-532
Report tools
Action score
26
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 6.5
- CNA · elastic
- 5.2
- 1.3 point gap
CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| elastic | elasticsearch | cpe:2.3:a:elastic:elasticsearch |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (elastic). Independent of NVD's CPE analysis and usually ahead of it.
Elastic Elasticsearch
- 7.0.0 and later · before 7.17.16affected · semver
- 8.0.0 and later · before 8.11.2affected · semver
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- elastic elasticsearch7.0.0 and later · before 7.17.16
- elastic elasticsearch8.0.0 and later · before 8.11.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.elasticsearch:elasticsearch | from 8.0.0 · before 8.11.2 | 8.11.2 |
| Maven | org.elasticsearch:elasticsearch | before 7.17.16 | 7.17.16 |
Same product
elastic: all recordsOther highest-scoring records for the same primary product.
- CVE-2015-1427The Groovy scripting engine in Elasticsearch before 1.3.8 and 1.4.x before 1.4.3 allows remote attackers to bypass the sandbox protection…KEV99Now
- CVE-2014-3120The default configuration in Elasticsearch before 1.2 enables dynamic scripting, which allows remote attackers to execute arbitrary MVEL…KEV89Now
- CVE-2021-22145A memory disclosure vulnerability was identified in Elasticsearch 7.10.0 to 7.13.3 error reporting.49Plan
Published before and after this one in the same product
- ← EarlierCVE-2024-23445Jun 12, 2024 · Elasticsearch Remote Cluster Search Cross Cluster API Key insufficient restrictions26Monitor
- ← EarlierCVE-2024-37280Jun 13, 2024 · Elasticsearch StackOverflow vulnerability19Monitor
- Later →CVE-2024-23444Jul 31, 2024 · Elasticsearch elasticsearch-certutil csr fails to encrypt private key30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Elastic Elasticsearch | 7.17.16 | Vendor (CNA) |
| Elastic Elasticsearch | 8.11.2 | Vendor (CNA) |
| Maven:org.elasticsearch:elasticsearch | 7.17.16 | Package registry (OSV) |
| Maven:org.elasticsearch:elasticsearch | 8.11.2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-37727441 days apartElasticsearch Insertion of sensitive information in log file22Monitor
- CVE-2023-31417274 days apartElasticsearch Insertion of sensitive information in audit logs17Monitor
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-532 · Insertion of Sensitive Information into Log FileCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.