VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.opensaml:opensaml: vulnerability history, versions and safety

org.opensaml:opensaml is a package in the Maven ecosystem. Vulert records 3 vulnerabilities for it across 12 releases, first recorded in May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded M3
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.opensaml:opensaml vulnerabilities

Vulert verdict on org.opensaml:opensaml 2.6.4 i

Updated on 23 Oct 2026

Action needed: 2.6.4 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 78/100
  • Security No known security issues
  • Maintenance Slowing
  • Popularity Widely used
  • Community Not enough data

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 2.6.4 — affected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 17 May 2022 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 147 packages i
  • Last release 140 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 org.opensaml:opensaml, 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
2.6.4 11 Feb 2015 M1 Apache-2.0 Yes Details →
2.6.1 18 Feb 2014 M1 Apache-2.0 Yes Details →
2.6.0 19 Aug 2013 M2 Apache-2.0 Yes Details →
2.5.3 29 Mar 2013 M2 Apache-2.0 Yes Details →
2.5.1-1 12 Sep 2011 M2 Apache-2.0 Yes Details →
2.5.1 20 Aug 2011 M2 Apache-2.0 Yes Details →
2.4.1 16 Mar 2011 M3 Apache-2.0 Yes Details →
2.2.3 17 Jul 2009 M2 Apache-2.0 Yes Details →
1.1 28 Oct 2008 M2 Apache-2.0 Yes Details →
2.2.1 20 Oct 2008 M2 Apache-2.0 Yes Details →
2.2.0 09 Oct 2008 M2 Apache-2.0 Yes Details →
2.1.0 24 Sep 2008 M2 Apache-2.0 Yes Details →

All 12 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 3

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

03 Vulnerabilities

Recorded vulnerabilities for org.opensaml:opensaml

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2015-1796: Improper Certificate Validation in Shibboleth Identity Provider and OpenSAML N/A medium 2.6.5 17 May 2022
CVE-2011-1411: Improper Authentication in OpenSAML N/A medium 2.4.3 17 May 2022
CVE-2013-6440: OpenSAML-Java XML External Entity (XXE) Vulnerability N/A medium 2.6.1 13 May 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 org.opensaml:opensaml

Is org.opensaml:opensaml safe to use?

Vulert records 3 vulnerabilities for org.opensaml:opensaml in Maven: 0 critical, 0 high, 3 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.opensaml:opensaml's Vulert package health score?

Vulert scores org.opensaml:opensaml 78/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.opensaml:opensaml affected?

Yes. 2.6.4, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of org.opensaml:opensaml should I use?

2.6.4 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.opensaml:opensaml have?

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

0 vulnerabilities were recorded for org.opensaml:opensaml in the last 12 months, and the oldest entry in this database dates to 13 May 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 org.opensaml:opensaml 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.opensaml:opensaml for upcoming vulnerabilities?

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