OESA-2026-1961 (CVE-2026-34956)

Vulnerability from osv_openeuler – Published: 2026-04-17 11:10 – Updated: 2026-08-06 11:10 – Source website
VLAI
Summary
openvswitch security update
Details

Open vSwitch provides standard network bridging functions and support for the OpenFlow protocol for remote per-flow control of traffic.

Security Fix(es):

"Description\n===========\n\nMultiple versions of Open vSwitch are vulnerable to crafted FTP payloads\ncausing invalid memory accesses, potential denial of service, and possible\nremote code execution. This impacts the userspace implementation of\nconntrack. Triggering the vulnerability requires that Open vSwitch has\nconfigured conntrack flows specifying the FTP alg handler. Conntrack\nhandlers in userspace are not automatically applied.\n\nThe issue is caused by type narrowing when copying FTP substrings. It\nhas existed in all versions of the userspace conntrack supporting the\nFTP handler. This was introduced with Open vSwitch version 2.8.0 and\naffects all versions up to 3.7.0.\n\nThe Common Vulnerabilities and Exposures project (cve.mitre.org) has\nassigned CVE-2026-34956 identifier to this issue. At the time of writing\nthe flaw is considered with Moderate impact and 5.9 CVSS.\n\n\nMitigation\n==========\n\nFor any affected version of Open vSwitch, avoiding the FTP alg will\nprevent the issue from triggering. The Open vSwitch team does not\nrecommend attempting to mitigate the vulnerability this way because it\nmay impact packet forwarding.\n\nBy default, alg handlers are not installed, and must be added as part\nof the OpenFlow rules (via 'ct(alg=ftp)' for example).\n\nUsers can check if they are using affected flows by looking at their\nOpenFlow ruleset for their bridges, for example:\n\n ovs-ofctl dump-flows <bridge> | grep 'alg=ftp'\n\nWe have found that Open vSwitch may be subject to heap corruption when\nprocessing FTP messages.\n\n\nFix\n===\n\nPatches to fix this vulnerability in Open vSwitch 3.3 and newer are\napplied to the appropriate branches, and the original patch is located\nat:", 'Recommendation\n==============\n\nWe recommend that users of Open vSwitch apply the included patch, or\nupgrade to a known patched version of Open vSwitch. These include:\n\n 3.3.9\n 3.4.6\n 3.5.4\n 3.6.3\n* 3.7.1\n\n\nAcknowledgements\n================\n\nThe Open vSwitch team wishes to thank the reporter:\n\n * Seiji Sakurai <Seiji.Sakurai () outlook com>'

Severity
5.9 (Medium)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
References
To clipboard 

