{
  "affected": [
    {
      "ranges": [
        {
          "database_specific": {
            "cpe": "cpe:2.3:a:netty:netty:*:*:*:*:*:*:*:*",
            "extracted_events": [
              {
                "introduced": "0"
              },
              {
                "fixed": "4.1.135"
              },
              {
                "introduced": "4.2.0"
              },
              {
                "fixed": "4.2.15"
              }
            ],
            "source": [
              "CPE_RANGE",
              "REFERENCES"
            ]
          },
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "f05f765d81460799c53123a207f665bf3b465171"
            },
            {
              "introduced": "09e64d259c99be8b5b2a471a78f11e65eb82598a"
            },
            {
              "fixed": "a41f7b289ce1d697c50846f3ade3983e22b2ed40"
            }
          ],
          "repo": "https://github.com/netty/netty",
          "type": "GIT"
        }
      ]
    }
  ],
  "aliases": [
    "GHSA-563q-j3cm-6jxm"
  ],
  "database_specific": {
    "cna_assigner": "GitHub_M",
    "cwe_ids": [
      "CWE-770"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/50xxx/CVE-2026-50560.json"
  },
  "details": "Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, Netty HTTP/2 max header size handling produces an attack similar to HTTP/2 Rapid Reset. There is a setting in the http2 specification called `SETTINGS_MAX_HEADER_LIST_SIZE`. When a client sends that setting to Netty, it appears that Netty will behave as follows: read the request; proxy the request to the origin; attempt to produce a response; and create an exception while writing the headers for the response. Functionally, this should be similar to the http2 reset attack, but with a different on-the-wire signature. Versions 4.1.135.Final and 4.2.15.Final patch the issue.",
  "id": "CVE-2026-50560",
  "modified": "2026-07-08T05:37:15.327955970Z",
  "published": "2026-06-12T14:59:59.901Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/netty/netty/releases/tag/netty-4.1.135.Final"
    },
    {
      "type": "WEB",
      "url": "https://github.com/netty/netty/releases/tag/netty-4.2.15.Final"
    },
    {
      "type": "WEB",
      "url": "https://www.rfc-editor.org/rfc/rfc9113.html#name-defined-settings"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/50xxx/CVE-2026-50560.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/netty/netty/security/advisories/GHSA-563q-j3cm-6jxm"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-50560"
    }
  ],
  "schema_version": "1.7.5",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Netty susceptible to HTTP/2 Reset Attack with different on-the-wire signature"
}