CVE-2026-26932
Elasticsearch Packetbeat 8.0.0 – 8.19.11
Raw vector
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-26932 is a medium-severity Improper Validation of Array Index (CWE-129) vulnerability in Elasticsearch Packetbeat. Its CVSS base score is 5.7 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 38th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-26932 is an Improper Validation of Array Index vulnerability (CWE-129) in the PostgreSQL protocol parser within Packetbeat. This issue enables a Denial of Service via Input Data Manipulation (CAPEC-153), where an attacker can send a specially crafted packet that triggers a Go runtime panic, terminating the Packetbeat process. The vulnerability is present only when the pgsql protocol is explicitly enabled and configured to monitor traffic on the targeted port.
Attackers with adjacent network access (AV:A), low attack complexity (AC:L), and low privileges (PR:L) can exploit this without user interaction (UI:N) in an unchanged impact scope (S:U). Successful exploitation results in high availability impact (A:H) through process termination, with no effects on confidentiality (C:N) or integrity (I:N), as scored at CVSS 5.7 (CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).
The Elastic Security Advisory ESA-2026-10, detailed at https://discuss.elastic.co/t/packetbeat-8-19-11-9-2-5-security-update-esa-2026-10/385247, addresses this vulnerability with security updates for Packetbeat.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-8864
Vulnerability Data
Improper Validation of Array Index (CWE-129) in the PostgreSQL protocol parser in Packetbeat can lead Denial of Service via Input Data Manipulation (CAPEC-153). An attacker can send a specially crafted packet causing a Go runtime panic that terminates the Packetbeat…
more
process. This vulnerability requires the pgsql protocol to be explicitly enabled and configured to monitor traffic on the targeted port.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input validation and bounds checking that prevent improper array indexing.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect out-of-bounds array access but does not prevent the weakness by itself.
Secure development lifecycle mandates input validation and bounds checking that directly prevents improper array indexing.
Application security requirements include validation of untrusted input used for indexing or addressing memory structures.
Secure architecture principles encourage defensive coding patterns that reduce index-related vulnerabilities.
Secure coding standards explicitly require bounds checking and validation of array indices derived from untrusted data.