{
  "affected": [
    {
      "ecosystem_specific": {
        "aarch64": [
          "network-scripts-openvswitch-3.2.1-5.oe2403sp2.aarch64.rpm",
          "openvswitch-3.2.1-5.oe2403sp2.aarch64.rpm",
          "openvswitch-debuginfo-3.2.1-5.oe2403sp2.aarch64.rpm",
          "openvswitch-debugsource-3.2.1-5.oe2403sp2.aarch64.rpm",
          "openvswitch-devel-3.2.1-5.oe2403sp2.aarch64.rpm",
          "openvswitch-dpdk-3.2.1-5.oe2403sp2.aarch64.rpm",
          "openvswitch-ipsec-3.2.1-5.oe2403sp2.aarch64.rpm",
          "openvswitch-testcontroller-3.2.1-5.oe2403sp2.aarch64.rpm",
          "python3-openvswitch-3.2.1-5.oe2403sp2.aarch64.rpm"
        ],
        "noarch": [
          "openvswitch-test-3.2.1-5.oe2403sp2.noarch.rpm"
        ],
        "src": [
          "openvswitch-3.2.1-5.oe2403sp2.src.rpm"
        ],
        "x86_64": [
          "network-scripts-openvswitch-3.2.1-5.oe2403sp2.x86_64.rpm",
          "openvswitch-3.2.1-5.oe2403sp2.x86_64.rpm",
          "openvswitch-debuginfo-3.2.1-5.oe2403sp2.x86_64.rpm",
          "openvswitch-debugsource-3.2.1-5.oe2403sp2.x86_64.rpm",
          "openvswitch-devel-3.2.1-5.oe2403sp2.x86_64.rpm",
          "openvswitch-dpdk-3.2.1-5.oe2403sp2.x86_64.rpm",
          "openvswitch-ipsec-3.2.1-5.oe2403sp2.x86_64.rpm",
          "openvswitch-testcontroller-3.2.1-5.oe2403sp2.x86_64.rpm",
          "python3-openvswitch-3.2.1-5.oe2403sp2.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:24.03-LTS-SP2",
        "name": "openvswitch",
        "purl": "pkg:rpm/openEuler/openvswitch\u0026distro=openEuler-24.03-LTS-SP2"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3.2.1-5.oe2403sp2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "severity": "Medium"
  },
  "details": "Open vSwitch provides standard network bridging functions and support for the OpenFlow protocol for remote per-flow control of traffic.\r\n\r\nSecurity Fix(es):\n\n[\u0026quot;Description\\n===========\\n\\nMultiple versions of Open vSwitch are vulnerable to crafted FTP payloads\\ncausing invalid memory accesses, potential denial of service, and possible\\nremote code execution.  This impacts the userspace implementation of\\nconntrack.  Triggering the vulnerability requires that Open vSwitch has\\nconfigured conntrack flows specifying the FTP alg handler.  Conntrack\\nhandlers in userspace are not automatically applied.\\n\\nThe issue is caused by type narrowing when copying FTP substrings.  It\\nhas existed in all versions of the userspace conntrack supporting the\\nFTP handler.  This was introduced with Open vSwitch version 2.8.0 and\\naffects all versions up to 3.7.0.\\n\\nThe Common Vulnerabilities and Exposures project (cve.mitre.org) has\\nassigned CVE-2026-34956 identifier to this issue.  At the time of writing\\nthe flaw is considered with Moderate impact and 5.9 CVSS.\\n\\n\\nMitigation\\n==========\\n\\nFor any affected version of Open vSwitch, avoiding the FTP alg will\\nprevent the issue from triggering.  The Open vSwitch team does not\\nrecommend attempting to mitigate the vulnerability this way because it\\nmay impact packet forwarding.\\n\\nBy default, alg handlers are not installed, and must be added as part\\nof the OpenFlow rules (via \u0026apos;ct(alg=ftp)\u0026apos; for example).\\n\\nUsers can check if they are using affected flows by looking at their\\nOpenFlow ruleset for their bridges, for example:\\n\\n   ovs-ofctl dump-flows \u0026lt;bridge\u0026gt; | grep \u0026apos;alg=ftp\u0026apos;\\n\\nWe have found that Open vSwitch may be subject to heap corruption when\\nprocessing FTP messages.\\n\\n\\nFix\\n===\\n\\nPatches to fix this vulnerability in Open vSwitch 3.3 and newer are\\napplied to the appropriate branches, and the original patch is located\\nat:\u0026quot;, \u0026apos;Recommendation\\n==============\\n\\nWe recommend that users of Open vSwitch apply the included patch, or\\nupgrade to a known patched version of Open vSwitch.  These include:\\n\\n* 3.3.9\\n* 3.4.6\\n* 3.5.4\\n* 3.6.3\\n* 3.7.1\\n\\n\\nAcknowledgements\\n================\\n\\nThe Open vSwitch team wishes to thank the reporter:\\n\\n  * Seiji Sakurai \u0026lt;Seiji.Sakurai () outlook com\u0026gt;\u0026apos;](CVE-2026-34956)",
  "id": "OESA-2026-1961",
  "modified": "2026-08-06T11:10:58Z",
  "published": "2026-04-17T11:10:58Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1961"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-34956"
    }
  ],
  "schema_version": "1.7.2",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "openvswitch security update",
  "upstream": [
    "CVE-2026-34956"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.