{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-77620 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-77620 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-77620 is a high-severity denial of service vulnerability in vectordotdev vector, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-77620 and fix it if it is affected.\n\nWhat it is: CVE-2026-77620 is a high-severity denial of service vulnerability in vectordotdev vector, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-77620 in the wild and no public exploit code.\n\nAffected product: vectordotdev vector. 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-77620/ (Markdown: https://insights.sbomify.com/CVE-2026-77620/index.md)","id":"CVE-2026-77620","markdown":"https://insights.sbomify.com/CVE-2026-77620/index.md","name":"CVE-2026-77620","record":{"aliases":["GHSA-qp6f-fpfx-4gg6"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Observability data pipeline","requires_auth":"none","summary":"Unauthenticated attackers can crash Vector by sending nested compressed frames to the Logstash source, causing stack exhaustion and halting log ingestion.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-409","name":"Improper Handling of Highly Compressed Data (Data Amplification)"}],"description":"Vector is a high-performance observability data pipeline. From 0.15.0 until 0.57.0, the logstash source feeds each decompressed frame back into its decoder without limiting nested compression depth. An unauthenticated remote peer that can reach the default 0.0.0.0:5044 listener can send many nested compressed frames, causing recursive decoding that exhausts the worker thread stack and aborts the process. The same nested construction amplifies decompressed input, and process termination can halt log ingestion for every tenant on a shared pipeline. This issue is fixed in version 0.57.0.","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":"Denial of service in vector","id":"CVE-2026-77620","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Vector: Arbitrary file write in the file sink via templated path (path traversal).","id":"CVE-2026-77621"},"packages":[],"prev":{"headline":"Vector: Unauthenticated denial of service in the `logstash` source via unbounded memory allocation.","id":"CVE-2026-77619"},"products":["vector"],"published":"2026-09-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-22","vendors":["vectordotdev"]},"summary":"Unauthenticated attackers can crash Vector by sending nested compressed frames to the Logstash source, causing stack exhaustion and halting log ingestion.","url":"https://insights.sbomify.com/CVE-2026-77620/"}