VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.apache.sanselan:sanselan: vulnerability history, versions and safety

org.apache.sanselan:sanselan is a package in the Maven ecosystem. Vulert records 2 vulnerabilities for it across 1 release, first recorded in May 2019. 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 H2
i
2 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 org.apache.sanselan:sanselan vulnerabilities

Vulert verdict on org.apache.sanselan:sanselan 0.97-incubator i

Updated on 23 Oct 2026

Careful: 0.97-incubator has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Widely used
  • Community Not enough data

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 0.97-incubator — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 14 May 2019 i
  • Highest CVSS 7.5 i
  • With no published fix 2 i
  • Depended on by 232 packages i
  • Last release 212 months ago 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.apache.sanselan:sanselan, 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
0.97-incubator 20 Feb 2009 H2 Apache-2.0 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 2

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

03 Vulnerabilities

Recorded vulnerabilities for org.apache.sanselan:sanselan

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-17202: Infinite Loop in Apache Sanselan 7.5 high No fix published 14 May 2019
CVE-2018-17201: Improper Input Validation in Apache Sanselan 7.5 high No fix published 14 May 2019

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.apache.sanselan:sanselan

Is org.apache.sanselan:sanselan safe to use?

Vulert records 2 vulnerabilities for org.apache.sanselan:sanselan in Maven: 0 critical, 2 high, 0 medium and 0 low. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is org.apache.sanselan:sanselan's Vulert package health score?

Vulert scores org.apache.sanselan:sanselan 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of org.apache.sanselan:sanselan affected?

Yes. 0.97-incubator, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of org.apache.sanselan:sanselan should I use?

0.97-incubator 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.apache.sanselan:sanselan have?

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

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

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