{
  "@id": "urn:uuid:39708a7e-1e8f-4154-a48a-78b798edf461",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 10,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-04T09:04:11.456857+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/io.projectreactor.netty/reactor-netty@1.2.18-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/io.projectreactor.netty/reactor-netty@1.2.18-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-04T09:04:11.456857+00:00",
      "status_notes": "Vulnerability CVE-2019-11284 does not affect version 1.2.18-tuxcare.2 of io.projectreactor.netty:reactor-netty. CVE-2019-11284 is NOT present in reactor-netty version 1.2.18. The vulnerability (passing authentication headers through HTTP redirects to different servers) was fixed by upstream vendor Pivotal in version 0.8.11.RELEASE (commit 656f9323, September 2019). The fix introduces fromURI/toURI tracking and removes sensitive headers (COOKIE, AUTHORIZATION, PROXY_AUTHORIZATION, EXPECT) when redirecting to a different server. This fix was already present in the upstream release that TuxCare onboarded for version 1.2.18, so the target never had this vulnerability.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 0.8.11), NVD (>= 0.8.0, < 0.8.11), cve.org (< 0.8.11.RELEASE), Snyk (>= 0.8.0, < 0.8.11.RELEASE).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-11284"
      },
      "impact_statement": "CVE-2019-11284 is NOT present in reactor-netty version 1.2.18. The vulnerability (passing authentication headers through HTTP redirects to different servers) was fixed by upstream vendor Pivotal in version 0.8.11.RELEASE (commit 656f9323, September 2019). The fix introduces fromURI/toURI tracking and removes sensitive headers (COOKIE, AUTHORIZATION, PROXY_AUTHORIZATION, EXPECT) when redirecting to a different server. This fix was already present in the upstream release that TuxCare onboarded for version 1.2.18, so the target never had this vulnerability.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 0.8.11), NVD (>= 0.8.0, < 0.8.11), cve.org (< 0.8.11.RELEASE), Snyk (>= 0.8.0, < 0.8.11.RELEASE)."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/io.projectreactor.netty/reactor-netty@1.2.18-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/io.projectreactor.netty/reactor-netty@1.2.18-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-14T14:55:00.657167+00:00",
      "status_notes": "Vulnerability CVE-2026-41715 affects version 1.2.18-tuxcare.2 of io.projectreactor.netty:reactor-netty.",
      "vulnerability": {
        "name": "CVE-2026-41715"
      },
      "action_statement": "Vulnerability CVE-2026-41715 affects version 1.2.18-tuxcare.2 of io.projectreactor.netty:reactor-netty."
    }
  ]
}
