{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-26932 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-26932 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-26932 is a medium-severity denial of service vulnerability in Elastic Packetbeat, published on 26 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-26932 and fix it if it is affected.\n\nWhat it is: CVE-2026-26932 is a medium-severity denial of service vulnerability in Elastic Packetbeat, published on 26 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-26932 in the wild and no public exploit code.\n\nAffected product: Elastic Packetbeat. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-26932/ (Markdown: https://insights.sbomify.com/CVE-2026-26932/index.md)","id":"CVE-2026-26932","markdown":"https://insights.sbomify.com/CVE-2026-26932/index.md","name":"CVE-2026-26932","record":{"aliases":["GHSA-fg9r-q7mv-mcrw"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Packetbeat network monitor","requires_auth":"low_privilege","summary":"An attacker can cause a denial of service in Packetbeat by sending crafted packets to the PostgreSQL protocol parser, requiring explicit configuration.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"packetbeat","vendor":"elasticsearch"}],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-129","name":"Improper Validation of Array Index"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Improper Validation of Array Index in Packetbeat Leading to Denial of Service","id":"CVE-2026-26932","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Improper Validation of Array Index in Packetbeat Leading to Denial of Service","id":"CVE-2026-26933"},"packages":[],"prev":{"headline":"Memory Allocation with Excessive Size Value in Metricbeat Leading to Denial of Service","id":"CVE-2026-26931"},"products":["Packetbeat"],"published":"2026-02-26","related":[{"cvss_score":7.5,"headline":"Denial of Service in Packetbeat","id":"CVE-2017-11480","kev_date_added":null,"published":"2017-12-08"},{"cvss_score":6.5,"headline":"Packetbeat Improper Bounds Check","id":"CVE-2025-68381","kev_date_added":null,"published":"2025-12-18"},{"cvss_score":6.5,"headline":"Packetbeat Out-of-bounds Read","id":"CVE-2025-68382","kev_date_added":null,"published":"2025-12-18"},{"cvss_score":5.7,"headline":"Improper Validation of Array Index in Packetbeat Leading to Denial of Service","id":"CVE-2026-26933","kev_date_added":null,"published":"2026-03-19"},{"cvss_score":5.3,"headline":"Elasticsearch Packetbeat has Excessive Allocation of Memory and CPU via Malicious IPv4 Fragments","id":"CVE-2025-68388","kev_date_added":null,"published":"2025-12-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["Elastic"]},"summary":"An attacker can cause a denial of service in Packetbeat by sending crafted packets to the PostgreSQL protocol parser, requiring explicit configuration.","url":"https://insights.sbomify.com/CVE-2026-26932/"}