AI Science Tracker

Packetbeat PostgreSQL DataRow parsing could panic

Packetbeat · AI involvement attributed to AISLE analyzer (specific model/version not disclosed)

Finding and attribution

A crafted PostgreSQL DataRow could claim more fields than the earlier RowDescription, causing an unchecked index and Go runtime panic in Packetbeat. The issue requires the PostgreSQL parser to be configured for monitored traffic.

Product: Packetbeat. AI system: AISLE analyzer (specific model/version not disclosed). Team / organization: AISLE.

CVE identifiers: CVE-2026-26932.

AI and human contribution (source account): AISLE’s April 30, 2026 report states that its analyzer found nine Elastic Beats denial-of-service issues and says these issues were discovered and reported by Pavel Kohout using AISLE’s analyzer. The exact model/version and human/model division of work are not disclosed.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The public vendor/CVE disclosure date and public campaign-level AI attribution date are recorded separately. The vendor security advisory establishes the affected component, conditions, and remediation. No in-the-wild exploitation claim is made. Elastic credits a different reporter in its per-CVE record; AISLE’s independently itemized campaign claims this finding, so no priority or sole-authorship claim is made.

Remediation status: fix documented. Elastic’s ESA-2026-10 documents the DataRow parser crash and fixed releases. The CVE-specific Elastic record credits a different reporter, while AISLE’s primary campaign explicitly says the itemized Packetbeat finding was discovered and reported by Pavel Kohout using its analyzer; no priority claim is made.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 26 Feb 2026. AI attribution dated 30 Apr 2026. Sources checked 15 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Medium · highest recorded score 5.7. Documented technical effects: denial of service.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

  • CVE-2026-26932: CVSS 3.1 · 5.7 (Medium) · CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H · Assessment scenarios: GENERAL. elastic (CNA; CVE Program record) · checked 16 Nov 2026.

CVE-2026-26932: denial of service.
Prerequisites / affected scope: Requires PostgreSQL protocol parsing to be explicitly enabled and configured on the target port. A crafted packet triggers a Go runtime panic that terminates Packetbeat..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.

Documented fix: Elastic’s ESA-2026-10 documents the DataRow parser crash and fixed releases. The CVE-specific Elastic record credits a different reporter, while AISLE’s primary campaign explicitly says the itemized Packetbeat finding was discovered and reported by Pavel Kohout using its analyzer; no priority claim is made.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases