VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

com.twitter:twitter-server_2.12: vulnerability history, versions and safety

com.twitter:twitter-server_2.12 is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 47 releases, first recorded in Feb 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
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 com.twitter:twitter-server_2.12 vulnerabilities

Vulert verdict on com.twitter:twitter-server_2.12 24.2.0 i

Updated on 23 Oct 2026

Good news: 24.2.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 79/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Not enough data

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

  • Current release 24.2.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 09 Feb 2022 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Depended on by 13 packages i
  • Last release 29 months ago i
  • Licence Apache-2.0 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 com.twitter:twitter-server_2.12, 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
24.2.0 02 May 2024 none Apache-2.0 — Details →
23.11.0 02 Nov 2023 none Apache-2.0 — Details →
22.12.0 26 Dec 2022 none Apache-2.0 — Details →
22.7.0 28 Jul 2022 none Apache-2.0 — Details →
22.4.0 19 Apr 2022 none Apache-2.0 — Details →
22.3.0 29 Mar 2022 none Apache-2.0 — Details →
22.2.0 25 Feb 2022 none Apache-2.0 — Details →
22.1.0 13 Jan 2022 none Apache-2.0 — Details →
21.12.0 16 Dec 2021 none Apache-2.0 — Details →
21.11.0 23 Nov 2021 none Apache-2.0 — Details →
21.10.0 29 Oct 2021 none Apache-2.0 — Details →
21.9.0 30 Sep 2021 none Apache-2.0 — Details →
21.8.0 13 Aug 2021 none Apache-2.0 — Details →
21.6.0 22 Jun 2021 none Apache-2.0 — Details →
21.5.0 29 May 2021 none Apache-2.0 — Details →
21.4.0 27 Apr 2021 none Apache-2.0 — Details →
21.3.0 29 Mar 2021 none Apache-2.0 — Details →
21.2.0 11 Feb 2021 none Apache-2.0 — Details →
21.1.0 14 Jan 2021 none Apache-2.0 — Details →
20.12.0 10 Dec 2020 none Apache-2.0 — Details →
20.10.0 27 Oct 2020 M1 Apache-2.0 Yes Details →
20.9.0 22 Sep 2020 M1 Apache-2.0 Yes Details →
20.8.1 25 Aug 2020 M1 Apache-2.0 Yes Details →
20.8.0 11 Aug 2020 M1 Apache-2.0 Yes Details →
20.7.0 21 Jul 2020 M1 Apache-2.0 Yes Details →
20.6.0 24 Jun 2020 M1 Apache-2.0 Yes Details →
20.5.0 26 May 2020 M1 Apache-2.0 Yes Details →
20.4.1 26 Apr 2020 M1 Apache-2.0 Yes Details →
20.4.0 02 Apr 2020 M1 Apache-2.0 Yes Details →
20.3.0 08 Mar 2020 M1 Apache-2.0 Yes Details →
20.1.0 29 Jan 2020 M1 Apache-2.0 Yes Details →
19.12.0 13 Dec 2019 M1 Apache-2.0 Yes Details →
19.11.0 06 Nov 2019 M1 Apache-2.0 Yes Details →
19.10.0 09 Oct 2019 M1 Apache-2.0 Yes Details →
19.9.0 10 Sep 2019 M1 Apache-2.0 Yes Details →
19.8.0 06 Aug 2019 M1 Apache-2.0 Yes Details →
19.7.0 17 Jul 2019 M1 Apache-2.0 Yes Details →
19.6.0 19 Jun 2019 M1 Apache-2.0 Yes Details →
19.5.1 21 May 2019 M1 Apache-2.0 Yes Details →
19.5.0 17 May 2019 M1 Apache-2.0 Yes Details →
19.4.0 18 Apr 2019 M1 Apache-2.0 Yes Details →
19.3.0 13 Mar 2019 M1 Apache-2.0 Yes Details →
19.2.0 21 Feb 2019 M1 Apache-2.0 Yes Details →
19.1.0 09 Jan 2019 M1 Apache-2.0 Yes Details →
18.12.0 11 Dec 2018 M1 Apache-2.0 Yes Details →
18.11.0 12 Nov 2018 M1 Apache-2.0 Yes Details →
18.10.0 19 Oct 2018 M1 Apache-2.0 Yes Details →
18.9.1 26 Sep 2018 M1 Apache-2.0 Yes Details →
18.9.0 11 Sep 2018 M1 Apache-2.0 Yes Details →
18.8.0 06 Aug 2018 M1 Apache-2.0 Yes Details →
18.7.0 10 Jul 2018 M1 Apache-2.0 Yes Details →
18.6.0 15 Jun 2018 M1 Apache-2.0 Yes Details →
18.5.0 08 May 2018 M1 Apache-2.0 Yes Details →
18.4.0 10 Apr 2018 M1 Apache-2.0 Yes Details →
18.3.0 06 Mar 2018 M1 Apache-2.0 Yes Details →
18.2.0 06 Feb 2018 M1 Apache-2.0 Yes Details →
18.1.0 18 Jan 2018 M1 Apache-2.0 Yes Details →
17.12.0 09 Dec 2017 M1 Apache-2.0 Yes Details →
17.11.0 16 Nov 2017 M1 Apache-2.0 Yes Details →
17.10.0 27 Oct 2017 M1 Apache-2.0 Yes Details →
1.32.0 06 Sep 2017 M1 Apache-2.0 Yes Details →
1.31.0 17 Aug 2017 M1 Apache-2.0 Yes Details →
1.30.0 09 Jun 2017 M1 Apache-2.0 Yes Details →
1.29.0 21 Apr 2017 M1 Apache-2.0 Yes Details →
1.28.0 11 Mar 2017 M1 Apache-2.0 Yes Details →
1.27.0 04 Feb 2017 M1 Apache-2.0 Yes Details →
1.26.0 21 Dec 2016 M1 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for com.twitter:twitter-server_2.12

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-35774: Cross-site Scripting in TwitterServer 6.1 medium 20.12.0 09 Feb 2022

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 com.twitter:twitter-server_2.12

Is com.twitter:twitter-server_2.12 safe to use?

Vulert records 1 vulnerabilities for com.twitter:twitter-server_2.12 in Maven: 0 critical, 0 high, 1 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 com.twitter:twitter-server_2.12's Vulert package health score?

Vulert scores com.twitter:twitter-server_2.12 79/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 com.twitter:twitter-server_2.12 affected?

No. 24.2.0, 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 com.twitter:twitter-server_2.12 should I use?

24.2.0 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 com.twitter:twitter-server_2.12 have?

1 vulnerability is recorded for com.twitter:twitter-server_2.12 in the Maven ecosystem: 0 critical, 0 high, 1 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 com.twitter:twitter-server_2.12 vulnerabilities disclosed?

0 vulnerabilities were recorded for com.twitter:twitter-server_2.12 in the last 12 months, and the oldest entry in this database dates to 09 Feb 2022. 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 com.twitter:twitter-server_2.12 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 com.twitter:twitter-server_2.12 for upcoming vulnerabilities?

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