VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.eclipse.jetty.websocket:websocket-core-server: vulnerability history, versions and safety

org.eclipse.jetty.websocket:websocket-core-server is a package in the Maven ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Maven ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.eclipse.jetty.websocket:websocket-core-server vulnerabilities

Vulert verdict on org.eclipse.jetty.websocket:websocket-core-server 11.0.26 i

Updated on 23 Oct 2026

Good news: 11.0.26, the version you would install today, has no known vulnerabilities.

Package health score 84/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Active

What to do: Stay on 11.0.26 or newer. This can change: a vulnerability disclosed tomorrow can affect 11.0.26 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 11.0.26 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 86 packages i
  • Stars 4,099 i
  • Last release 14 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for org.eclipse.jetty.websocket:websocket-core-server, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
11.0.26 14 Aug 2025 none non-standard — Details →
10.0.26 14 Aug 2025 none non-standard — Details →
11.0.25 13 Mar 2025 none non-standard — Details →
10.0.25 13 Mar 2025 none non-standard — Details →
11.0.24 26 Aug 2024 none non-standard — Details →
10.0.24 26 Aug 2024 none non-standard — Details →
11.0.23 14 Aug 2024 none non-standard — Details →
10.0.23 14 Aug 2024 none non-standard — Details →
11.0.22 27 Jun 2024 none non-standard — Details →
10.0.22 27 Jun 2024 none non-standard — Details →
11.0.21 14 May 2024 none non-standard — Details →
10.0.21 14 May 2024 none non-standard — Details →
11.0.20 29 Jan 2024 none non-standard — Details →
10.0.20 29 Jan 2024 none non-standard — Details →
11.0.19 15 Dec 2023 none non-standard — Details →
10.0.19 15 Dec 2023 none non-standard — Details →
11.0.18 27 Oct 2023 none non-standard — Details →
10.0.18 27 Oct 2023 none non-standard — Details →
11.0.17 09 Oct 2023 none non-standard — Details →
10.0.17 09 Oct 2023 none non-standard — Details →
11.0.16 25 Aug 2023 none non-standard — Details →
10.0.16 25 Aug 2023 none non-standard — Details →
11.0.15 11 Apr 2023 none non-standard — Details →
10.0.15 11 Apr 2023 none non-standard — Details →
11.0.14 22 Feb 2023 none non-standard — Details →
10.0.14 22 Feb 2023 none non-standard — Details →
11.0.13 07 Dec 2022 none non-standard — Details →
10.0.13 07 Dec 2022 none non-standard — Details →
11.0.12 14 Sep 2022 none non-standard — Details →
10.0.12 14 Sep 2022 none non-standard — Details →
11.0.11 21 Jun 2022 none non-standard — Details →
10.0.11 21 Jun 2022 none non-standard — Details →
11.0.10 16 Jun 2022 none non-standard — Details →
10.0.10 16 Jun 2022 none non-standard — Details →
11.0.9 30 Mar 2022 none non-standard — Details →
10.0.9 30 Mar 2022 none non-standard — Details →
11.0.8 07 Feb 2022 none non-standard — Details →
10.0.8 07 Feb 2022 none non-standard — Details →
11.0.7 06 Oct 2021 none non-standard — Details →
10.0.7 06 Oct 2021 none non-standard — Details →
11.0.6 29 Jun 2021 none non-standard — Details →
10.0.6 29 Jun 2021 none non-standard — Details →
11.0.5 11 Jun 2021 none non-standard — Details →
10.0.5 11 Jun 2021 none non-standard — Details →
11.0.4 04 Jun 2021 none non-standard — Details →
10.0.4 04 Jun 2021 none non-standard — Details →
11.0.3 20 May 2021 none non-standard — Details →
10.0.3 20 May 2021 none non-standard — Details →
11.0.2 26 Mar 2021 none non-standard — Details →
10.0.2 26 Mar 2021 none non-standard — Details →
11.0.1 19 Feb 2021 none non-standard — Details →
10.0.1 19 Feb 2021 none non-standard — Details →
11.0.0 02 Dec 2020 none non-standard — Details →
10.0.0 02 Dec 2020 none non-standard — Details →
11.0.0.beta3 21 Oct 2020 none non-standard — Details →
10.0.0.beta3 21 Oct 2020 none non-standard — Details →
11.0.0.beta2 02 Oct 2020 none non-standard — Details →
10.0.0.beta2 02 Oct 2020 none non-standard — Details →
11.0.0.beta1 10 Jul 2020 none non-standard — Details →
10.0.0.beta1 10 Jul 2020 none non-standard — Details →
11.0.0-alpha0 30 May 2020 none non-standard — Details →
10.0.0.beta0 27 May 2020 none non-standard — Details →

All 62 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for org.eclipse.jetty.websocket:websocket-core-server

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About org.eclipse.jetty.websocket:websocket-core-server

Is org.eclipse.jetty.websocket:websocket-core-server safe to use?

Vulert has no vulnerabilities on record for org.eclipse.jetty.websocket:websocket-core-server in Maven at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is org.eclipse.jetty.websocket:websocket-core-server's Vulert package health score?

Vulert scores org.eclipse.jetty.websocket:websocket-core-server 84/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of org.eclipse.jetty.websocket:websocket-core-server affected?

No. 11.0.26, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of org.eclipse.jetty.websocket:websocket-core-server should I use?

11.0.26 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does org.eclipse.jetty.websocket:websocket-core-server have?

0 vulnerabilities are recorded for org.eclipse.jetty.websocket:websocket-core-server in the Maven ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.eclipse.jetty.websocket:websocket-core-server vulnerabilities disclosed?

0 vulnerabilities were recorded for org.eclipse.jetty.websocket:websocket-core-server in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of org.eclipse.jetty.websocket:websocket-core-server are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor org.eclipse.jetty.websocket:websocket-core-server for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.eclipse.jetty.websocket:websocket-core-server version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.