{
  "@id": "urn:uuid:5890f0ef-a664-42a6-b275-aa97439eba60",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 1,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-12T09:29:45.015792+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2006-6969 does not affect version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2006-6969 concerns predictable session ID generation using java.util.Random. The target repository (Jetty 9.4.51.v20230217) is not affected because it uses java.security.SecureRandom by default for session ID generation. This fix was introduced by upstream commit c3275730b91 (Greg Wilkins, April 2010, JETTY-1202) and shipped in the upstream release that TuxCare onboarded. The vulnerable pat...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2006-6969"
      },
      "impact_statement": "not_affected \u2014 CVE-2006-6969 concerns predictable session ID generation using java.util.Random. The target repository (Jetty 9.4.51.v20230217) is not affected because it uses java.security.SecureRandom by default for session ID generation. This fix was introduced by upstream commit c3275730b91 (Greg Wilkins, April 2010, JETTY-1202) and shipped in the upstream release that TuxCare onboarded. The vulnerable pat..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2011-4461 does not affect version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2011-4461 is not present in Jetty 9.4.51.v20230217. The vulnerability (hash collision DoS via unlimited form parameters) was fixed in upstream commit 085c79d7d6cfbccc02821ffdb64968593df3e0bf by Greg Wilkins in December 2011. This fix introduces maxFormKeys limiting (default 1000) with checkMaxKeys() enforcement that throws IllegalStateException when the parameter count exceeds the limit. Th...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2011-4461"
      },
      "impact_statement": "not_affected \u2014 CVE-2011-4461 is not present in Jetty 9.4.51.v20230217. The vulnerability (hash collision DoS via unlimited form parameters) was fixed in upstream commit 085c79d7d6cfbccc02821ffdb64968593df3e0bf by Greg Wilkins in December 2011. This fix introduces maxFormKeys limiting (default 1000) with checkMaxKeys() enforcement that throws IllegalStateException when the parameter count exceeds the limit. Th..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2015-2080 does not affect version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server. Prechecker: The upstream fix is already in this version's source history (commits 3e7b5f0f, 4df5647f). Version 9.4.51.v20230217 is on a newer release line than any version the advisories list as affected. Advisories: GitHub GHSA-ghgj-3xqr-6jfm (affected up to 9.2.9.v20150224), NVD (affected up to 9.3.0-m1).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2015-2080"
      },
      "impact_statement": "Prechecker: The upstream fix is already in this version's source history (commits 3e7b5f0f, 4df5647f). Version 9.4.51.v20230217 is on a newer release line than any version the advisories list as affected. Advisories: GitHub GHSA-ghgj-3xqr-6jfm (affected up to 9.2.9.v20150224), NVD (affected up to 9.3.0-m1)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2016-4800 does not affect version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2016-4800 affects Eclipse Jetty 9.3.0 through 9.3.8, where path normalization in PathResource on Windows allowed bypassing protected resources via backslash-related escaped characters. The target repository (version 9.4.51.v20230217) contains the upstream fix that was applied in May 2016 (commit 97af3d663fd). The fix adds URI comparison logic in checkAliasPath() to detect when Windows JVM n...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2016-4800"
      },
      "impact_statement": "not_affected \u2014 CVE-2016-4800 affects Eclipse Jetty 9.3.0 through 9.3.8, where path normalization in PathResource on Windows allowed bypassing protected resources via backslash-related escaped characters. The target repository (version 9.4.51.v20230217) contains the upstream fix that was applied in May 2016 (commit 97af3d663fd). The fix adds URI comparison logic in checkAliasPath() to detect when Windows JVM n..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2017-7656 does not affect version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server. The target version 9.4.51.v20230217 is not affected by CVE-2017-7656. The upstream Eclipse Jetty project introduced a compliance system in December 2017 (commit d8dead35) that addresses this vulnerability by rejecting HTTP/0.9 requests in the default RFC7230 compliance mode. This fix was already present in version 9.4.51.v20230217 when TuxCare onboarded it in September 2026. In the default configuration, HTTP/0.9 requests are rejected with HTTP 505 error via the NO_HTTP_0_9 compliance check at HttpParser.java lines 785-786, effectively blocking the HTTP Request Smuggling attack vector described in the CVE.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 9.3.24.v20180605; >= 9.4.0, < 9.4.11.v20180605), NVD (<= 9.2.26; >= 9.3.0, < 9.3.24; >= 9.4.0, < 9.4.11), Snyk (< 9.3.24.v20180605; >= 9.4.0.M0, < 9.4.11.v20180605; > 8.2.0.v20160908, < 9.3.24.v20180605; >= 9.4.0.M0, < 9.4.11.v20180605).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2017-7656"
      },
      "impact_statement": "The target version 9.4.51.v20230217 is not affected by CVE-2017-7656. The upstream Eclipse Jetty project introduced a compliance system in December 2017 (commit d8dead35) that addresses this vulnerability by rejecting HTTP/0.9 requests in the default RFC7230 compliance mode. This fix was already present in version 9.4.51.v20230217 when TuxCare onboarded it in September 2026. In the default configuration, HTTP/0.9 requests are rejected with HTTP 505 error via the NO_HTTP_0_9 compliance check at HttpParser.java lines 785-786, effectively blocking the HTTP Request Smuggling attack vector described in the CVE.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 9.3.24.v20180605; >= 9.4.0, < 9.4.11.v20180605), NVD (<= 9.2.26; >= 9.3.0, < 9.3.24; >= 9.4.0, < 9.4.11), Snyk (< 9.3.24.v20180605; >= 9.4.0.M0, < 9.4.11.v20180605; > 8.2.0.v20160908, < 9.3.24.v20180605; >= 9.4.0.M0, < 9.4.11.v20180605)."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2017-7657 affects version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2017-7657"
      },
      "action_statement": "Vulnerability CVE-2017-7657 affects version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2017-7658 does not affect version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server. CVE-2017-7658 (HTTP Request Smuggling via conflicting Content-Length headers) is NOT present in Jetty 9.4.51.v20230217. The upstream fix (commit a285deea42f by Greg Wilkins) was already included in the upstream release that TuxCare onboarded. The fix adds validation to reject requests with duplicate Content-Length headers or requests containing both Content-Length and Transfer-Encoding: chunked headers. The default HttpCompliance mode (RFC7230) enforces these security checks, preventing the request smuggling attack vector.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 9.2.25.v20180606; >= 9.3.0, < 9.3.24.v20180605; >= 9.4.0, < 9.4.11.v20180605), NVD (<= 9.2.26; >= 9.3.0, < 9.3.24; >= 9.4.0, < 9.4.11), Snyk (> 8.2.0.v20160908, < 9.2.25.v20180606; >= 9.3.0.M0, < 9.3.24.v20180605; >= 9.4.0.M0, < 9.4.11.v20180605).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2017-7658"
      },
      "impact_statement": "CVE-2017-7658 (HTTP Request Smuggling via conflicting Content-Length headers) is NOT present in Jetty 9.4.51.v20230217. The upstream fix (commit a285deea42f by Greg Wilkins) was already included in the upstream release that TuxCare onboarded. The fix adds validation to reject requests with duplicate Content-Length headers or requests containing both Content-Length and Transfer-Encoding: chunked headers. The default HttpCompliance mode (RFC7230) enforces these security checks, preventing the request smuggling attack vector.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 9.2.25.v20180606; >= 9.3.0, < 9.3.24.v20180605; >= 9.4.0, < 9.4.11.v20180605), NVD (<= 9.2.26; >= 9.3.0, < 9.3.24; >= 9.4.0, < 9.4.11), Snyk (> 8.2.0.v20160908, < 9.2.25.v20180606; >= 9.3.0.M0, < 9.3.24.v20180605; >= 9.4.0.M0, < 9.4.11.v20180605)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2017-9735 does not affect version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server. CVE-2017-9735 timing channel vulnerability is NOT present in target version 9.4.51.v20230217. The vulnerable variable-time password comparison was replaced with constant-time comparison in upstream Jetty commits from May 2017 through October 2018. The fix was already included in the upstream 9.4.51.v20230217 release that TuxCare onboarded in September 2026. The target code uses sophisticated constant-time comparison with modulo arithmetic and proper handling of edge cases, eliminating timing side-channels in password validation.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 9.4.0, < 9.4.6.v20170531; >= 9.3.0, < 9.3.20.v20170531; < 9.2.22.v20170606), NVD (< 9.2.22; >= 9.3.0, < 9.3.20; >= 9.4.0, < 9.4.6), Snyk (< 9.2.22.v20170606; >= 9.3.0.M0, < 9.3.20.v20170531; >= 9.4.0.M0, < 9.4.6.v20170531).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2017-9735"
      },
      "impact_statement": "CVE-2017-9735 timing channel vulnerability is NOT present in target version 9.4.51.v20230217. The vulnerable variable-time password comparison was replaced with constant-time comparison in upstream Jetty commits from May 2017 through October 2018. The fix was already included in the upstream 9.4.51.v20230217 release that TuxCare onboarded in September 2026. The target code uses sophisticated constant-time comparison with modulo arithmetic and proper handling of edge cases, eliminating timing side-channels in password validation.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 9.4.0, < 9.4.6.v20170531; >= 9.3.0, < 9.3.20.v20170531; < 9.2.22.v20170606), NVD (< 9.2.22; >= 9.3.0, < 9.3.20; >= 9.4.0, < 9.4.6), Snyk (< 9.2.22.v20170606; >= 9.3.0.M0, < 9.3.20.v20170531; >= 9.4.0.M0, < 9.4.6.v20170531)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2018-12536 does not affect version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2018-12536 is an information disclosure vulnerability where malformed HTTP request paths trigger InvalidPathException containing full server filesystem paths, which leak in error responses when handled by the default error handler. The upstream fix (commit ad4dceb1c08 authored by joakim.erdfelt@gmail.com on 2018-05-31) was already present in Jetty 9.4.51.v20230217 before TuxCare onboarded i...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-12536"
      },
      "impact_statement": "not_affected \u2014 CVE-2018-12536 is an information disclosure vulnerability where malformed HTTP request paths trigger InvalidPathException containing full server filesystem paths, which leak in error responses when handled by the default error handler. The upstream fix (commit ad4dceb1c08 authored by joakim.erdfelt@gmail.com on 2018-05-31) was already present in Jetty 9.4.51.v20230217 before TuxCare onboarded i..."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2018-12538 affects version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2018-12538"
      },
      "action_statement": "Vulnerability CVE-2018-12538 affects version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2018-12545 does not affect version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server. CVE-2018-12545 describes a DoS vulnerability in Jetty 9.3.x/9.4.x where the server is vulnerable to resource exhaustion from processing HTTP/2 SETTINGS frames containing many settings entries. The vendor fix (commit 9eca404da296f48, July 2018) adds validation to limit the number of settings keys per frame to 64 (DEFAULT_MAX_KEYS), rejecting oversized frames with ENHANCE_YOUR_CALM_ERROR before resource exhaustion.\n\nThe target repository (Jetty 9.4.51.v20230217) contains this exact fix in SettingsBodyParser.java. The defense is comprehensive: maxKeys field (line 38), keys counter (line 44), and validation in onSetting() (lines 198-205) that blocks unbounded settings processing.\n\nThis fix was authored by upstream developer Simone Bordet (simone.bordet@gmail.com) and was already present in version 9.4.51.v20230217 when TuxCare onboarded it (commit b53307d0427, 2026-09-12). The fix commit is an ancestor of the TuxCare onboarding commit, confirming it shipped in the upstream release.\n\nVerdict: not_affected - the vulnerable pattern (unbounded settings processing) is not present because the upstream fix is already in the code.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 9.4.0, < 9.4.12.v20180830; >= 9.3.0, < 9.3.25.v20180904), NVD (= 9.3.0-20150601; = 9.3.0-20150608; = 9.3.0-20150612; = 9.3.0-maintenance0; = 9.3.0-maintenance1; = 9.3.0-maintenance2; = 9.3.0-rc0; = 9.3.0-rc1; = 9.3.1-20150714; = 9.3.2-20150730; = 9.3.3-20150825; = 9.3.3-20150827; = 9.3.4-20151005; = 9.3.4-20151007; = 9.3.4-rc0; = 9.3.4-rc1; = 9.3.5-20151012; = 9.3.6-20151106; = 9.3.7-20160115; = 9.3.7-rc0; = 9.3.7-rc1; = 9.3.8-20160311; = 9.3.8-20160314; = 9.3.8-rc0; = 9.3.9-20160517; = 9.3.9-maintenance_0; = 9.3.9-maintenance_1; = 9.3.10-20160621; = 9.3.10-maintenance_0; = 9.3.11-20160721; = 9.3.11-maintenance_0; = 9.3.12-20160915; = 9.3.13-20161014; = 9.3.13-maintenance_0; = 9.3.14-20161028; = 9.3.15-20161220; = 9.3.16-20170119; = 9.3.16-20170120; = 9.3.17-20170317; = 9.3.17-rc0; = 9.3.18-20170406; = 9.3.19-20170502; = 9.3.20-20170531; = 9.3.21-20170918; = 9.3.21-maintenance_0; = 9.3.21-rc0; = 9.3.22-20171030; = 9.3.23-20180228; = 9.3.24-20180605; = 9.4.0-20161207; = 9.4.0-20161208; = 9.4.0-20180619; = 9.4.0-maintenance_0; = 9.4.0-maintenance_1; = 9.4.0-rc0; = 9.4.0-rc1; = 9.4.0-rc2; = 9.4.0-rc3; = 9.4.1-20170120; = 9.4.1-20180619; = 9.4.2-20170220; = 9.4.2-20180619; = 9.4.3-20170317; = 9.4.3-20180619; = 9.4.4-20170410; = 9.4.4-20170414; = 9.4.4-20180619; = 9.4.5-20170502; = 9.4.5-20180619; = 9.4.6-20170531; = 9.4.6-20180619; = 9.4.7-20170914; = 9.4.7-20180619; = 9.4.7-rc0; = 9.4.8-20171121; = 9.4.8-20180619; = 9.4.9-20180320; = 9.4.10-20180503; = 9.4.10-rc0; = 9.4.10-rc1; = 9.4.11-20180605; = 9.4.12-rc0; = 9.4.12-rc1; = 9.4.12-rc2), Snyk (<= 0; >= 9.3.0.M0, < 9.4.12.v20180830).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-12545"
      },
      "impact_statement": "CVE-2018-12545 describes a DoS vulnerability in Jetty 9.3.x/9.4.x where the server is vulnerable to resource exhaustion from processing HTTP/2 SETTINGS frames containing many settings entries. The vendor fix (commit 9eca404da296f48, July 2018) adds validation to limit the number of settings keys per frame to 64 (DEFAULT_MAX_KEYS), rejecting oversized frames with ENHANCE_YOUR_CALM_ERROR before resource exhaustion.\n\nThe target repository (Jetty 9.4.51.v20230217) contains this exact fix in SettingsBodyParser.java. The defense is comprehensive: maxKeys field (line 38), keys counter (line 44), and validation in onSetting() (lines 198-205) that blocks unbounded settings processing.\n\nThis fix was authored by upstream developer Simone Bordet (simone.bordet@gmail.com) and was already present in version 9.4.51.v20230217 when TuxCare onboarded it (commit b53307d0427, 2026-09-12). The fix commit is an ancestor of the TuxCare onboarding commit, confirming it shipped in the upstream release.\n\nVerdict: not_affected - the vulnerable pattern (unbounded settings processing) is not present because the upstream fix is already in the code.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 9.4.0, < 9.4.12.v20180830; >= 9.3.0, < 9.3.25.v20180904), NVD (= 9.3.0-20150601; = 9.3.0-20150608; = 9.3.0-20150612; = 9.3.0-maintenance0; = 9.3.0-maintenance1; = 9.3.0-maintenance2; = 9.3.0-rc0; = 9.3.0-rc1; = 9.3.1-20150714; = 9.3.2-20150730; = 9.3.3-20150825; = 9.3.3-20150827; = 9.3.4-20151005; = 9.3.4-20151007; = 9.3.4-rc0; = 9.3.4-rc1; = 9.3.5-20151012; = 9.3.6-20151106; = 9.3.7-20160115; = 9.3.7-rc0; = 9.3.7-rc1; = 9.3.8-20160311; = 9.3.8-20160314; = 9.3.8-rc0; = 9.3.9-20160517; = 9.3.9-maintenance_0; = 9.3.9-maintenance_1; = 9.3.10-20160621; = 9.3.10-maintenance_0; = 9.3.11-20160721; = 9.3.11-maintenance_0; = 9.3.12-20160915; = 9.3.13-20161014; = 9.3.13-maintenance_0; = 9.3.14-20161028; = 9.3.15-20161220; = 9.3.16-20170119; = 9.3.16-20170120; = 9.3.17-20170317; = 9.3.17-rc0; = 9.3.18-20170406; = 9.3.19-20170502; = 9.3.20-20170531; = 9.3.21-20170918; = 9.3.21-maintenance_0; = 9.3.21-rc0; = 9.3.22-20171030; = 9.3.23-20180228; = 9.3.24-20180605; = 9.4.0-20161207; = 9.4.0-20161208; = 9.4.0-20180619; = 9.4.0-maintenance_0; = 9.4.0-maintenance_1; = 9.4.0-rc0; = 9.4.0-rc1; = 9.4.0-rc2; = 9.4.0-rc3; = 9.4.1-20170120; = 9.4.1-20180619; = 9.4.2-20170220; = 9.4.2-20180619; = 9.4.3-20170317; = 9.4.3-20180619; = 9.4.4-20170410; = 9.4.4-20170414; = 9.4.4-20180619; = 9.4.5-20170502; = 9.4.5-20180619; = 9.4.6-20170531; = 9.4.6-20180619; = 9.4.7-20170914; = 9.4.7-20180619; = 9.4.7-rc0; = 9.4.8-20171121; = 9.4.8-20180619; = 9.4.9-20180320; = 9.4.10-20180503; = 9.4.10-rc0; = 9.4.10-rc1; = 9.4.11-20180605; = 9.4.12-rc0; = 9.4.12-rc1; = 9.4.12-rc2), Snyk (<= 0; >= 9.3.0.M0, < 9.4.12.v20180830)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2019-10241 does not affect version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2019-10241 (XSS in directory listings) is not present in target version 9.4.51.v20230217. The upstream fix (commit 1565b5f160e) was already shipped in this release before TuxCare onboarding. The fix includes: (1) getFileName() method with proper URL decoding via UrlEncoded.decodeString(), (2) hrefEncodeURI() encoding dangerous characters in href attributes, (3) deTag() sanitizing displayed ...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-10241"
      },
      "impact_statement": "not_affected \u2014 CVE-2019-10241 (XSS in directory listings) is not present in target version 9.4.51.v20230217. The upstream fix (commit 1565b5f160e) was already shipped in this release before TuxCare onboarding. The fix includes: (1) getFileName() method with proper URL decoding via UrlEncoded.decodeString(), (2) hrefEncodeURI() encoding dangerous characters in href attributes, (3) deTag() sanitizing displayed ..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2019-10246 does not affect version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server. not_affected \u2014 The target repository (Eclipse Jetty 9.4.51.v20230217) is NOT affected by CVE-2019-10246. The vulnerability, which exposed fully qualified filesystem paths in directory listings on Windows, was fixed in upstream commit 7b774d82e82 by Joakim Erdfelt on 2019-04-15. This fix was already present in the upstream release jetty-9.4.51.v20230217 that TuxCare onboarded. The fix replaces direct use of ge...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-10246"
      },
      "impact_statement": "not_affected \u2014 The target repository (Eclipse Jetty 9.4.51.v20230217) is NOT affected by CVE-2019-10246. The vulnerability, which exposed fully qualified filesystem paths in directory listings on Windows, was fixed in upstream commit 7b774d82e82 by Joakim Erdfelt on 2019-04-15. This fix was already present in the upstream release jetty-9.4.51.v20230217 that TuxCare onboarded. The fix replaces direct use of ge..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2019-10247 does not affect version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2019-10247 does not affect this target. The vulnerability requires DefaultHandler to call context.toString() in 404 error responses, which reveals the configured filesystem directory base resource location. The target version 9.4.51.v20230217 contains upstream fixes (commits 04c994712c0 and 9f506e4123b by Joakim Erdfelt) that removed all context.toString() calls from the error output before...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-10247"
      },
      "impact_statement": "not_affected \u2014 CVE-2019-10247 does not affect this target. The vulnerability requires DefaultHandler to call context.toString() in 404 error responses, which reveals the configured filesystem directory base resource location. The target version 9.4.51.v20230217 contains upstream fixes (commits 04c994712c0 and 9f506e4123b by Joakim Erdfelt) that removed all context.toString() calls from the error output before..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2019-17632 does not affect version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2019-17632 does not affect this version. The vulnerability (unescaped exception messages in HTML/JSON error responses) was fixed by upstream Jetty in version 9.4.24.v20191120 (commit cf0df6e3ffd, November 2019). The target version 9.4.51.v20230217 already contained this fix when TuxCare onboarded it in 2023. The vulnerable code pattern is not present - all exception output is sanitized via ...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-17632"
      },
      "impact_statement": "not_affected \u2014 CVE-2019-17632 does not affect this version. The vulnerability (unescaped exception messages in HTML/JSON error responses) was fixed by upstream Jetty in version 9.4.24.v20191120 (commit cf0df6e3ffd, November 2019). The target version 9.4.51.v20230217 already contained this fix when TuxCare onboarded it in 2023. The vulnerable code pattern is not present - all exception output is sanitized via ..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2019-17638 does not affect version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server. Target version 9.4.51.v20230217 is NOT AFFECTED by CVE-2019-17638. The vulnerable double-release pattern described in the CVE (ByteBuffer released twice when oversized response headers trigger HTTP 431 error) is absent from the target code. The fix for this vulnerability was already present in the upstream Eclipse Jetty 9.4.51 release that TuxCare onboarded. The fix was authored by Greg Wilkins (gregw@webtide.com) in commit ff8ae56fa93, which is an ancestor of the TuxCare onboarding commit. The vulnerable code pattern no longer exists: the HEADER_OVERFLOW case now checks buffer capacity BEFORE releasing (not after), and all buffer release operations null their references to prevent double-release.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 9.4.27, < 9.4.30.v20200611), NVD (= 9.4.27-20200227; = 9.4.28-20200408; = 9.4.29-20200521), Snyk (>= 9.4.27.v20200227, < 9.4.30.v20200611).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-17638"
      },
      "impact_statement": "Target version 9.4.51.v20230217 is NOT AFFECTED by CVE-2019-17638. The vulnerable double-release pattern described in the CVE (ByteBuffer released twice when oversized response headers trigger HTTP 431 error) is absent from the target code. The fix for this vulnerability was already present in the upstream Eclipse Jetty 9.4.51 release that TuxCare onboarded. The fix was authored by Greg Wilkins (gregw@webtide.com) in commit ff8ae56fa93, which is an ancestor of the TuxCare onboarding commit. The vulnerable code pattern no longer exists: the HEADER_OVERFLOW case now checks buffer capacity BEFORE releasing (not after), and all buffer release operations null their references to prevent double-release.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 9.4.27, < 9.4.30.v20200611), NVD (= 9.4.27-20200227; = 9.4.28-20200408; = 9.4.29-20200521), Snyk (>= 9.4.27.v20200227, < 9.4.30.v20200611)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2020-27218 does not affect version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server. not_affected \u2014 Target Jetty 9.4.51.v20230217 is NOT AFFECTED by CVE-2020-27218. The fix for the GZIP unconsumed input vulnerability (issue #5605) was already present in the upstream Jetty 9.4.51.v20230217 release that TuxCare onboarded. Fix commit 14f94f738df by gregw@webtide.com is an ancestor of the first TuxCare commit b53307d0427 (onboarding commit), confirming the fix shipped in the upstream release. All...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2020-27218"
      },
      "impact_statement": "not_affected \u2014 Target Jetty 9.4.51.v20230217 is NOT AFFECTED by CVE-2020-27218. The fix for the GZIP unconsumed input vulnerability (issue #5605) was already present in the upstream Jetty 9.4.51.v20230217 release that TuxCare onboarded. Fix commit 14f94f738df by gregw@webtide.com is an ancestor of the first TuxCare commit b53307d0427 (onboarding commit), confirming the fix shipped in the upstream release. All..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2020-27223 does not affect version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2020-27223 is NOT present in Jetty 9.4.51.v20230217. The vulnerability involved an O(n\u00b2) bubble-sort algorithm in QuotedQualityCSV.java that caused excessive CPU consumption when processing HTTP headers with many quality parameters. The fix (commit 10e531756b9) replaced this with an efficient O(n log n) comparator-based sort and was introduced in Jetty 9.4.38.v20210224 (February 2021). The ...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2020-27223"
      },
      "impact_statement": "not_affected \u2014 CVE-2020-27223 is NOT present in Jetty 9.4.51.v20230217. The vulnerability involved an O(n\u00b2) bubble-sort algorithm in QuotedQualityCSV.java that caused excessive CPU consumption when processing HTTP headers with many quality parameters. The fix (commit 10e531756b9) replaced this with an efficient O(n log n) comparator-based sort and was introduced in Jetty 9.4.38.v20210224 (February 2021). The ..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2021-28165 does not affect version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server. CVE-2021-28165 is NOT affecting this version. The vulnerability (high CPU usage when processing invalid large TLS frames >17408 bytes) was fixed by upstream Jetty maintainer Simone Bordet in commit 294b2ba02b667548617a94cd99592110ac230add (March 22, 2021), which shipped in the upstream 9.4.51.v20230217 release. The fix adds a buffer space check that throws SSLHandshakeException when the encrypted input buffer is full, preventing the CPU exhaustion attack. This fix was already present when TuxCare onboarded version 9.4.51.v20230217.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 7.2.2, < 9.4.39; >= 10.0.0, < 10.0.2; >= 11.0.0, < 11.0.2), NVD (>= 7.2.2, < 9.4.39; >= 10.0.0, < 10.0.2; >= 11.0.0, < 11.0.2), Snyk (>= 7.2.2.v20101205, < 9.4.39.v20210325; >= 10.0.0.alpha0, < 10.0.2; >= 11.0.0.alpha0, < 11.0.2).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2021-28165"
      },
      "impact_statement": "CVE-2021-28165 is NOT affecting this version. The vulnerability (high CPU usage when processing invalid large TLS frames >17408 bytes) was fixed by upstream Jetty maintainer Simone Bordet in commit 294b2ba02b667548617a94cd99592110ac230add (March 22, 2021), which shipped in the upstream 9.4.51.v20230217 release. The fix adds a buffer space check that throws SSLHandshakeException when the encrypted input buffer is full, preventing the CPU exhaustion attack. This fix was already present when TuxCare onboarded version 9.4.51.v20230217.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 7.2.2, < 9.4.39; >= 10.0.0, < 10.0.2; >= 11.0.0, < 11.0.2), NVD (>= 7.2.2, < 9.4.39; >= 10.0.0, < 10.0.2; >= 11.0.0, < 11.0.2), Snyk (>= 7.2.2.v20101205, < 9.4.39.v20210325; >= 10.0.0.alpha0, < 10.0.2; >= 11.0.0.alpha0, < 11.0.2)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2021-34428 does not affect version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2021-34428 is a Jetty session-invalidation flaw: if an application's SessionListener#sessionDestroyed() throws, the pre-fix Session.invalidate() skipped SessionIdManager.invalidateAll(), leaving the session ID registered in the ID manager. On clustered / multi-context deployments the session stays valid and a user can remain logged in on a shared computer. The upstream fix (commit 087f486b4461, \"Issue #6277 Better handling of exceptions thrown in sessionDestroyed\", tagged jetty-9.4.41.v20210516) wraps the destroy-listener call in try/catch(Exception) and moves getSessionIdManager().invalidateAll(id) into the finally block so ID removal always runs. Target is jetty-9.4.51.v20230217 (newer than the 9.4.41 fix). Session.java lines 942-958 contain the exact post-fix try/catch/finally; git blame attributes the catch (947-949) and the invalidateAll-in-finally (956-957) to the patch commit itself, authored by Jan Bartel <janb@webtide.com> (upstream Webtide). The fix is stock upstream baked into the onboarded release (ancestor of both parents of the TuxCare onboarding merge; not introduced by it), not a TuxCare backport. Verdict: not_affected \u2014 upstream fix already present in the shipped version; vulnerable pattern absent from HEAD. Justification: code_not_present. [VC re-run with claude-opus-4-8, prod pin d46bd7a, 2026-09-23; the earlier Sonnet run was parked by the author-verification gate after crediting a TuxCare backport for an upstream fix]",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2021-34428"
      },
      "impact_statement": "not_affected \u2014 CVE-2021-34428 is a Jetty session-invalidation flaw: if an application's SessionListener#sessionDestroyed() throws, the pre-fix Session.invalidate() skipped SessionIdManager.invalidateAll(), leaving the session ID registered in the ID manager. On clustered / multi-context deployments the session stays valid and a user can remain logged in on a shared computer. The upstream fix (commit 087f486b4461, \"Issue #6277 Better handling of exceptions thrown in sessionDestroyed\", tagged jetty-9.4.41.v20210516) wraps the destroy-listener call in try/catch(Exception) and moves getSessionIdManager().invalidateAll(id) into the finally block so ID removal always runs. Target is jetty-9.4.51.v20230217 (newer than the 9.4.41 fix). Session.java lines 942-958 contain the exact post-fix try/catch/finally; git blame attributes the catch (947-949) and the invalidateAll-in-finally (956-957) to the patch commit itself, authored by Jan Bartel <janb@webtide.com> (upstream Webtide). The fix is stock upstream baked into the onboarded release (ancestor of both parents of the TuxCare onboarding merge; not introduced by it), not a TuxCare backport. Verdict: not_affected \u2014 upstream fix already present in the shipped version; vulnerable pattern absent from HEAD. Justification: code_not_present. [VC re-run with claude-opus-4-8, prod pin d46bd7a, 2026-09-23; the earlier Sonnet run was parked by the author-verification gate after crediting a TuxCare backport for an upstream fix]"
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2022-2191 does not affect version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server. Re-checked 2026-11-10 by the vulnerability checker and confirmed by an independent code review: not affected. This version is not affected because its default buffer pool does not retain acquired buffers, so missed returns do not cause the persistent pool-entry leak. Acquisition removes buffers with queue.poll() at jetty-io/src/main/java/org/eclipse/jetty/io/ByteBufferPool.java:181, and the contract explicitly permits garbage collection of unreturned buffers at jetty-io/src/main/java/org/eclipse/jetty/io/ByteBufferPool.java:35.",
      "justification": "vulnerable_code_not_in_execute_path",
      "vulnerability": {
        "name": "CVE-2022-2191"
      },
      "impact_statement": "Re-checked 2026-11-10 by the vulnerability checker and confirmed by an independent code review: not affected. This version is not affected because its default buffer pool does not retain acquired buffers, so missed returns do not cause the persistent pool-entry leak. Acquisition removes buffers with queue.poll() at jetty-io/src/main/java/org/eclipse/jetty/io/ByteBufferPool.java:181, and the contract explicitly permits garbage collection of unreturned buffers at jetty-io/src/main/java/org/eclipse/jetty/io/ByteBufferPool.java:35."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2023-26048 does not affect version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server. not_affected \u2014 The target repository (Jetty 9.4.51.v20230217-tuxcare.1) is not affected by CVE-2023-26048. The vulnerability pattern has been removed by an upstream fix (PR #9345, commit c3021592218) that was already present in the upstream Jetty 9.4.51.v20230217 release before TuxCare onboarded it. Both defense mechanisms are present and active by default: (1) part count limiting with DEFAULT_MAX_FORM_KEYS=1...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-26048"
      },
      "impact_statement": "not_affected \u2014 The target repository (Jetty 9.4.51.v20230217-tuxcare.1) is not affected by CVE-2023-26048. The vulnerability pattern has been removed by an upstream fix (PR #9345, commit c3021592218) that was already present in the upstream Jetty 9.4.51.v20230217 release before TuxCare onboarded it. Both defense mechanisms are present and active by default: (1) part count limiting with DEFAULT_MAX_FORM_KEYS=1..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2023-26049 does not affect version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2023-26049 (cookie smuggling via semicolons in quoted values) does not affect this target. The upstream vendor fix (commit 1be1401bafb, PR #9352) was already present in the Eclipse Jetty 9.4.51.v20230217 release that TuxCare onboarded. The fix adds a 'reject' flag that is set when a semicolon is found inside a quoted cookie value (in RFC6265 compliance mode, which is the default), preventin...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-26049"
      },
      "impact_statement": "not_affected \u2014 CVE-2023-26049 (cookie smuggling via semicolons in quoted values) does not affect this target. The upstream vendor fix (commit 1be1401bafb, PR #9352) was already present in the Eclipse Jetty 9.4.51.v20230217 release that TuxCare onboarded. The fix adds a 'reject' flag that is set when a semicolon is found inside a quoted cookie value (in RFC6265 compliance mode, which is the default), preventin..."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2024-13009 affects version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2024-13009"
      },
      "action_statement": "Vulnerability CVE-2024-13009 affects version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2024-7708 does not affect version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server. Re-checked 2026-11-10 by the vulnerability checker and confirmed by an independent code review: not affected. This version is not affected because empty request buffers are returned to the pool after zero-byte reads, preventing the buffer leak. Both read paths parse immediately after filling (jetty-server/src/main/java/org/eclipse/jetty/server/HttpConnection.java:260 and :327); parsing releases buffers with no content references (:387), and release clears the connection\u2019s buffer field and returns the empty buffer to the pool (:224).",
      "vulnerability": {
        "name": "CVE-2024-7708"
      },
      "impact_statement": "Re-checked 2026-11-10 by the vulnerability checker and confirmed by an independent code review: not affected. This version is not affected because empty request buffers are returned to the pool after zero-byte reads, preventing the buffer leak. Both read paths parse immediately after filling (jetty-server/src/main/java/org/eclipse/jetty/server/HttpConnection.java:260 and :327); parsing releases buffers with no content references (:387), and release clears the connection\u2019s buffer field and returns the empty buffer to the pool (:224)."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2024-8184 affects version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2024-8184"
      },
      "action_statement": "Vulnerability CVE-2024-8184 affects version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2026-10051 does not affect version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server. not_affected \u2014 Jetty 9.4.51.v20230217 is not affected by CVE-2026-10051 because the vulnerable pattern (trailers not being cleared between requests) does not exist in this version. The CVE describes a vulnerability in Jetty 12.x's HttpConnection where the _trailers field was never cleared between HTTP/1.1 keep-alive requests. However, Jetty 9.4.x uses a different architecture (HttpChannelOverHttp) that proper...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-10051"
      },
      "impact_statement": "not_affected \u2014 Jetty 9.4.51.v20230217 is not affected by CVE-2026-10051 because the vulnerable pattern (trailers not being cleared between requests) does not exist in this version. The CVE describes a vulnerability in Jetty 12.x's HttpConnection where the _trailers field was never cleared between HTTP/1.1 keep-alive requests. However, Jetty 9.4.x uses a different architecture (HttpChannelOverHttp) that proper..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2026-1605 does not affect version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server. Jetty 9.4.51.v20230217 uses a fundamentally different architecture than the vulnerable Jetty 12.x described in CVE-2026-1605. The CVE-specific vulnerability pattern requires GzipRequest with InflaterPool where cleanup is conditional on response deflation. Jetty 9.4.51 lacks these components entirely (GzipRequest, GzipResponseAndCallback, pooled Inflaters) and instead uses GzipHttpInputInterceptor with direct Inflater creation and deferred cleanup via HttpInput.recycle(). The specific chain from Input to Goal (pool exhaustion leading to permanent memory leak) is not reachable in this version's architecture.",
      "justification": "vulnerable_code_not_in_execute_path",
      "vulnerability": {
        "name": "CVE-2026-1605"
      },
      "impact_statement": "Jetty 9.4.51.v20230217 uses a fundamentally different architecture than the vulnerable Jetty 12.x described in CVE-2026-1605. The CVE-specific vulnerability pattern requires GzipRequest with InflaterPool where cleanup is conditional on response deflation. Jetty 9.4.51 lacks these components entirely (GzipRequest, GzipResponseAndCallback, pooled Inflaters) and instead uses GzipHttpInputInterceptor with direct Inflater creation and deferred cleanup via HttpInput.recycle(). The specific chain from Input to Goal (pool exhaustion leading to permanent memory leak) is not reachable in this version's architecture."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.51.v20230217-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:29:45.015792+00:00",
      "status_notes": "Vulnerability CVE-2026-6790 is fixed in version 9.4.51.v20230217-tuxcare.3 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2026-6790"
      }
    }
  ]
}
