Skip to main content
VulnerabilityPublished

CVE-2026-77620: vectordotdev vector · Data Amplification

Affects vectordotdev vectorSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 0.57.0 soon.

Data as of 5 Nov 2026, 23:24 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.57.0
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade vector and github/vectordotdev/vector to 0.57.0.

Affected software

ProductAffectedFixed in
vectordotdevvectorAffected
  • >=0.15.0 <0.57.0
Fixed in
  • 0.57.0
crates.iogithub/vectordotdev/vectorpkg:cargo/github/vectordotdev/vectorOther threatsAffected
  • >=0.15.0 <0.57.0
Fixed in
  • 0.57.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Vector to version 0.57.0 or later, where this vulnerability is fixed. No other mitigation or temporary fix is indicated. Patch status is confirmed by the vendor advisory stating the fix in 0.57.0.

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.

References

Community reviews

Loading reviews…