VulertSecurity VulertSecurity

Vulnerability Database · Ubuntu · Package report

libspring-java: vulnerability history, versions and safety

libspring-java is a package in the Ubuntu ecosystem. Vulert records 47 vulnerabilities for it across 9 releases, from Nov 2014 to Sep 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
47 vulnerabilities recorded U47
i
40 with no fix published

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

See the unfixed vulnerabilities →
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 libspring-java vulnerabilities

Vulert verdict on libspring-java i

Updated on 22 Oct 2026

Careful: 40 of the 47 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 47 vulnerabilities on record across 10 years, none in the last year.

What to do: Plan around the 40 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 47 over 10 years · 0 in the last year i
  • Latest disclosure 16 Sep 2025 i
  • Highest CVSS 9.8 i
  • With no published fix 40 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.

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2014 1
  • 2015 1
  • 2016 2
  • 2017 3
  • 2018 5
  • 2020 4
  • 2021 2
  • 2022 9
  • 2023 4
  • 2024 11
  • 2025 5

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

03 Vulnerabilities

Recorded vulnerabilities for libspring-java

The 5 most severe of 47 vulnerabilities recorded for this package

Search all 47 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Authorization Bypass Vulnerability in libspring-java Package 9.8 critical No fix published 31 Oct 2022
Authorization Bypass Vulnerability in libspring-java Package 9.8 critical No fix published 19 May 2022
Critical Remote Code Execution Vulnerability in libspring-java Package 9.8 critical No fix published 02 Jan 2020
Critical Reflected File Download Vulnerability in libspring-java Package 9.6 critical 3.0.6.RELEASE-13ubuntu0.1~esm2 25 May 2017
Critical XXE Vulnerability in libspring-java Package: CVE-2014-0225 8.8 high 3.0.6.RELEASE-13ubuntu0.1~esm1 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 47 vulnerabilities for libspring-java in Ubuntu: 0 critical, 0 high, 0 medium and 0 low, plus 47 not yet rated. 40 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does libspring-java have?

47 vulnerabilities are recorded for libspring-java in the Ubuntu ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 47 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?

0 vulnerabilities were recorded for libspring-java in the last 12 months, and the oldest entry in this database dates to 20 Nov 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.