{
  "@id": "urn:uuid:07f04318-661f-4f46-ba16-9cc758d52ab1",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 4,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-10T04:16:00.061099+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:39.218308+00:00",
      "status_notes": "Vulnerability CVE-2006-6969 does not affect version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2006-6969 affects Jetty versions before 4.2.27, 5.1.12, 6.0.2, and 6.1.0pre3 due to predictable session ID generation using java.util.Random. The target version 9.4.58.v20250814 is NOT affected. The vulnerable pattern (using java.util.Random for session IDs) is not present in the default code path. DefaultSessionIdManager.initRandom() (lines 368-385) uses SecureRandom by default, only falli...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2006-6969"
      },
      "impact_statement": "not_affected \u2014 CVE-2006-6969 affects Jetty versions before 4.2.27, 5.1.12, 6.0.2, and 6.1.0pre3 due to predictable session ID generation using java.util.Random. The target version 9.4.58.v20250814 is NOT affected. The vulnerable pattern (using java.util.Random for session IDs) is not present in the default code path. DefaultSessionIdManager.initRandom() (lines 368-385) uses SecureRandom by default, only falli..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:39.218308+00:00",
      "status_notes": "Vulnerability CVE-2011-4461 does not affect version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2011-4461 is NOT PRESENT in this target. The vulnerability describes a hash collision DoS attack via unbounded form parameters. The upstream fix (commit 085c79d7d6c by Greg Wilkins, Dec 2011) adds a configurable limit (maxFormKeys, default 1000) to prevent CPU exhaustion from processing excessive form parameters. This fix was already included in the upstream Jetty 9.4.58.v20250814 release t...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2011-4461"
      },
      "impact_statement": "not_affected \u2014 CVE-2011-4461 is NOT PRESENT in this target. The vulnerability describes a hash collision DoS attack via unbounded form parameters. The upstream fix (commit 085c79d7d6c by Greg Wilkins, Dec 2011) adds a configurable limit (maxFormKeys, default 1000) to prevent CPU exhaustion from processing excessive form parameters. This fix was already included in the upstream Jetty 9.4.58.v20250814 release t..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:39.218308+00:00",
      "status_notes": "Vulnerability CVE-2015-2080 does not affect version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server. Prechecker: An upstream release that contains the fix is part of this version's source history, and the code the fix removes is gone. Version 9.4.58.v20250814 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: An upstream release that contains the fix is part of this version's source history, and the code the fix removes is gone. Version 9.4.58.v20250814 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.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:39.218308+00:00",
      "status_notes": "Vulnerability CVE-2016-4800 does not affect version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2016-4800 affects Eclipse Jetty 9.3.x before 9.3.9. The target version 9.4.58.v20250814 contains the upstream fix (commit 97af3d663fd from May 2016) that addresses the Windows path normalization vulnerability. The fix was authored by Joakim Erdfelt and shipped in upstream Jetty 9.3.9, well before this version. The PathResource class now properly detects aliasing by comparing the original UR...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2016-4800"
      },
      "impact_statement": "not_affected \u2014 CVE-2016-4800 affects Eclipse Jetty 9.3.x before 9.3.9. The target version 9.4.58.v20250814 contains the upstream fix (commit 97af3d663fd from May 2016) that addresses the Windows path normalization vulnerability. The fix was authored by Joakim Erdfelt and shipped in upstream Jetty 9.3.9, well before this version. The PathResource class now properly detects aliasing by comparing the original UR..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:39.218308+00:00",
      "status_notes": "Vulnerability CVE-2017-7656 does not affect version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server. CVE-2017-7656 HTTP Request Smuggling vulnerability is not present in Jetty 9.4.58.v20250814. The upstream fix (commit a285deea from May 2018) was already included in the upstream release when TuxCare onboarded version 9.4.58.v20250814. The target uses the default RFC7230 compliance mode which actively enforces protections against multiple Content-Length headers, Content-Length+Transfer-Encoding combinations, and chunk length overflow. The CVE only affects 9.4.x in non-default RFC2616 compliance mode, which explicitly disables these 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 vulnerability is not present in Jetty 9.4.58.v20250814. The upstream fix (commit a285deea from May 2018) was already included in the upstream release when TuxCare onboarded version 9.4.58.v20250814. The target uses the default RFC7230 compliance mode which actively enforces protections against multiple Content-Length headers, Content-Length+Transfer-Encoding combinations, and chunk length overflow. The CVE only affects 9.4.x in non-default RFC2616 compliance mode, which explicitly disables these 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.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:39.218308+00:00",
      "status_notes": "Vulnerability CVE-2017-7657 affects version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2017-7657"
      },
      "action_statement": "Vulnerability CVE-2017-7657 affects version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:39.218308+00:00",
      "status_notes": "Vulnerability CVE-2017-7658 does not affect version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server. CVE-2017-7658 (HTTP Request Smuggling via duplicate Content-Length or Content-Length + Transfer-Encoding headers) is NOT PRESENT in Jetty 9.4.58.v20250814-tuxcare.7. The upstream vendor fix (commit a285deea by Greg Wilkins) shipped in the upstream Jetty 9.4.58 release and is present in the target. The HttpParser includes compliance checks for MULTIPLE_CONTENT_LENGTHS and TRANSFER_ENCODING_WITH_CONTENT_LENGTH, active by default in RFC7230 mode, that reject malformed requests matching the CVE's attack pattern.\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 duplicate Content-Length or Content-Length + Transfer-Encoding headers) is NOT PRESENT in Jetty 9.4.58.v20250814-tuxcare.7. The upstream vendor fix (commit a285deea by Greg Wilkins) shipped in the upstream Jetty 9.4.58 release and is present in the target. The HttpParser includes compliance checks for MULTIPLE_CONTENT_LENGTHS and TRANSFER_ENCODING_WITH_CONTENT_LENGTH, active by default in RFC7230 mode, that reject malformed requests matching the CVE's attack pattern.\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.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:39.218308+00:00",
      "status_notes": "Vulnerability CVE-2017-9735 does not affect version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server. CVE-2017-9735 timing attack vulnerability is NOT present in the target. The target contains a comprehensive constant-time comparison fix that was already included in the upstream Jetty 9.4.58.v20250814 release. The fix replaces variable-time String.equals() and Arrays.equals() with constant-time stringEquals() and byteEquals() methods in Password.java and Credential.java, preventing attackers from inferring password content through timing measurements. The implementation (commit e727ad89 by lachlan@webtide.com, Oct 2018) is more advanced than the original CVE-2017-9735 patches, using modulo indexing and unknown-length looping to prevent both timing attacks and ArithmeticException. 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.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 attack vulnerability is NOT present in the target. The target contains a comprehensive constant-time comparison fix that was already included in the upstream Jetty 9.4.58.v20250814 release. The fix replaces variable-time String.equals() and Arrays.equals() with constant-time stringEquals() and byteEquals() methods in Password.java and Credential.java, preventing attackers from inferring password content through timing measurements. The implementation (commit e727ad89 by lachlan@webtide.com, Oct 2018) is more advanced than the original CVE-2017-9735 patches, using modulo indexing and unknown-length looping to prevent both timing attacks and ArithmeticException. 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.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.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:39.218308+00:00",
      "status_notes": "Vulnerability CVE-2018-12536 does not affect version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2018-12536 is not present in this version. The upstream fix (issue #2560) that prevents filesystem path disclosure through InvalidPathException messages was already included in the upstream release 9.4.58.v20250814. ResourceContentFactory.getContent() wraps resource loading in a try-catch block that sanitizes exception messages to contain only user-provided input, not internal filesystem pa...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-12536"
      },
      "impact_statement": "not_affected \u2014 CVE-2018-12536 is not present in this version. The upstream fix (issue #2560) that prevents filesystem path disclosure through InvalidPathException messages was already included in the upstream release 9.4.58.v20250814. ResourceContentFactory.getContent() wraps resource loading in a try-catch block that sanitizes exception messages to contain only user-provided input, not internal filesystem pa..."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:39.218308+00:00",
      "status_notes": "Vulnerability CVE-2018-12538 affects version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2018-12538"
      },
      "action_statement": "Vulnerability CVE-2018-12538 affects version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:39.218308+00:00",
      "status_notes": "Vulnerability CVE-2018-12545 does not affect version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server. Target Jetty 9.4.58.v20250814 is NOT AFFECTED by CVE-2018-12545. The vulnerability (DoS via unbounded SETTINGS frame processing) was fixed by upstream Eclipse Jetty in commits 9eca404da29 (2018-07-18, maxSettingsKeys defense) and 508ad4aff91 (2019-08-17, RateControl defense). Both fixes were already present in the upstream release version 9.4.58.v20250814 when TuxCare onboarded it (first TuxCare commit: 69ac75396aae \"Onboard version 9.4.58.v20250814\"). The vulnerable code pattern (unbounded processing of SETTINGS frame entries) is not present in the target.\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": "Target Jetty 9.4.58.v20250814 is NOT AFFECTED by CVE-2018-12545. The vulnerability (DoS via unbounded SETTINGS frame processing) was fixed by upstream Eclipse Jetty in commits 9eca404da29 (2018-07-18, maxSettingsKeys defense) and 508ad4aff91 (2019-08-17, RateControl defense). Both fixes were already present in the upstream release version 9.4.58.v20250814 when TuxCare onboarded it (first TuxCare commit: 69ac75396aae \"Onboard version 9.4.58.v20250814\"). The vulnerable code pattern (unbounded processing of SETTINGS frame entries) is not present in the target.\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.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:39.218308+00:00",
      "status_notes": "Vulnerability CVE-2019-10241 does not affect version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2019-10241 (XSS in directory listings) is NOT present in target version 9.4.58.v20250814. The vulnerability was fixed in upstream commit 3d028ab2ca7 (Issue #3549) by Joakim Erdfelt, which added the getFileName() method to extract only the filename (last path segment) instead of using full paths in directory listing HTML. This fix was already present in upstream release 9.4.58 when TuxCare o...",
      "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.58.v20250814. The vulnerability was fixed in upstream commit 3d028ab2ca7 (Issue #3549) by Joakim Erdfelt, which added the getFileName() method to extract only the filename (last path segment) instead of using full paths in directory listing HTML. This fix was already present in upstream release 9.4.58 when TuxCare o..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:39.218308+00:00",
      "status_notes": "Vulnerability CVE-2019-10246 does not affect version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2019-10246 is not present in the target. The vulnerability was fixed by upstream commit 7b774d82e82 authored by joakim.erdfelt@gmail.com, which shipped in upstream release 9.4.58.v20250814 before TuxCare onboarded it (onboarding commit: 69ac75396aae). The fix introduces a getFileName() method that properly extracts just the filename using File.getName() or URL-decoded segment extraction, pr...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-10246"
      },
      "impact_statement": "not_affected \u2014 CVE-2019-10246 is not present in the target. The vulnerability was fixed by upstream commit 7b774d82e82 authored by joakim.erdfelt@gmail.com, which shipped in upstream release 9.4.58.v20250814 before TuxCare onboarded it (onboarding commit: 69ac75396aae). The fix introduces a getFileName() method that properly extracts just the filename using File.getName() or URL-decoded segment extraction, pr..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:39.218308+00:00",
      "status_notes": "Vulnerability CVE-2019-10247 does not affect version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server. not_affected \u2014 Target version 9.4.58.v20250814 is not affected by CVE-2019-10247. The vulnerability (information disclosure of filesystem paths via context.toString() in 404 error pages) was fixed by upstream commit 04c994712c0 authored by Joakim Erdfelt, which shipped in the upstream release before TuxCare onboarded this version. The vulnerable code pattern (outputting context.toString() which includes base ...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-10247"
      },
      "impact_statement": "not_affected \u2014 Target version 9.4.58.v20250814 is not affected by CVE-2019-10247. The vulnerability (information disclosure of filesystem paths via context.toString() in 404 error pages) was fixed by upstream commit 04c994712c0 authored by Joakim Erdfelt, which shipped in the upstream release before TuxCare onboarded this version. The vulnerable code pattern (outputting context.toString() which includes base ..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:39.218308+00:00",
      "status_notes": "Vulnerability CVE-2019-17632 does not affect version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2019-17632 is NOT present in Jetty 9.4.58.v20250814. The vulnerability affected versions 9.4.21-9.4.23 where exception messages in error pages were rendered without HTML escaping, enabling XSS attacks. The upstream fix (commits 9e40fc9a6fb and cf0df6e3ffd by Joakim Erdfelt) was applied in November 2019 and was already present in the upstream Jetty 9.4.58.v20250814 release that TuxCare onboa...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-17632"
      },
      "impact_statement": "not_affected \u2014 CVE-2019-17632 is NOT present in Jetty 9.4.58.v20250814. The vulnerability affected versions 9.4.21-9.4.23 where exception messages in error pages were rendered without HTML escaping, enabling XSS attacks. The upstream fix (commits 9e40fc9a6fb and cf0df6e3ffd by Joakim Erdfelt) was applied in November 2019 and was already present in the upstream Jetty 9.4.58.v20250814 release that TuxCare onboa..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:39.218308+00:00",
      "status_notes": "Vulnerability CVE-2019-17638 does not affect version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server. CVE-2019-17638 affects Jetty versions 9.4.27.v20200227 to 9.4.29.v20200521 (released in May 2020). The vulnerability involves double-release of ByteBuffer when handling oversized response headers, potentially exposing sensitive data across client sessions. The upstream fix (commit ff8ae56fa93, June 3, 2020, authored by gregw@webtide.com) was included in Jetty 9.4.30.v20200611 and all subsequent releases. The target version 9.4.58.v20250814 was onboarded by TuxCare from upstream with the fix already present. The defense code (releaseHeader/releaseChunk methods that null buffer references after release) is verified present in HttpConnection.java at the target SHA.\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": "CVE-2019-17638 affects Jetty versions 9.4.27.v20200227 to 9.4.29.v20200521 (released in May 2020). The vulnerability involves double-release of ByteBuffer when handling oversized response headers, potentially exposing sensitive data across client sessions. The upstream fix (commit ff8ae56fa93, June 3, 2020, authored by gregw@webtide.com) was included in Jetty 9.4.30.v20200611 and all subsequent releases. The target version 9.4.58.v20250814 was onboarded by TuxCare from upstream with the fix already present. The defense code (releaseHeader/releaseChunk methods that null buffer references after release) is verified present in HttpConnection.java at the target SHA.\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.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:39.218308+00:00",
      "status_notes": "Vulnerability CVE-2020-27218 does not affect version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2020-27218 (unconsumed GZIP request body causing data injection into subsequent requests on persistent connections) is NOT present in target version 9.4.58.v20250814-tuxcare.7. The fix (commit 14f94f738df5adf68549749d01d4f9d97ea51452, \"Issue #5605 unconsumed input on sendError\") was already included in the upstream Jetty release 9.4.58.v20250814 that TuxCare onboarded. The defense mechanism...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2020-27218"
      },
      "impact_statement": "not_affected \u2014 CVE-2020-27218 (unconsumed GZIP request body causing data injection into subsequent requests on persistent connections) is NOT present in target version 9.4.58.v20250814-tuxcare.7. The fix (commit 14f94f738df5adf68549749d01d4f9d97ea51452, \"Issue #5605 unconsumed input on sendError\") was already included in the upstream Jetty release 9.4.58.v20250814 that TuxCare onboarded. The defense mechanism..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:39.218308+00:00",
      "status_notes": "Vulnerability CVE-2020-27223 does not affect version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server. not_affected \u2014 The target version 9.4.58.v20250814 is not affected by CVE-2020-27223. The vulnerability affected Jetty versions 9.4.6 through 9.4.36, and was fixed in 9.4.37.v20210219. The target version includes the upstream fix (commit 10e531756b972162eed402c44d0244f7f6b85131) that replaced the inefficient O(n\u00b3) bubble-sort algorithm with an efficient O(n log n) comparator-based sort. The fix was authored b...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2020-27223"
      },
      "impact_statement": "not_affected \u2014 The target version 9.4.58.v20250814 is not affected by CVE-2020-27223. The vulnerability affected Jetty versions 9.4.6 through 9.4.36, and was fixed in 9.4.37.v20210219. The target version includes the upstream fix (commit 10e531756b972162eed402c44d0244f7f6b85131) that replaced the inefficient O(n\u00b3) bubble-sort algorithm with an efficient O(n log n) comparator-based sort. The fix was authored b..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:39.218308+00:00",
      "status_notes": "Vulnerability CVE-2021-28165 does not affect version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server. CVE-2021-28165 is NOT present in Jetty 9.4.58.v20250814. The upstream fix for the large TLS frame CPU exhaustion vulnerability (commit 294b2ba02b6, dated 2021-03-22) is already present in the target code at jetty-io/src/main/java/org/eclipse/jetty/io/ssl/SslConnection.java lines 753-757. The fix was shipped in the upstream release and predates the TuxCare onboarding commit (69ac75396aa). The defense correctly detects when the encrypted input buffer is full and cannot make progress, throwing SSLHandshakeException(\"Encrypted buffer max length exceeded\") to prevent the infinite loop that would cause 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 is NOT present in Jetty 9.4.58.v20250814. The upstream fix for the large TLS frame CPU exhaustion vulnerability (commit 294b2ba02b6, dated 2021-03-22) is already present in the target code at jetty-io/src/main/java/org/eclipse/jetty/io/ssl/SslConnection.java lines 753-757. The fix was shipped in the upstream release and predates the TuxCare onboarding commit (69ac75396aa). The defense correctly detects when the encrypted input buffer is full and cannot make progress, throwing SSLHandshakeException(\"Encrypted buffer max length exceeded\") to prevent the infinite loop that would cause 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": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:39.218308+00:00",
      "status_notes": "Vulnerability CVE-2021-34428 affects version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2021-34428"
      },
      "action_statement": "Vulnerability CVE-2021-34428 affects version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-10T04:16:00.061099+00:00",
      "status_notes": "Vulnerability CVE-2022-2191 does not affect version 9.4.58.v20250814-tuxcare.8 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, allowing unrecycled buffers to be garbage-collected with failed TLS connections. Acquisition removes buffers from the pool queue (jetty-io/src/main/java/org/eclipse/jetty/io/ByteBufferPool.java:181). TLS failures close the endpoint (jetty-io/src/main/java/org/eclipse/jetty/io/ssl/SslConnection.java:843), and closed endpoints are removed from the connector (jetty-server/src/main/java/org/eclipse/jetty/server/AbstractConnector.java:750).",
      "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, allowing unrecycled buffers to be garbage-collected with failed TLS connections. Acquisition removes buffers from the pool queue (jetty-io/src/main/java/org/eclipse/jetty/io/ByteBufferPool.java:181). TLS failures close the endpoint (jetty-io/src/main/java/org/eclipse/jetty/io/ssl/SslConnection.java:843), and closed endpoints are removed from the connector (jetty-server/src/main/java/org/eclipse/jetty/server/AbstractConnector.java:750)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:39.218308+00:00",
      "status_notes": "Vulnerability CVE-2023-26048 does not affect version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server. not_affected \u2014 Target version 9.4.58.v20250814 is NOT affected by CVE-2023-26048. The vulnerability (unbounded memory buffering of multipart parts without filename) was fixed in upstream Jetty 9.4.51.v20230217 and is not present in this version. Both required defenses are implemented: (1) content-size validation for parts-without-filename (Request.java:2523-2525) that throws IllegalStateException when cumulat...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-26048"
      },
      "impact_statement": "not_affected \u2014 Target version 9.4.58.v20250814 is NOT affected by CVE-2023-26048. The vulnerability (unbounded memory buffering of multipart parts without filename) was fixed in upstream Jetty 9.4.51.v20230217 and is not present in this version. Both required defenses are implemented: (1) content-size validation for parts-without-filename (Request.java:2523-2525) that throws IllegalStateException when cumulat..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:39.218308+00:00",
      "status_notes": "Vulnerability CVE-2023-26049 does not affect version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server. not_affected \u2014 CVE-2023-26049 (cookie smuggling via nonstandard quoted-value parsing) is NOT present in target Jetty 9.4.58.v20250814. The upstream fix (commit 1be1401bafb) was authored by gregw@webtide.com and shipped in Jetty 9.4.51.v20230217 (February 2023), over 2 years before TuxCare onboarded version 9.4.58.v20250814. The vulnerable pattern (parsing semicolons inside quoted cookie values as part of the ...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-26049"
      },
      "impact_statement": "not_affected \u2014 CVE-2023-26049 (cookie smuggling via nonstandard quoted-value parsing) is NOT present in target Jetty 9.4.58.v20250814. The upstream fix (commit 1be1401bafb) was authored by gregw@webtide.com and shipped in Jetty 9.4.51.v20230217 (February 2023), over 2 years before TuxCare onboarded version 9.4.58.v20250814. The vulnerable pattern (parsing semicolons inside quoted cookie values as part of the ..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:39.218308+00:00",
      "status_notes": "Vulnerability CVE-2024-13009 does not affect version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server. The target repository (Jetty 9.4.58.v20250814-tuxcare.7) is NOT AFFECTED by CVE-2024-13009. The vulnerability involves incorrect buffer release when gzip decompression fails, leading to potential data corruption or sharing between requests. However, the upstream fix (commit e3fa9466633 from 2024-12-19 by Greg Wilkins) was already present in the upstream Jetty 9.4.58 release that TuxCare onboarded on 2026-05-12. All protective code changes are present in the target: the _content reference is properly nulled after failed content in both fail() and addContent() methods, the nextContent() method includes the isError() check, and interceptor calls are properly handled. This is an upstream vendor fix, not a TuxCare backport.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 9.4.0, < 9.4.57.v20241219), NVD (>= 9.4.0, < 9.4.57), cve.org (>= 9.4.0, <= 9.4.56), Snyk (>= 9.4.0.M0, < 9.4.57.v20241219).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2024-13009"
      },
      "impact_statement": "The target repository (Jetty 9.4.58.v20250814-tuxcare.7) is NOT AFFECTED by CVE-2024-13009. The vulnerability involves incorrect buffer release when gzip decompression fails, leading to potential data corruption or sharing between requests. However, the upstream fix (commit e3fa9466633 from 2024-12-19 by Greg Wilkins) was already present in the upstream Jetty 9.4.58 release that TuxCare onboarded on 2026-05-12. All protective code changes are present in the target: the _content reference is properly nulled after failed content in both fail() and addContent() methods, the nextContent() method includes the isError() check, and interceptor calls are properly handled. This is an upstream vendor fix, not a TuxCare backport.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 9.4.0, < 9.4.57.v20241219), NVD (>= 9.4.0, < 9.4.57), cve.org (>= 9.4.0, <= 9.4.56), Snyk (>= 9.4.0.M0, < 9.4.57.v20241219)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T20:55:00.104909+00:00",
      "status_notes": "Vulnerability CVE-2024-7708 does not affect version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server. Re-checked 2026-11-10 by the vulnerability checker and confirmed by an independent code review: not affected. Body reads reach `fillAndParseForContent()` through HttpInputOverHTTP.java:33. Both callers of `fillRequestBuffer()` subsequently parse before exiting for a zero-byte result (HttpConnection.java:260, HttpConnection.java:327). Filling rejects outstanding content references and acquires a buffer only when empty (HttpConnection.java:337). Empty body parsing creates no content chunk because the content loop requires remaining bytes (HttpParser.java:1659, HttpParser.java:1682). Parsing releases the buffer when its content-reference count is zero; release clears the connection field and returns the empty buffer to the pool (HttpConnection.java:386, HttpConnection.java:224). Content callbacks also release at zero references, and the outer network exception handler clears and releases (HttpConnection.java:634, HttpConnection.java:296).",
      "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. Body reads reach `fillAndParseForContent()` through HttpInputOverHTTP.java:33. Both callers of `fillRequestBuffer()` subsequently parse before exiting for a zero-byte result (HttpConnection.java:260, HttpConnection.java:327). Filling rejects outstanding content references and acquires a buffer only when empty (HttpConnection.java:337). Empty body parsing creates no content chunk because the content loop requires remaining bytes (HttpParser.java:1659, HttpParser.java:1682). Parsing releases the buffer when its content-reference count is zero; release clears the connection field and returns the empty buffer to the pool (HttpConnection.java:386, HttpConnection.java:224). Content callbacks also release at zero references, and the outer network exception handler clears and releases (HttpConnection.java:634, HttpConnection.java:296)."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:39.218308+00:00",
      "status_notes": "Vulnerability CVE-2024-8184 affects version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2024-8184"
      },
      "action_statement": "Vulnerability CVE-2024-8184 affects version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:39.218308+00:00",
      "status_notes": "Vulnerability CVE-2026-10051 affects version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2026-10051"
      },
      "action_statement": "Vulnerability CVE-2026-10051 affects version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:39.218308+00:00",
      "status_notes": "Vulnerability CVE-2026-1605 affects version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2026-1605"
      },
      "action_statement": "Vulnerability CVE-2026-1605 affects version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8",
          "identifiers": {
            "purl": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.58.v20250814-tuxcare.8"
          }
        }
      ],
      "timestamp": "2026-11-09T18:21:51.752427+00:00",
      "status_notes": "Vulnerability CVE-2026-6790 is fixed in version 9.4.58.v20250814-tuxcare.8 of org.eclipse.jetty:jetty-server.",
      "vulnerability": {
        "name": "CVE-2026-6790"
      }
    }
  ]
}
