Vulnerability Database · Maven · Package report

org.springframework:spring-websocket: vulnerability history, versions and safety

org.springframework:spring-websocket is a package in the Maven ecosystem. Vulert records 2 vulnerabilities for it across 20 releases, from Oct 2025 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 09 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on org.springframework:spring-websocket 7.1.0-RC1 i

Updated on 23 Oct 2026

Good news: 7.1.0-RC1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 89/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 7.1.0-RC1 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 1 in the last year i
  • Latest disclosure 09 Jun 2026 i
  • Highest CVSS 4.8 i
  • With no published fix 0 i
  • Stars 60,294 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 22 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.springframework:spring-websocket, 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
7.0.10 22 Oct 2026 none Apache-2.0 — Details →
7.1.0-RC1 22 Oct 2026 none Apache-2.0 — Details →
7.1.0-M2 24 Sep 2026 none Apache-2.0 — Details →
7.0.9 20 Aug 2026 none Apache-2.0 — Details →
7.1.0-M1 20 Aug 2026 none Apache-2.0 — Details →
7.0.8 08 Jun 2026 none Apache-2.0 — Details →
6.2.19 08 Jun 2026 none Apache-2.0 — Details →
6.2.18 17 Apr 2026 none Apache-2.0 — Details →
7.0.7 17 Apr 2026 M1 Apache-2.0 Yes Details →
7.0.6 13 Mar 2026 M1 Apache-2.0 Yes Details →
6.2.17 13 Mar 2026 none Apache-2.0 — Details →
7.0.5 18 Feb 2026 M1 Apache-2.0 Yes Details →
7.0.4 12 Feb 2026 M1 Apache-2.0 Yes Details →
6.2.16 12 Feb 2026 none Apache-2.0 — Details →
7.0.3 15 Jan 2026 M1 Apache-2.0 Yes Details →
7.0.2 11 Dec 2025 M1 Apache-2.0 Yes Details →
6.2.15 11 Dec 2025 none Apache-2.0 — Details →
7.0.1 20 Nov 2025 M1 Apache-2.0 Yes Details →
6.2.14 20 Nov 2025 none Apache-2.0 — Details →
7.0.0 13 Nov 2025 M1 Apache-2.0 Yes Details →
6.2.13 13 Nov 2025 none Apache-2.0 — Details →
7.0.0-RC3 31 Oct 2025 none Apache-2.0 — Details →
7.0.0-RC2 23 Oct 2025 none Apache-2.0 — Details →
7.0.0-RC1 16 Oct 2025 none Apache-2.0 — Details →
6.2.12 16 Oct 2025 none Apache-2.0 — Details →
7.0.0-M9 11 Sep 2025 none Apache-2.0 — Details →
6.2.11 11 Sep 2025 M1 Apache-2.0 Yes Details →
7.0.0-M8 14 Aug 2025 none Apache-2.0 — Details →
6.2.10 14 Aug 2025 M1 Apache-2.0 Yes Details →
7.0.0-M7 17 Jul 2025 none Apache-2.0 — Details →
6.2.9 17 Jul 2025 M1 Apache-2.0 Yes Details →
7.0.0-M6 12 Jun 2025 none Apache-2.0 — Details →
6.2.8 12 Jun 2025 M1 Apache-2.0 Yes Details →
6.1.21 12 Jun 2025 none Apache-2.0 — Details →
7.0.0-M5 15 May 2025 none Apache-2.0 — Details →
6.2.7 15 May 2025 M1 Apache-2.0 Yes Details →
6.1.20 15 May 2025 none Apache-2.0 — Details →
7.0.0-M4 17 Apr 2025 none Apache-2.0 — Details →
6.2.6 17 Apr 2025 M1 Apache-2.0 Yes Details →
6.1.19 17 Apr 2025 none Apache-2.0 — Details →
6.2.5 19 Mar 2025 M1 Apache-2.0 Yes Details →
7.0.0-M3 13 Mar 2025 none Apache-2.0 — Details →
6.2.4 13 Mar 2025 M1 Apache-2.0 Yes Details →
6.1.18 13 Mar 2025 none Apache-2.0 — Details →
7.0.0-M2 13 Feb 2025 none Apache-2.0 — Details →
6.2.3 13 Feb 2025 M1 Apache-2.0 Yes Details →
6.1.17 13 Feb 2025 none Apache-2.0 — Details →
7.0.0-M1 23 Jan 2025 none Apache-2.0 — Details →
6.2.2 16 Jan 2025 M1 Apache-2.0 Yes Details →
6.2.1 12 Dec 2024 M1 Apache-2.0 Yes Details →
6.1.16 12 Dec 2024 none Apache-2.0 — Details →
6.2.0 14 Nov 2024 M1 Apache-2.0 Yes Details →
6.1.15 14 Nov 2024 none Apache-2.0 — Details →
6.1.14 17 Oct 2024 none Apache-2.0 — Details →
6.1.13 12 Sep 2024 none Apache-2.0 — Details →
6.1.12 14 Aug 2024 none Apache-2.0 — Details →
6.0.23 14 Aug 2024 none Apache-2.0 — Details →
5.3.39 14 Aug 2024 none Apache-2.0 — Details →
5.3.38 14 Aug 2024 none Apache-2.0 — Details →
6.1.11 11 Jul 2024 none Apache-2.0 — Details →
6.1.10 19 Jun 2024 none Apache-2.0 — Details →
6.1.9 13 Jun 2024 none Apache-2.0 — Details →
6.0.22 13 Jun 2024 none Apache-2.0 — Details →
5.3.37 13 Jun 2024 none Apache-2.0 — Details →
6.1.8 22 May 2024 none Apache-2.0 — Details →
6.0.21 22 May 2024 none Apache-2.0 — Details →
5.3.36 22 May 2024 none Apache-2.0 — Details →
6.1.7 16 May 2024 none Apache-2.0 — Details →
6.0.20 16 May 2024 none Apache-2.0 — Details →
5.3.35 16 May 2024 none Apache-2.0 — Details →
6.1.6 11 Apr 2024 none Apache-2.0 — Details →
6.0.19 11 Apr 2024 none Apache-2.0 — Details →
5.3.34 11 Apr 2024 none Apache-2.0 — Details →
6.1.5 14 Mar 2024 none Apache-2.0 — Details →
6.0.18 14 Mar 2024 none Apache-2.0 — Details →
5.3.33 14 Mar 2024 none Apache-2.0 — Details →
5.3.32 15 Feb 2024 none Apache-2.0 — Details →
6.0.17 15 Feb 2024 none Apache-2.0 — Details →
6.1.4 15 Feb 2024 none Apache-2.0 — Details →
6.0.16 11 Jan 2024 none Apache-2.0 — Details →
6.1.3 11 Jan 2024 none Apache-2.0 — Details →
6.1.2 14 Dec 2023 none Apache-2.0 — Details →
6.0.15 14 Dec 2023 none Apache-2.0 — Details →
6.1.1 23 Nov 2023 none Apache-2.0 — Details →
6.1.0 16 Nov 2023 none Apache-2.0 — Details →
6.0.14 16 Nov 2023 none Apache-2.0 — Details →
5.3.31 16 Nov 2023 none Apache-2.0 — Details →
6.0.13 12 Oct 2023 none Apache-2.0 — Details →
6.0.12 14 Sep 2023 none Apache-2.0 — Details →
5.3.30 14 Sep 2023 none Apache-2.0 — Details →
6.0.11 13 Jul 2023 none Apache-2.0 — Details →
5.3.29 13 Jul 2023 none Apache-2.0 — Details →
5.2.25.RELEASE 13 Jul 2023 none Apache-2.0 — Details →
5.3.28 15 Jun 2023 none Apache-2.0 — Details →
6.0.10 15 Jun 2023 none Apache-2.0 — Details →
6.0.9 11 May 2023 none Apache-2.0 — Details →
5.2.24.RELEASE 13 Apr 2023 none Apache-2.0 — Details →
5.3.27 13 Apr 2023 none Apache-2.0 — Details →
6.0.8 13 Apr 2023 none Apache-2.0 — Details →
5.2.23.RELEASE 20 Mar 2023 none Apache-2.0 — Details →
5.3.26 20 Mar 2023 none — — Details →
6.0.7 20 Mar 2023 none — — Details →
6.0.6 02 Mar 2023 none — — Details →
6.0.5 15 Feb 2023 none — — Details →
6.0.4 11 Jan 2023 none — — Details →
5.3.25 11 Jan 2023 none — — Details →
6.0.3 15 Dec 2022 none — — Details →
6.0.2 24 Nov 2022 none — — Details →
6.0.1 23 Nov 2022 none — — Details →
6.0.0 16 Nov 2022 none — — Details →
5.3.24 16 Nov 2022 none — — Details →
5.3.23 15 Sep 2022 none — — Details →
5.3.22 14 Jul 2022 none — — Details →
5.3.21 15 Jun 2022 none — — Details →
5.2.22.RELEASE 11 May 2022 none — — Details →
5.3.20 11 May 2022 none — — Details →
5.2.21.RELEASE 13 Apr 2022 none — — Details →
5.3.19 13 Apr 2022 none — — Details →
5.2.20.RELEASE 31 Mar 2022 none — — Details →
5.3.18 31 Mar 2022 none — — Details →

The newest 120 of 261 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for org.springframework:spring-websocket

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →

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.springframework:spring-websocket

Is org.springframework:spring-websocket safe to use?

Vulert records 2 vulnerabilities for org.springframework:spring-websocket in Maven: 0 critical, 0 high, 2 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is org.springframework:spring-websocket's Vulert package health score?

Vulert scores org.springframework:spring-websocket 89/100, which reads as healthy. 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.springframework:spring-websocket affected?

No. 7.1.0-RC1, 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.

How many vulnerabilities does org.springframework:spring-websocket have?

2 vulnerabilities are recorded for org.springframework:spring-websocket in the Maven ecosystem: 0 critical, 0 high, 2 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.springframework:spring-websocket vulnerabilities disclosed?

1 vulnerability was recorded for org.springframework:spring-websocket in the last 12 months, and the oldest entry in this database dates to 16 Oct 2025. 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.springframework:spring-websocket 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.springframework:spring-websocket for upcoming vulnerabilities?

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