{
  "@id": "urn:uuid:0118d43d-7c10-42be-adae-df5cb7908a02",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 3,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-10T15:06:44.318506+00:00",
  "statements": [
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-codec-redis@4.1.59.Final-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-codec-redis@4.1.59.Final-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-09T20:51:20.044630+00:00",
      "status_notes": "Vulnerability CVE-2026-42586 affects version 4.1.59.Final-tuxcare.3 of io.netty:netty-codec-redis.",
      "vulnerability": {
        "name": "CVE-2026-42586"
      },
      "action_statement": "Vulnerability CVE-2026-42586 affects version 4.1.59.Final-tuxcare.3 of io.netty:netty-codec-redis."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-codec-redis@4.1.59.Final-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-codec-redis@4.1.59.Final-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-09T20:51:20.044630+00:00",
      "status_notes": "Vulnerability CVE-2026-44250 affects version 4.1.59.Final-tuxcare.3 of io.netty:netty-codec-redis.",
      "vulnerability": {
        "name": "CVE-2026-44250"
      },
      "action_statement": "Vulnerability CVE-2026-44250 affects version 4.1.59.Final-tuxcare.3 of io.netty:netty-codec-redis."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-codec-redis@4.1.59.Final-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-codec-redis@4.1.59.Final-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-09T20:51:20.044630+00:00",
      "status_notes": "Vulnerability CVE-2026-44890 affects version 4.1.59.Final-tuxcare.3 of io.netty:netty-codec-redis.",
      "vulnerability": {
        "name": "CVE-2026-44890"
      },
      "action_statement": "Vulnerability CVE-2026-44890 affects version 4.1.59.Final-tuxcare.3 of io.netty:netty-codec-redis."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-codec-redis@4.1.59.Final-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-codec-redis@4.1.59.Final-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-09T20:51:31.468347+00:00",
      "status_notes": "Vulnerability CVE-2026-48006 is fixed in version 4.1.59.Final-tuxcare.3 of io.netty:netty-codec-redis.",
      "vulnerability": {
        "name": "CVE-2026-48006"
      }
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-codec-redis@4.1.59.Final-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-codec-redis@4.1.59.Final-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-09T20:51:20.044630+00:00",
      "status_notes": "Vulnerability CVE-2026-50011 affects version 4.1.59.Final-tuxcare.3 of io.netty:netty-codec-redis.",
      "vulnerability": {
        "name": "CVE-2026-50011"
      },
      "action_statement": "Vulnerability CVE-2026-50011 affects version 4.1.59.Final-tuxcare.3 of io.netty:netty-codec-redis."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-codec-redis@4.1.59.Final-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-codec-redis@4.1.59.Final-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-09T20:51:20.044630+00:00",
      "status_notes": "Vulnerability CVE-2026-56818 does not affect version 4.1.59.Final-tuxcare.3 of io.netty:netty-codec-redis. not_affected \u2014 Version 4.1.59.Final is not affected by CVE-2026-56818. The vulnerable code path (maxElements limit check that throws without cleanup) does not exist in this version. The maxElements feature was introduced in commit e51c64c964 (June 2026) for Netty 4.1.135.Final and 4.2.x series, five years after 4.1.59.Final was released (February 2021). The target version only has a basic Integer.MAX_VALUE ch...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-56818"
      },
      "impact_statement": "not_affected \u2014 Version 4.1.59.Final is not affected by CVE-2026-56818. The vulnerable code path (maxElements limit check that throws without cleanup) does not exist in this version. The maxElements feature was introduced in commit e51c64c964 (June 2026) for Netty 4.1.135.Final and 4.2.x series, five years after 4.1.59.Final was released (February 2021). The target version only has a basic Integer.MAX_VALUE ch..."
    }
  ]
}