A flaw was found in Open vSwitch. When Open vSwitch is configured with a conntrack flow using FTP helpers over the userspace datapath, a remote attacker can send a specially crafted FTP stream with an EPASV command exceeding 255 characters. This heap access error can lead to a crash, resulting in a Denial of Service (DoS) for the affected system.
CVE-2026-34956
Score 5.9 from GitHub Security Advisory published 2026-05-05. NVD baseline CVSS 5.9; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.9
- EG Score
- 5.9(medium)
- EG Risk
- 27(Track)EG Risk 27/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 computedSeverity59% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 34%
- KEV
- Not listed
Published
May 5, 2026
Last Modified
September 1, 2026
Advisory Details (3)
Auto-updated May 5, 2026oss-security - [ADVISORY] CVE-2026-34956: Open vSwitch: Invalid memory access in conntrack FTP alg.
http://www.openwall.com/lists/oss-security/2026/03/31/152453459 – (CVE-2026-34956) CVE-2026-34956 openvswitch: Open vSwitch: Denial of Service via malformed FTP EPASV command
https://bugzilla.redhat.com/show_bug.cgi?id=2453459Vendor Advisories for CVE-2026-34956(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| openvswitch | 2.15.0+ds1-10 ... 3.7.1-3 (62 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| openvswitch | 3.1.0-2 ... 3.7.1-3 (36 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| openvswitch | 3.5.0-1 ... 3.7.1-3 (14 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| openvswitch | 3.5.0-1 ... 3.7.0~git20260211.8c6ebf8-1~1.gbp9127d3 (11 versions) | 3.7.1-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 67× 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.
Showing the most recent 100 of 215 total refreshes for this CVE.
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 13:48 UTCVendor advisory
- 2026-09-01 13:48 UTCGHSA enrichment
- 2026-09-01 12:22 UTCEG score recompute
- 2026-09-01 12:22 UTCVendor advisory
- 2026-09-01 12:22 UTCGHSA enrichment
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-31 16:42 UTCEG score recompute
- 2026-08-31 16:42 UTCVendor advisory
- 2026-08-31 16:42 UTCGHSA enrichment
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-23 21:11 UTCEG score recompute
- 2026-08-23 21:11 UTCVendor advisory
- 2026-08-23 21:11 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 13:19 UTCVendor advisory
- 2026-08-21 13:19 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-08-21 12:32 UTCEG score recompute
- 2026-08-21 12:32 UTCVendor advisory
- 2026-08-21 12:32 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 13:03 UTCEG score recompute
- 2026-08-17 13:03 UTCVendor advisory
- 2026-08-17 13:03 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 04:59 UTCEG score recompute
- 2026-08-16 04:59 UTCVendor advisory
- 2026-08-16 04:59 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 03:35 UTCEG score recompute
- 2026-08-14 03:35 UTCVendor advisory
- 2026-08-14 03:35 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 18:11 UTCEG score recompute
- 2026-08-12 18:11 UTCVendor advisory
- 2026-08-12 18:11 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 16:03 UTCEG score recompute
- 2026-08-11 16:03 UTCVendor advisory
- 2026-08-11 16:03 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 08:09 UTCEG score recompute
- 2026-08-10 08:09 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 06:08 UTCEG score recompute
- 2026-08-09 06:08 UTCVendor advisory
- 2026-08-09 06:08 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 04:07 UTCEG score recompute
- 2026-08-08 04:07 UTCVendor advisory
- 2026-08-08 04:07 UTCGHSA enrichment
- 2026-08-07 02:05 UTCEG score recompute
- 2026-08-07 02:05 UTCVendor advisory
- 2026-08-07 02:05 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-05 22:26 UTCEG score recompute
- 2026-08-05 22:26 UTCVendor advisory
- 2026-08-05 22:26 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-03 19:57 UTCEG score recompute
- 2026-08-03 19:57 UTCVendor advisory
- 2026-08-03 19:57 UTCGHSA enrichment
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 05:17 UTCEG score recompute
- 2026-08-02 05:17 UTCVendor advisory
- 2026-08-02 05:17 UTCGHSA enrichment
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:10 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-120
- CVE-2010-10016EG 10.0CRITICAL
- CVE-2012-10035EG 10.0CRITICAL
- CVE-2011-4862EG 10.0EPSS p100HIGH
- CVE-2008-3496EG 10.0HIGH
- CVE-2007-1770EG 10.0EPSS p97HIGH
- CVE-2002-1337EG 10.0EPSS p99HIGH
- CVE-2001-0554EG 10.0EPSS p98HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-1999-1237EG 10.0EPSS p94HIGH
- CVE-1999-0385EG 10.0EPSS p97HIGH
Frequently asked(5)
What is CVE-2026-34956?
When was CVE-2026-34956 disclosed?
Is CVE-2026-34956 actively exploited?
What is the CVSS score of CVE-2026-34956?
How do I remediate CVE-2026-34956?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-34956
Is Your Infrastructure Affected by CVE-2026-34956?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.