{
  "@id": "urn:uuid:68cfb6cb-5e6e-4889-b1c9-636d124a465c",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 21,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-02T14:58:56.128088+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-resolver-dns@4.1.135.Final-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-resolver-dns@4.1.135.Final-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-45673 does not affect version 4.1.135.Final-tuxcare.1 of io.netty:netty-resolver-dns. already_fixed \u2014 The target repository (Netty 4.1.135.Final at SHA 445f793ae3) already contains the vendor security patch for CVE-2026-45673. Commit 06eb73d74c3075b35a21d882475c06ac41e8e57f, applied on 2026-06-01, replaced predictable ThreadLocalRandom with cryptographically secure SecureRandom for DNS transaction ID generation in DnsQueryIdSpace.java. This fix is an ancestor of the current HEAD and has not bee...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-45673"
      },
      "impact_statement": "already_fixed \u2014 The target repository (Netty 4.1.135.Final at SHA 445f793ae3) already contains the vendor security patch for CVE-2026-45673. Commit 06eb73d74c3075b35a21d882475c06ac41e8e57f, applied on 2026-06-01, replaced predictable ThreadLocalRandom with cryptographically secure SecureRandom for DNS transaction ID generation in DnsQueryIdSpace.java. This fix is an ancestor of the current HEAD and has not bee..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-resolver-dns@4.1.135.Final-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-resolver-dns@4.1.135.Final-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-45674 does not affect version 4.1.135.Final-tuxcare.1 of io.netty:netty-resolver-dns. already_fixed \u2014 The target repository (Netty 4.1.135.Final) already contains both bailiwick validation fixes for CVE-2026-45674. The CNAME bailiwick check was added in commit 5749d7822f and the NS bailiwick check in commit 6f19adf368, both present in the current HEAD. These fixes prevent DNS cache poisoning by validating that DNS resource records (CNAME and NS) originate from authoritative sources within the q...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-45674"
      },
      "impact_statement": "already_fixed \u2014 The target repository (Netty 4.1.135.Final) already contains both bailiwick validation fixes for CVE-2026-45674. The CNAME bailiwick check was added in commit 5749d7822f and the NS bailiwick check in commit 6f19adf368, both present in the current HEAD. These fixes prevent DNS cache poisoning by validating that DNS resource records (CNAME and NS) originate from authoritative sources within the q..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-resolver-dns@4.1.135.Final-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-resolver-dns@4.1.135.Final-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-47691 does not affect version 4.1.135.Final-tuxcare.1 of io.netty:netty-resolver-dns. already_fixed \u2014 The target repository (Netty 4.1.135.Final) already contains both DNS Cache Poisoning fixes. Commits 6f19adf368 (NS record bailiwick validation) and 5749d7822f (CNAME bailiwick validation) were applied on June 2, 2026, as part of TuxCare ELS security backports. The bailiwick checks prevent subdomain authoritative servers from poisoning the cache for parent domains or unrelated zones.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-47691"
      },
      "impact_statement": "already_fixed \u2014 The target repository (Netty 4.1.135.Final) already contains both DNS Cache Poisoning fixes. Commits 6f19adf368 (NS record bailiwick validation) and 5749d7822f (CNAME bailiwick validation) were applied on June 2, 2026, as part of TuxCare ELS security backports. The bailiwick checks prevent subdomain authoritative servers from poisoning the cache for parent domains or unrelated zones."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-resolver-dns@4.1.135.Final-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-resolver-dns@4.1.135.Final-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability GHSA-mfg7-5gfp-c4w3 is fixed in version 4.1.135.Final-tuxcare.1 of io.netty:netty-resolver-dns.",
      "vulnerability": {
        "name": "GHSA-mfg7-5gfp-c4w3"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-resolver-dns@4.1.135.Final-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-resolver-dns@4.1.135.Final-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability GHSA-v74w-7mr3-4qg3 is fixed in version 4.1.135.Final-tuxcare.1 of io.netty:netty-resolver-dns.",
      "vulnerability": {
        "name": "GHSA-v74w-7mr3-4qg3"
      }
    }
  ]
}
