CVE-2026-26932

Process crash via unchecked PostgreSQL array index

Published Feb 26, 2026 · Updated Feb 26, 2026

Improper array-index validation in Elastic Packetbeat 8.0.0 through 8.19.10 and 9.0.0 through 9.2.4 allows attackers to crash the process. The PostgreSQL protocol parser uses an insufficiently validated index while processing a crafted packet, causing an out-of-range Go runtime panic that terminates Packetbeat. Reachability requires the pgsql protocol to be explicitly enabled and configured to monitor traffic on the targeted port; the bounded consequence is loss of packet analysis until the process restarts.

CVSS severity7.5
High
EPSS probability0.45%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper array-index validation in Elastic Packetbeat 8.0.0 through 8.19.10 and 9.0.0 through 9.2.4 allows attackers to crash the process. The PostgreSQL protocol parser uses an insufficiently validated index while processing a crafted packet, causing an out-of-range Go runtime panic that terminates Packetbeat. Reachability requires the pgsql protocol to be explicitly enabled and configured to monitor traffic on the targeted port; the bounded consequence is loss of packet analysis until the process restarts.

The record

CVE
CVE-2026-26932
Published
Feb 26, 2026
Updated
Feb 26, 2026
Vendor
Elastic
Product
Packetbeat
Classifications
CWE-129, CAPEC-153, T1499
Attack vector
adjacent
Privileges
Unavailable

Timeline

How it unfolded

  1. Feb 26, 2026CVE publishedPublication date reported by the CVE source.
  2. Feb 26, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=8.0.0 <=8.19.10
  2. Affected versionversion=9.0.0 <=9.2.4

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesUnavailable in this record.

What is affected?

Elastic · Packetbeatversion=8.0.0 <=8.19.10; version=9.0.0 <=9.2.4

Published CVSS scores

7.5NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
5.7ElasticCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-129Improper Validation of Array Index
CAPEC-153Input Data Manipulation
T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo