CVE-2023-46673

It was identified that malformed scripts used in the script processor of an Ingest Pipeline could cause an Elasticsearch node to crash when calling the Simulate Pipeline API.

Published: 2023-11-22 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-46673 is rated Moderate Risk (44.9/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.84%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-46673

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.46% 0.84% +0.39%
2 2026-04-13 0.81% 0.46% -0.35%
3 2025-12-10 — 0.81% —

Full EPSS history (10 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-46673

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 3.6 [email protected]
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2023-46673

GitHub Security Advisory for CVE-2023-46673

GHSA-285m-vhfq-xx4h · Severity: medium · Ecosystem: maven — Elasticsearch Improper Handling of Exceptional Conditions

OS Trackers for CVE-2023-46673

vendor priority summary link
redhat medium — https://access.redhat.com/security/cve/CVE-2023-46673
ubuntu medium CVE-2023-46673 medium priority: Ubuntu including 1 source packages (elasticsearch), 12 status rows across 12 suites (bionic, focal, jammy, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 8, ignored 2, needs-triage 2. https://ubuntu.com/security/CVE-2023-46673

Affected software / configurations for CVE-2023-46673

Vendor Product Version Raw CPE
elastic elasticsearch >= 7.0.0, < 7.17.14 cpe:2.3:a:elastic:elasticsearch:*:*:*:*:*:*:*:*
elastic elasticsearch >= 8.0.0, < 8.10.3 cpe:2.3:a:elastic:elasticsearch:*:*:*:*:*:*:*:*

References for CVE-2023-46673

cvelogic Threat Intelligence