dbcve.org
PacketbeatApplication · Elasticsearch

CVE-2026-26932

HIGH · 7.5 CVSS v3.1 Published 2026-02-26
Fix available
A fix is available. Upgrade to 8.19.11 / 9.2.5 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 process. This vulnerability requires the pgsql protocol to be explicitly enabled and configured to monitor traffic on the targeted port.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A CWE-129 (Improper Validation of Array Index) vulnerability exists in the PostgreSQL protocol parser within Packetbeat. An attacker can send a specially crafted packet that triggers an out-of-bounds array access, causing a Go runtime panic and terminating the Packetbeat process. Successful exploitation requires the pgsql protocol to be explicitly enabled and configured to monitor the targeted port.

MitigationDisable the PostgreSQL protocol in Packetbeat if not required, or implement network segmentation to restrict access to the monitored ports. Apply the vendor patch when available to fix the array index validation logic in the pgsql parser.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PacketbeatApplication
Affected:>= 8.0.0, < 8.19.11>= 9.0.0, < 9.2.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Packetbeat version
    Run `packetbeat version` or inspect the installed package to determine the exact version number
    Affected if Version is >= 8.0.0 and < 8.19.11, or >= 9.0.0 and < 9.2.5
  2. Locate Packetbeat configuration file
    Find the packetbeat.yml configuration file, typically in /etc/packetbeat/ or the configuration directory used during installation
    Affected if Configuration file exists and is accessible for inspection
  3. Verify if pgsql protocol is enabled
    Search the packetbeat.yml file for `pgsql:` protocol section or entries containing `pgsql` under the `packetbeat.protocols:` configuration block
    Affected if The pgsql protocol is present and enabled in the configuration
  4. Check pgsql port configuration
    Look for `ports:` directive under the pgsql protocol section to identify which ports Packetbeat is configured to monitor for PostgreSQL traffic
    Affected if A port number is specified for the pgsql protocol, indicating it will parse PostgreSQL traffic on that port

Affected if Packetbeat version is within the vulnerable range AND the pgsql protocol is enabled with a configured port in the Packetbeat configuration file.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.19.11 / 9.2.5 or later
Fixed in 8.19.119.2.5
Interim mitigation

Disable the PostgreSQL protocol in Packetbeat if not required, or implement network segmentation to restrict access to the monitored ports. Apply the vendor patch when available to fix the array index validation logic in the pgsql parser.

Recommended fix High confidence

Packetbeat 8.19.11 (or 9.2.5 for 9.x branch)

  1. 1. Identify the current Packetbeat version by running `packetbeat version`
  2. 2. Stop the Packetbeat service before upgrading (e.g., `systemctl stop packetbeat` or `service packetbeat stop`)
  3. 3. Upgrade Packetbeat using your package manager or download the appropriate fixed version (8.19.11 for 8.x line or 9.2.5 for 9.x line) from elastic.co/downloads/packetbeat
  4. 4. Verify the new version installed correctly by running `packetbeat version`
  5. 5. Start the Packetbeat service (e.g., `systemctl start packetbeat` or `service packetbeat start`)
  6. 6. Confirm Packetbeat is running without errors and monitoring PostgreSQL traffic as expected
Caveat Check the Elastic Stack 8.19.x or 9.2.x release notes for any breaking changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Packetbeat Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26932 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-26932 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data