CVE-2026-77619

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 57% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Vector is a high-performance observability data pipeline. From 0.15.0 until 0.57.0, the logstash source reads a 32-bit compressed-frame length from the network and uses it to size an in-memory buffer without an upper bound. An unauthenticated remote peer that can reach the default 0.0.0.0:5044 listener can send a minimal frame declaring a multi-gigabyte payload, causing an excessive allocation that can abort Vector or invoke the host OOM killer. Because the allocation follows the declared length rather than bytes transmitted, the attacker has low resource cost, and process termination can halt log ingestion for every tenant on a shared pipeline. This issue is fixed in version 0.57.0.

CVSS v3
8.7
EG Score
8.7(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity87% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

September 22, 2026

Last Modified

September 22, 2026

Advisory Details (4)

Auto-updated Sep 22, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

v0.57.0

Patch available: vectordotdev/vector v0.57.0

https://github.com/vectordotdev/vector/releases/tag/v0.57.0
github_commit

commit 3162ed1a2e5e (vectordotdev/vector)

Fix landed in vectordotdev/vector commit 3162ed1a2e5e — awaiting tagged release

https://github.com/vectordotdev/vector/commit/3162ed1a2e5e8d3f210134607518a26aa01e1a37
github_pr

fix(sources): cap compressed and decompressed payload size across network sources to prevent OOM

Fix merged in vectordotdev/vector PR #25819 on 2026-07-13 — awaiting tagged release

https://github.com/vectordotdev/vector/pull/25819
github Patch Available

Unauthenticated denial of service in the `logstash` source via unbounded memory allocation. · Advisory · vectordotdev/vector · GitHub

https://github.com/vectordotdev/vector/security/advisories/GHSA-rrfg-9487-mhp6

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 5× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-24 05:01 UTCEG score recompute
  2. 2026-09-23 17:54 UTCEPSS rescore
  3. 2026-09-22 16:20 UTCEG score recompute
  4. 2026-09-22 15:30 UTCEG score recompute
  5. 2026-09-22 15:29 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-77619?
CVE-2026-77619 is a high vulnerability published on September 22, 2026. Vector is a high-performance observability data pipeline. From 0.15.0 until 0.57.0, the logstash source reads a 32-bit compressed-frame length from the network and uses it to size an in-memory buffer without an upper bound. An unauthenticated remote peer that can reach the default 0.0.0.0:5044…
When was CVE-2026-77619 disclosed?
CVE-2026-77619 was first published in the National Vulnerability Database on September 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-77619 actively exploited?
CVE-2026-77619 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.6% of all scored CVEs.
What is the CVSS score of CVE-2026-77619?
CVE-2026-77619 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-77619?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-77619, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-77619

Explore →

Is Your Infrastructure Affected by CVE-2026-77619?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs