{
  "cveId": "CVE-2026-2436",
  "url": "https://patchblox.com/security/cve/CVE-2026-2436",
  "summary": "CVE-2026-2436 is fixed in 5 products on 1 platform, first by ALAS2023-2026-1778, released June 8, 2026. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "libsoup3: Package updates are available for Amazon Linux 2023 that fix the following vulnerabilities:\nCVE-2026-5119:\n\tA flaw wa...",
  "description": "Package updates are available for Amazon Linux 2023 that fix the following vulnerabilities:\nCVE-2026-5119:\n\tA flaw was found in libsoup. When establishing HTTPS tunnels through a configured HTTP proxy, sensitive session cookies are transmitted in cleartext within the initial HTTP CONNECT request. A network-positioned attacker or a malicious HTTP proxy can intercept these cookies, leading to potential session hijacking or user impersonation.\n\nCVE-2026-2708:\n\tlibsoup includes an embedded HTTP/1 server. When a server sits behind a proxy / load balancer, it\u0027s critical that every hop agrees on how request bodies are framed.\nIn the affected code path, libsoup accepted HTTP/1 requests with ambiguous body framing:\n\nmultiple Content-Length headers (CL.CL)\n\nTransfer-Encoding: chunked together with Content-Length (TE\u002BCL)\n\nDifferent intermediaries pick different framing rules in these cases. If a front-end and back-end disagree, an attacker can desynchronize the connection and \u0022smuggle\u0022 an extra request through the chain. Depending on deployment, this can lead to routing/ACL bypass, cache poisoning, or reaching internal-only endpoints.\n\nCVE-2026-2436:\n\tDenial of Service via use-after-free in SoupServer during TLS handshake\n\nCVE-2026-1801:\n\tA flaw was found in libsoup, an HTTP client/server library. This HTTP Request Smuggling vulnerability arises from non-RFC-compliant parsing in the soup_filter_input_stream_read_line() logic, where libsoup accepts malformed chunk headers, such as lone line feed (LF) characters instead of the required carriage return and line feed (CRLF). A remote attacker can exploit this without authentication or user interaction by sending specially crafted chunked requests. This allows libsoup to parse and process multiple HTTP requests from a single network message, potentially leading to information disclosure.\n\nCVE-2026-1761:\n\tA flaw was found in libsoup. This stack-based buffer overflow vulnerability occurs during the parsing of multipart HTTP responses due to an incorrect length calculation. A remote attacker can exploit this by sending a specially crafted multipart HTTP response, which can lead to memory corruption. This issue may result in application crashes or arbitrary code execution in applications that process untrusted server responses, and it does not require authentication or user interaction.\n\nCVE-2026-1760:\n\tA flaw was found in SoupServer. This HTTP request smuggling vulnerability occurs because SoupServer improperly handles requests that combine Transfer-Encoding: chunked and Connection: keep-alive headers. A remote, unauthenticated client can exploit this by sending specially crafted requests, causing SoupServer to fail to close the connection as required by RFC 9112. This allows the attacker to smuggle additional requests over the persistent connection, leading to unintended request processing and potential denial-of-service (DoS) conditions.\n\nCVE-2026-1467:\n\tA flaw was found in libsoup, an HTTP client library. This vulnerability, known as CRLF (Carriage Return Line Feed) Injection, occurs when an HTTP proxy is configured and the library improperly handles URL-decoded input used to create the Host header. A remote attacker can exploit this by providing a specially crafted URL containing CRLF sequences, allowing them to inject additional HTTP headers or complete HTTP request bodies. This can lead to unintended or unauthorized HTTP requests being forwarded by the proxy, potentially impacting downstream services.\n\nCVE-2026-0716:\n\tOOB Read via Integer Overflow on libsoup through libsoup/websocket/soup-websocket-connection.c via process_frame() leads to Undefined Behavior",
  "published": "2026-06-08T09:00:00Z",
  "severity": "moderate",
  "epss": 0.00455,
  "epssPercentile": 0.39817,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "libsoup3",
      "release": "amzn 2023",
      "fixedVersion": "3.6.6-58.amzn2023",
      "fix": "ALAS2023-2026-1778",
      "url": "https://patchblox.com/security/fix/linux/alas2023-2026-1778",
      "released": "2026-06-08T09:00:00Z"
    },
    {
      "platform": "linux",
      "product": "libsoup3-debuginfo",
      "release": "amzn 2023",
      "fixedVersion": "3.6.6-58.amzn2023",
      "fix": "ALAS2023-2026-1778",
      "url": "https://patchblox.com/security/fix/linux/alas2023-2026-1778",
      "released": "2026-06-08T09:00:00Z"
    },
    {
      "platform": "linux",
      "product": "libsoup3-debugsource",
      "release": "amzn 2023",
      "fixedVersion": "3.6.6-58.amzn2023",
      "fix": "ALAS2023-2026-1778",
      "url": "https://patchblox.com/security/fix/linux/alas2023-2026-1778",
      "released": "2026-06-08T09:00:00Z"
    },
    {
      "platform": "linux",
      "product": "libsoup3-devel",
      "release": "amzn 2023",
      "fixedVersion": "3.6.6-58.amzn2023",
      "fix": "ALAS2023-2026-1778",
      "url": "https://patchblox.com/security/fix/linux/alas2023-2026-1778",
      "released": "2026-06-08T09:00:00Z"
    },
    {
      "platform": "linux",
      "product": "libsoup3-doc",
      "release": "amzn 2023",
      "fixedVersion": "3.6.6-58.amzn2023",
      "fix": "ALAS2023-2026-1778",
      "url": "https://patchblox.com/security/fix/linux/alas2023-2026-1778",
      "released": "2026-06-08T09:00:00Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-10T20:03:11Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}