VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.eclipse.parsson:parsson: vulnerability history, versions and safety

org.eclipse.parsson:parsson is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 3 releases, first recorded in Jul 2024. 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 C1
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.eclipse.parsson:parsson vulnerabilities

Vulert verdict on org.eclipse.parsson:parsson 1.1.9 i

Updated on 23 Oct 2026

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

Package health score 71/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 1.1.9 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 17 Jul 2024 i
  • Highest CVSS 8.6 i
  • With no published fix 0 i
  • Depended on by 4,072 packages i
  • Stars 17 i
  • OpenSSF scorecard 3/10 i
  • Last release 4 months ago i
  • Licence non-standard 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.eclipse.parsson:parsson, 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
1.1.9 26 May 2026 none non-standard — Details →
1.1.8 26 May 2026 none non-standard — Details →
1.1.7 07 Jun 2024 none non-standard — Details →
1.1.6 27 Feb 2024 none non-standard — Details →
1.1.5 20 Oct 2023 none non-standard — Details →
1.0.5 04 Aug 2023 none non-standard — Details →
1.1.4 04 Aug 2023 none non-standard — Details →
1.0.4 13 Jul 2023 none non-standard — Details →
1.1.3 13 Jul 2023 none non-standard — Details →
1.1.2 11 May 2023 C1 non-standard Yes Details →
1.0.3 03 May 2023 none non-standard — Details →
1.1.1 21 Jul 2022 C1 non-standard Yes Details →
1.0.2 29 Jun 2022 none non-standard — Details →
1.0.1 17 Jun 2022 none non-standard — Details →
1.1.0 21 Jan 2022 C1 non-standard Yes Details →
1.0.0 11 Jun 2021 none non-standard — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 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 org.eclipse.parsson:parsson

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-7272: Eclipse Parsson Stack Overflow Vulnerability 8.6 critical 1.1.3 17 Jul 2024

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.eclipse.parsson:parsson

Is org.eclipse.parsson:parsson safe to use?

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

Vulert scores org.eclipse.parsson:parsson 71/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.eclipse.parsson:parsson affected?

No. 1.1.9, 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 org.eclipse.parsson:parsson should I use?

1.1.9 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.eclipse.parsson:parsson have?

1 vulnerability is recorded for org.eclipse.parsson:parsson in the Maven ecosystem: 1 critical, 0 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.eclipse.parsson:parsson vulnerabilities disclosed?

0 vulnerabilities were recorded for org.eclipse.parsson:parsson in the last 12 months, and the oldest entry in this database dates to 17 Jul 2024. 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.eclipse.parsson:parsson 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.eclipse.parsson:parsson for upcoming vulnerabilities?

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