VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

libspring-java: vulnerability history, versions and safety

libspring-java is a package in the Debian ecosystem. Vulert records 120 vulnerabilities for it across 4 releases, from Jan 2014 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
120 vulnerabilities recorded U120
i
76 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
27 in the last 12 months

Most recent disclosure 27 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all libspring-java vulnerabilities

Vulert verdict on libspring-java i

Updated on 22 Oct 2026

Careful: 76 of the 120 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 120 vulnerabilities on record across 12 years, 27 in the last year.

What to do: Plan around the 76 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 120 over 12 years · 27 in the last year i
  • Latest disclosure 27 Aug 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 76 i

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 holds for libspring-java, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
4.3.30-4 U27 No Details →
4.3.30-3 U76 No Details →
4.3.30-2 U76 No Details →
4.3.30-1 U76 No Details →

Newest 4 of 4 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2014 12
  • 2015 2
  • 2016 4
  • 2017 6
  • 2018 14
  • 2020 6
  • 2021 2
  • 2022 12
  • 2023 6
  • 2024 22
  • 2025 7
  • 2026 27

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

03 Vulnerabilities

Recorded vulnerabilities for libspring-java

The 5 most severe of 120 vulnerabilities recorded for this package

Search all 120 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
Critical Stream Corruption Vulnerability in libspring-java Affects Multiple Debian Releases 9.8 critical No fix published 27 Aug 2026
Remote Code Execution Vulnerability in libspring-java 9.8 critical No fix published 01 Apr 2022
Remote Code Execution Vulnerability in Spring Framework (CVE-2018-1270) 9.8 critical 4.3.19-1 06 Apr 2018
Remote Code Execution Vulnerability in Pivotal Spring Framework (CVE-2016-1000027) 9.8 critical 4.2.7-1 02 Jan 2020
Reflected File Download Vulnerability in libspring-java: CVE-2015-5211 9.6 critical 4.1.9-1 25 May 2017

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 libspring-java

Is libspring-java safe to use?

Vulert records 120 vulnerabilities for libspring-java in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 120 not yet rated. 76 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does libspring-java have?

120 vulnerabilities are recorded for libspring-java in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 120 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new libspring-java vulnerabilities disclosed?

27 vulnerabilities were recorded for libspring-java in the last 12 months, and the oldest entry in this database dates to 23 Jan 2014. 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 libspring-java 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 libspring-java for upcoming vulnerabilities?

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