{
  "@id": "urn:uuid:2aa36722-b08f-4e73-bd82-690baffd8639",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 7,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-10T04:14:20.974341+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T13:45:52.646915+00:00",
      "status_notes": "Vulnerability CVE-2006-6969 does not affect version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2006-6969 describes predictable session ID generation using java.util.Random in old Jetty versions (before 4.2.27, 5.1.12, 6.0.2, 6.1.0pre3). The target version 9.4.57.v20241219 uses SecureRandom by default for session ID generation in DefaultSessionIdManager.initRandom() (line 374). The fix was introduced by upstream Jetty developer Greg Wilkins in commit da627b843fe8 from 2009-03-24, whic...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2006-6969"
      },
      "impact_statement": "not_affected \u2014 CVE-2006-6969 describes predictable session ID generation using java.util.Random in old Jetty versions (before 4.2.27, 5.1.12, 6.0.2, 6.1.0pre3). The target version 9.4.57.v20241219 uses SecureRandom by default for session ID generation in DefaultSessionIdManager.initRandom() (line 374). The fix was introduced by upstream Jetty developer Greg Wilkins in commit da627b843fe8 from 2009-03-24, whic..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T13:45:52.646915+00:00",
      "status_notes": "Vulnerability CVE-2011-4461 does not affect version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2011-4461 is NOT present in Jetty 9.4.57.v20241219. The vulnerability (hash collision DoS via unbounded form parameter parsing) was fixed by upstream in commit 085c79d7d6c (December 2011) which added a maxFormKeys limit (default 1000) to all form parameter decoding paths. This fix was already included in the upstream 9.4.57.v20241219 release before TuxCare onboarded it. The target implement...",
      "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.57.v20241219. The vulnerability (hash collision DoS via unbounded form parameter parsing) was fixed by upstream in commit 085c79d7d6c (December 2011) which added a maxFormKeys limit (default 1000) to all form parameter decoding paths. This fix was already included in the upstream 9.4.57.v20241219 release before TuxCare onboarded it. The target implement..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-06T17:45:18.861504+00:00",
      "status_notes": "Vulnerability CVE-2015-2080 does not affect version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server. Prechecker: The upstream fix is already in this version's source history (commits 3e7b5f0f, 4df5647f). Version 9.4.57.v20241219 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.57.v20241219 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.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T13:45:52.646915+00:00",
      "status_notes": "Vulnerability CVE-2016-4800 does not affect version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2016-4800 affects Eclipse Jetty 9.3.0 through 9.3.8, allowing attackers to bypass protected resource restrictions on Windows by using URLs with escaped backslash characters. The target version 9.4.57.v20241219 is not affected because it already contains the upstream fix from commit 97af3d663fd (May 13, 2016, included in Jetty 9.3.9). This fix was part of the upstream release before TuxCare ...",
      "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, allowing attackers to bypass protected resource restrictions on Windows by using URLs with escaped backslash characters. The target version 9.4.57.v20241219 is not affected because it already contains the upstream fix from commit 97af3d663fd (May 13, 2016, included in Jetty 9.3.9). This fix was part of the upstream release before TuxCare ..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T13:45:52.646915+00:00",
      "status_notes": "Vulnerability CVE-2017-7656 does not affect version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server. CVE-2017-7656 (HTTP Request Smuggling) does not affect Jetty 9.4.57.v20241219. The upstream fix (commit a285deea42f by Greg Wilkins, May 2018) shipped in the release that TuxCare onboarded. All four defense mechanisms are present and active in the default RFC7230 compliance mode: (1) multiple Content-Length rejection via _hasContentLength flag, (2) Content-Length + Transfer-Encoding: chunked conflict detection via _hasTransferEncoding flag, (3) chunk length overflow protection via MAX_CHUNK_LENGTH, (4) HTTP version validation. The CVE states vulnerability exists \"in 9.4.x with non-default RFC2616 compliance enabled\" - the target uses default RFC7230 mode which enforces the protections.\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": "CVE-2017-7656 (HTTP Request Smuggling) does not affect Jetty 9.4.57.v20241219. The upstream fix (commit a285deea42f by Greg Wilkins, May 2018) shipped in the release that TuxCare onboarded. All four defense mechanisms are present and active in the default RFC7230 compliance mode: (1) multiple Content-Length rejection via _hasContentLength flag, (2) Content-Length + Transfer-Encoding: chunked conflict detection via _hasTransferEncoding flag, (3) chunk length overflow protection via MAX_CHUNK_LENGTH, (4) HTTP version validation. The CVE states vulnerability exists \"in 9.4.x with non-default RFC2616 compliance enabled\" - the target uses default RFC7230 mode which enforces the protections.\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.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T13:45:52.646915+00:00",
      "status_notes": "Vulnerability CVE-2017-7657 affects version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2017-7657"
      },
      "action_statement": "Vulnerability CVE-2017-7657 affects version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T13:45:52.646915+00:00",
      "status_notes": "Vulnerability CVE-2017-7658 does not affect version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server. The target Jetty 9.4.57.v20241219 is NOT affected by CVE-2017-7658 (HTTP Request Smuggling via multiple Content-Length headers or Content-Length + Transfer-Encoding: chunked). The vulnerability pattern is not present because the upstream fix (commit a285deea42f by Greg Wilkins, May 2018) was already included in the 9.4.57 release that TuxCare onboarded. The target's HttpParser.java enforces RFC7230 compliance by default, rejecting requests with multiple Content-Length headers or conflicting Content-Length + Transfer-Encoding headers via BadMessageException (400 Bad Request). This is an upstream vendor fix, not a TuxCare backport.\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": "The target Jetty 9.4.57.v20241219 is NOT affected by CVE-2017-7658 (HTTP Request Smuggling via multiple Content-Length headers or Content-Length + Transfer-Encoding: chunked). The vulnerability pattern is not present because the upstream fix (commit a285deea42f by Greg Wilkins, May 2018) was already included in the 9.4.57 release that TuxCare onboarded. The target's HttpParser.java enforces RFC7230 compliance by default, rejecting requests with multiple Content-Length headers or conflicting Content-Length + Transfer-Encoding headers via BadMessageException (400 Bad Request). This is an upstream vendor fix, not a TuxCare backport.\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.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T13:45:52.646915+00:00",
      "status_notes": "Vulnerability CVE-2017-9735 does not affect version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server. CVE-2017-9735 (timing channel in password comparison) is not present in target version 9.4.57.v20241219. The vulnerable pattern (variable-time String.equals/Arrays.equals) was replaced with constant-time stringEquals/byteEquals methods by upstream Jetty developers in 2017. This fix shipped in the upstream release that TuxCare onboarded, prior to any TuxCare modifications. The implementation uses sophisticated constant-time comparison that always loops for the attacker-controlled input length, uses bitwise AND to avoid short-circuits, and employs modulo arithmetic to prevent timing leaks from length mismatches.\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 in password comparison) is not present in target version 9.4.57.v20241219. The vulnerable pattern (variable-time String.equals/Arrays.equals) was replaced with constant-time stringEquals/byteEquals methods by upstream Jetty developers in 2017. This fix shipped in the upstream release that TuxCare onboarded, prior to any TuxCare modifications. The implementation uses sophisticated constant-time comparison that always loops for the attacker-controlled input length, uses bitwise AND to avoid short-circuits, and employs modulo arithmetic to prevent timing leaks from length mismatches.\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.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T13:45:52.646915+00:00",
      "status_notes": "Vulnerability CVE-2018-12536 does not affect version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2018-12536 describes path disclosure in Jetty 9.x when InvalidPathException containing full server paths is included in error responses. The target version 9.4.57.v20241219 is NOT affected because ResourceContentFactory.getContent() wraps all resource loading operations in a try-catch block that sanitizes exceptions, re-throwing InvalidPathException with only the request path (not system pa...",
      "vulnerability": {
        "name": "CVE-2018-12536"
      },
      "impact_statement": "not_affected \u2014 CVE-2018-12536 describes path disclosure in Jetty 9.x when InvalidPathException containing full server paths is included in error responses. The target version 9.4.57.v20241219 is NOT affected because ResourceContentFactory.getContent() wraps all resource loading operations in a try-catch block that sanitizes exceptions, re-throwing InvalidPathException with only the request path (not system pa..."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T13:45:52.646915+00:00",
      "status_notes": "Vulnerability CVE-2018-12538 affects version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2018-12538"
      },
      "action_statement": "Vulnerability CVE-2018-12538 affects version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T13:45:52.646915+00:00",
      "status_notes": "Vulnerability CVE-2018-12545 does not affect version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server. CVE-2018-12545 is NOT present in target Jetty 9.4.57.v20241219-tuxcare.6. The vulnerability (DoS via excessive HTTP/2 SETTINGS frames) was fixed by upstream in July-August 2018 through commits that added: (1) maxSettingsKeys limit (default 64) to reject frames with too many settings (ENHANCE_YOUR_CALM error), and (2) RateControl mechanism (default WindowRateControl with 128 events/sec) to reject excessive frame rates. Both defenses are present, active by default, and properly wired in SettingsBodyParser.java and AbstractHTTP2ServerConnectionFactory.java. The fix (commit 9eca404da29 by simone.bordet@gmail.com, 2018-07-18) is an ancestor of the first TuxCare commit (7d86f2018ba \"Initial setup 9.4.57.v20241219\"), meaning it shipped in the upstream Jetty 9.4.57 release that TuxCare onboarded. This is an upstream fix, not a TuxCare backport.\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 is NOT present in target Jetty 9.4.57.v20241219-tuxcare.6. The vulnerability (DoS via excessive HTTP/2 SETTINGS frames) was fixed by upstream in July-August 2018 through commits that added: (1) maxSettingsKeys limit (default 64) to reject frames with too many settings (ENHANCE_YOUR_CALM error), and (2) RateControl mechanism (default WindowRateControl with 128 events/sec) to reject excessive frame rates. Both defenses are present, active by default, and properly wired in SettingsBodyParser.java and AbstractHTTP2ServerConnectionFactory.java. The fix (commit 9eca404da29 by simone.bordet@gmail.com, 2018-07-18) is an ancestor of the first TuxCare commit (7d86f2018ba \"Initial setup 9.4.57.v20241219\"), meaning it shipped in the upstream Jetty 9.4.57 release that TuxCare onboarded. This is an upstream fix, not a TuxCare backport.\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.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T13:45:52.646915+00:00",
      "status_notes": "Vulnerability CVE-2019-10241 does not affect version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2019-10241 XSS vulnerability in directory listings is NOT present in this target. The upstream fix (commit 7b774d82e82, April 2019) was already included in the Jetty 9.4.57.v20241219 release that TuxCare onboarded. The vulnerable pattern where full paths could be exposed in directory listings has been replaced with the secure getFileName() method that extracts only the filename component.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-10241"
      },
      "impact_statement": "not_affected \u2014 CVE-2019-10241 XSS vulnerability in directory listings is NOT present in this target. The upstream fix (commit 7b774d82e82, April 2019) was already included in the Jetty 9.4.57.v20241219 release that TuxCare onboarded. The vulnerable pattern where full paths could be exposed in directory listings has been replaced with the secure getFileName() method that extracts only the filename component."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T13:45:52.646915+00:00",
      "status_notes": "Vulnerability CVE-2019-10246 does not affect version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2019-10246 is not present in Jetty 9.4.57.v20241219. The vulnerability, which exposed full filesystem paths in directory listings on Windows, was fixed by upstream Jetty in April 2019 (commit 7b774d82e82, released in version 9.4.16). The fix introduced a getFileName() method that extracts only the filename from resource paths, preventing full path disclosure. This fix was already present in...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-10246"
      },
      "impact_statement": "not_affected \u2014 CVE-2019-10246 is not present in Jetty 9.4.57.v20241219. The vulnerability, which exposed full filesystem paths in directory listings on Windows, was fixed by upstream Jetty in April 2019 (commit 7b774d82e82, released in version 9.4.16). The fix introduced a getFileName() method that extracts only the filename from resource paths, preventing full path disclosure. This fix was already present in..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T13:45:52.646915+00:00",
      "status_notes": "Vulnerability CVE-2019-10247 does not affect version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2019-10247 is NOT present in this version. The vulnerability involved DefaultHandler's 404 error response revealing filesystem paths via context.toString() output. The target version 9.4.57.v20241219 contains upstream fixes (commits 04c994712c0 and 9f506e4123b) that removed the context.toString() call, preventing filesystem path disclosure. These fixes were authored by upstream Jetty develo...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-10247"
      },
      "impact_statement": "not_affected \u2014 CVE-2019-10247 is NOT present in this version. The vulnerability involved DefaultHandler's 404 error response revealing filesystem paths via context.toString() output. The target version 9.4.57.v20241219 contains upstream fixes (commits 04c994712c0 and 9f506e4123b) that removed the context.toString() call, preventing filesystem path disclosure. These fixes were authored by upstream Jetty develo..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T13:45:52.646915+00:00",
      "status_notes": "Vulnerability CVE-2019-17632 does not affect version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2019-17632 describes unescaped exception messages in Jetty error responses (HTML and JSON), enabling XSS attacks. The target repository (9.4.57.v20241219) contains the upstream vendor's fix commits (cf0df6e3ffd and 9e40fc9a6fb) that add StringUtil.sanitizeXmlString() sanitization to error output. Both commits are ancestors of HEAD and were already in the upstream release before TuxCare onbo...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-17632"
      },
      "impact_statement": "not_affected \u2014 CVE-2019-17632 describes unescaped exception messages in Jetty error responses (HTML and JSON), enabling XSS attacks. The target repository (9.4.57.v20241219) contains the upstream vendor's fix commits (cf0df6e3ffd and 9e40fc9a6fb) that add StringUtil.sanitizeXmlString() sanitization to error output. Both commits are ancestors of HEAD and were already in the upstream release before TuxCare onbo..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T13:45:52.646915+00:00",
      "status_notes": "Vulnerability CVE-2019-17638 does not affect version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server. The target is NOT AFFECTED by CVE-2019-17638. The vulnerability (double-release of ByteBuffer leading to cross-client data leakage) was fixed in upstream Jetty commit ff8ae56fa93 (June 3, 2020) by Greg Wilkins. This fix was already present in the upstream Jetty 9.4.57.v20241219 release before TuxCare onboarded it (first TuxCare commit: 7d86f2018ba, \"Initial setup 9.4.57.v20241219\"). The target code contains all defensive mechanisms: releaseHeader() and releaseChunk() methods that null buffer references after release, proper scoping of _chunk to SendCallback instance level, and no class-level _chunk field. The CVE affected versions 9.4.27-9.4.29; target version 9.4.57 is well beyond this range.\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": "The target is NOT AFFECTED by CVE-2019-17638. The vulnerability (double-release of ByteBuffer leading to cross-client data leakage) was fixed in upstream Jetty commit ff8ae56fa93 (June 3, 2020) by Greg Wilkins. This fix was already present in the upstream Jetty 9.4.57.v20241219 release before TuxCare onboarded it (first TuxCare commit: 7d86f2018ba, \"Initial setup 9.4.57.v20241219\"). The target code contains all defensive mechanisms: releaseHeader() and releaseChunk() methods that null buffer references after release, proper scoping of _chunk to SendCallback instance level, and no class-level _chunk field. The CVE affected versions 9.4.27-9.4.29; target version 9.4.57 is well beyond this range.\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.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T13:45:52.646915+00:00",
      "status_notes": "Vulnerability CVE-2020-27218 does not affect version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2020-27218 (Issue #5605): The target Jetty 9.4.57.v20241219 is NOT AFFECTED. The vulnerability, which allowed unconsumed gzip-compressed request body content to leak into subsequent requests on the same HTTP connection, was fixed by upstream Jetty developer Greg Wilkins in commit 14f94f738df. This fix was already present in the upstream release 9.4.57.v20241219 that TuxCare onboarded. The f...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2020-27218"
      },
      "impact_statement": "not_affected \u2014 CVE-2020-27218 (Issue #5605): The target Jetty 9.4.57.v20241219 is NOT AFFECTED. The vulnerability, which allowed unconsumed gzip-compressed request body content to leak into subsequent requests on the same HTTP connection, was fixed by upstream Jetty developer Greg Wilkins in commit 14f94f738df. This fix was already present in the upstream release 9.4.57.v20241219 that TuxCare onboarded. The f..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T13:45:52.646915+00:00",
      "status_notes": "Vulnerability CVE-2020-27223 does not affect version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2020-27223 is NOT present in the target. The vulnerability concerned an O(n\u00b2) bubble-sort algorithm in QuotedQualityCSV.sort() that caused DoS when processing HTTP headers with many quality parameters. The target version 9.4.57.v20241219 contains the upstream fix (commit 10e531756b9, Feb 2021) that replaced the bubble sort with efficient O(n log n) stream-based sorting. This fix was already...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2020-27223"
      },
      "impact_statement": "not_affected \u2014 CVE-2020-27223 is NOT present in the target. The vulnerability concerned an O(n\u00b2) bubble-sort algorithm in QuotedQualityCSV.sort() that caused DoS when processing HTTP headers with many quality parameters. The target version 9.4.57.v20241219 contains the upstream fix (commit 10e531756b9, Feb 2021) that replaced the bubble sort with efficient O(n log n) stream-based sorting. This fix was already..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T13:45:52.646915+00:00",
      "status_notes": "Vulnerability CVE-2021-28165 does not affect version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server. CVE-2021-28165: Target is NOT AFFECTED. The vulnerability (high CPU usage from large TLS frames > 17408 bytes) was fixed by upstream Eclipse Jetty in commit 294b2ba02b6 authored by simone.bordet@gmail.com. This fix was already present in upstream release 9.4.57.v20241219 when TuxCare onboarded it. The defense code (checking BufferUtil.space(_encryptedInput) == 0 and throwing SSLHandshakeException) is present at jetty-io/src/main/java/org/eclipse/jetty/io/ssl/SslConnection.java:753-756, preventing the infinite loop that caused CPU exhaustion.\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: Target is NOT AFFECTED. The vulnerability (high CPU usage from large TLS frames > 17408 bytes) was fixed by upstream Eclipse Jetty in commit 294b2ba02b6 authored by simone.bordet@gmail.com. This fix was already present in upstream release 9.4.57.v20241219 when TuxCare onboarded it. The defense code (checking BufferUtil.space(_encryptedInput) == 0 and throwing SSLHandshakeException) is present at jetty-io/src/main/java/org/eclipse/jetty/io/ssl/SslConnection.java:753-756, preventing the infinite loop that caused CPU exhaustion.\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.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T13:45:52.646915+00:00",
      "status_notes": "Vulnerability CVE-2021-34428 does not affect version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server. Version 9.4.57.v20241219 is not affected by CVE-2021-34428: the security fix is already present in the target branch. Momus prerequisite check: \"All 1 patch commits already exist in target branch\". No backport needed.",
      "vulnerability": {
        "name": "CVE-2021-34428"
      },
      "impact_statement": "Version 9.4.57.v20241219 is not affected by CVE-2021-34428: the security fix is already present in the target branch. Momus prerequisite check: \"All 1 patch commits already exist in target branch\". No backport needed."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-10T04:14:20.974341+00:00",
      "status_notes": "Vulnerability CVE-2022-2191 does not affect version 9.4.57.v20241219-tuxcare.7 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 buffers left unreleased after TLS errors remain eligible for garbage collection instead of being permanently retained by the pool. The pool removes acquired buffers from its queue (jetty-io/src/main/java/org/eclipse/jetty/io/ArrayByteBufferPool.java:123). Closed endpoints are removed from the connector (jetty-server/src/main/java/org/eclipse/jetty/server/AbstractConnector.java:750), and the pool contract allows unreleased buffers to be garbage collected (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 buffers left unreleased after TLS errors remain eligible for garbage collection instead of being permanently retained by the pool. The pool removes acquired buffers from its queue (jetty-io/src/main/java/org/eclipse/jetty/io/ArrayByteBufferPool.java:123). Closed endpoints are removed from the connector (jetty-server/src/main/java/org/eclipse/jetty/server/AbstractConnector.java:750), and the pool contract allows unreleased buffers to be garbage collected (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.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T13:45:52.646915+00:00",
      "status_notes": "Vulnerability CVE-2023-26048 does not affect version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2023-26048 is not present in target version 9.4.57.v20241219. The upstream fix was already included in this release. The fix adds two defenses: (1) a part count limit (_maxParts, default 1000) that prevents processing excessive numbers of multipart parts, and (2) a form content size limit (maxFormContentSize) that prevents unbounded memory consumption from parts without filenames. Both defe...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-26048"
      },
      "impact_statement": "not_affected \u2014 CVE-2023-26048 is not present in target version 9.4.57.v20241219. The upstream fix was already included in this release. The fix adds two defenses: (1) a part count limit (_maxParts, default 1000) that prevents processing excessive numbers of multipart parts, and (2) a form content size limit (maxFormContentSize) that prevents unbounded memory consumption from parts without filenames. Both defe..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T13:45:52.646915+00:00",
      "status_notes": "Vulnerability CVE-2023-26049 does not affect version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2023-26049 describes a cookie smuggling vulnerability where Jetty's nonstandard cookie parsing allows an attacker to embed semicolons within quoted cookie values, bypassing normal cookie separation. The target repository (Jetty 9.4.57.v20241219) is NOT AFFECTED because the upstream fix was already included in the 9.4.57 release. The fix (commit 1be1401, authored by gregw@webtide.com) adds s...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-26049"
      },
      "impact_statement": "not_affected \u2014 CVE-2023-26049 describes a cookie smuggling vulnerability where Jetty's nonstandard cookie parsing allows an attacker to embed semicolons within quoted cookie values, bypassing normal cookie separation. The target repository (Jetty 9.4.57.v20241219) is NOT AFFECTED because the upstream fix was already included in the 9.4.57 release. The fix (commit 1be1401, authored by gregw@webtide.com) adds s..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-06T18:15:41.281614+00:00",
      "status_notes": "Vulnerability CVE-2024-13009 does not affect version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server. Prechecker: The upstream fix is already in this version's source history (commit e3fa9466). The upstream fix was released in 9.4.57.v20241219, which is this version. Advisories: GitHub GHSA-q4rv-gq96-w7c5 (fixed in 9.4.57.v20241219), NVD (fixed in 9.4.57), CVE record (last affected 9.4.56), Snyk (fixed in 9.4.57.v20241219).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2024-13009"
      },
      "impact_statement": "Prechecker: The upstream fix is already in this version's source history (commit e3fa9466). The upstream fix was released in 9.4.57.v20241219, which is this version. Advisories: GitHub GHSA-q4rv-gq96-w7c5 (fixed in 9.4.57.v20241219), NVD (fixed in 9.4.57), CVE record (last affected 9.4.56), Snyk (fixed in 9.4.57.v20241219)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-10T04:14:20.974341+00:00",
      "status_notes": "Vulnerability CVE-2024-7708 does not affect version 9.4.57.v20241219-tuxcare.7 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 leak. Parsing runs after filling and before the zero-byte exit at jetty-server/src/main/java/org/eclipse/jetty/server/HttpConnection.java:327. Parsing releases buffers with no content references at jetty-server/src/main/java/org/eclipse/jetty/server/HttpConnection.java:387; the release method clears the buffer field and returns the empty buffer to the pool at jetty-server/src/main/java/org/eclipse/jetty/server/HttpConnection.java: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 leak. Parsing runs after filling and before the zero-byte exit at jetty-server/src/main/java/org/eclipse/jetty/server/HttpConnection.java:327. Parsing releases buffers with no content references at jetty-server/src/main/java/org/eclipse/jetty/server/HttpConnection.java:387; the release method clears the buffer field and returns the empty buffer to the pool at jetty-server/src/main/java/org/eclipse/jetty/server/HttpConnection.java:224."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T13:45:52.646915+00:00",
      "status_notes": "Vulnerability CVE-2024-8184 does not affect version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server. Version 9.4.57.v20241219 is not vulnerable. Summary: The target repository has already been patched for CVE-2024-8184. The vulnerable get/putIfAbsent pattern has been replaced with atomic compute operations and reference counting, preventing the memory leak that causes DoS. [terminalized not_affected from patch_application_manual/not_vulnerable]",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2024-8184"
      },
      "impact_statement": "Version 9.4.57.v20241219 is not vulnerable. Summary: The target repository has already been patched for CVE-2024-8184. The vulnerable get/putIfAbsent pattern has been replaced with atomic compute operations and reference counting, preventing the memory leak that causes DoS. [terminalized not_affected from patch_application_manual/not_vulnerable]"
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T13:45:52.646915+00:00",
      "status_notes": "Vulnerability CVE-2026-10051 does not affect version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server. not_affected \u2014 Jetty 9.4.57.v20241219-tuxcare.4 is NOT affected by CVE-2026-10051. The vulnerability targets Jetty 12.x architecture where the _trailers field in HttpConnection was never reset between requests. Jetty 9.4.57 uses a different architecture where _trailers fields exist in HttpChannelOverHttp and HttpChannel classes, and BOTH are properly cleared to null in their respective recycle() methods, whic...",
      "vulnerability": {
        "name": "CVE-2026-10051"
      },
      "impact_statement": "not_affected \u2014 Jetty 9.4.57.v20241219-tuxcare.4 is NOT affected by CVE-2026-10051. The vulnerability targets Jetty 12.x architecture where the _trailers field in HttpConnection was never reset between requests. Jetty 9.4.57 uses a different architecture where _trailers fields exist in HttpChannelOverHttp and HttpChannel classes, and BOTH are properly cleared to null in their respective recycle() methods, whic..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T13:45:52.646915+00:00",
      "status_notes": "Vulnerability CVE-2026-1605 does not affect version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server. Version 9.4.57.v20241219 is not vulnerable. Summary: Target repository is Jetty 9.4.57.v20241219, which is not in the affected version range for CVE-2026-1605 (Jetty 12.0.0-12.0.31 and 12.1.0-12.0.5). The architecture and resource management patterns are fundamentally different from Jetty 12.x, and the specific vulnerability pattern does not exist in this version. [terminalized not_affected from patch_application_manual/not_vulnerable]",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-1605"
      },
      "impact_statement": "Version 9.4.57.v20241219 is not vulnerable. Summary: Target repository is Jetty 9.4.57.v20241219, which is not in the affected version range for CVE-2026-1605 (Jetty 12.0.0-12.0.31 and 12.1.0-12.0.5). The architecture and resource management patterns are fundamentally different from Jetty 12.x, and the specific vulnerability pattern does not exist in this version. [terminalized not_affected from patch_application_manual/not_vulnerable]"
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.57.v20241219-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-04T13:46:37.592358+00:00",
      "status_notes": "Vulnerability CVE-2026-6790 is fixed in version 9.4.57.v20241219-tuxcare.7 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2026-6790"
      }
    }
  ]
}
