Vulnerability Database · Maven · Package report

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

org.jsoup:jsoup is a package in the Maven ecosystem. Vulert records 5 vulnerabilities for it across 55 releases, from Aug 2021 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
5 vulnerabilities recorded H2 M3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 20 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on org.jsoup:jsoup 1.23.2 i

Updated on 23 Oct 2026

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

Package health score 83/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 1.23.2 — unaffected i
  • Vulnerabilities on record 5 over 4 years · 2 in the last year i
  • Latest disclosure 20 Aug 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 1,932 packages i
  • Stars 11,411 i
  • OpenSSF scorecard 5/10 i
  • Last release 1 month ago i
  • Licence non-standard 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.jsoup:jsoup, 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.23.2 26 Aug 2026 none non-standard — Details →
1.23.1 30 Jul 2026 H1 non-standard Yes Details →
1.22.2 20 Apr 2026 H1 M1 non-standard Yes Details →
1.22.1 01 Jan 2026 H1 M1 non-standard Yes Details →
1.21.2 24 Aug 2025 H1 M1 non-standard Yes Details →
1.21.1 23 Jun 2025 H1 M1 non-standard Yes Details →
1.20.1 29 Apr 2025 H1 M1 non-standard Yes Details →
1.19.1 04 Mar 2025 H1 M1 non-standard Yes Details →
1.18.3 01 Dec 2024 H1 M1 non-standard Yes Details →
1.18.2 27 Nov 2024 H1 M1 non-standard Yes Details →
1.18.1 10 Jul 2024 H1 M1 non-standard Yes Details →
1.17.2 29 Dec 2023 H1 M1 non-standard Yes Details →
1.17.1 27 Nov 2023 H1 M1 non-standard Yes Details →
1.16.2 20 Oct 2023 H1 M1 non-standard Yes Details →
1.16.1 29 Apr 2023 H1 M1 non-standard Yes Details →
1.15.4 18 Feb 2023 H1 M1 non-standard Yes Details →
1.15.3 24 Aug 2022 H1 M1 non-standard Yes Details →
1.15.2 04 Jul 2022 H1 M2 non-standard Yes Details →
1.15.1 15 May 2022 H1 M2 non-standard Yes Details →
1.14.3 30 Sep 2021 H1 M2 non-standard Yes Details →
1.14.2 15 Aug 2021 H1 M1 non-standard Yes Details →
1.14.1 10 Jul 2021 H2 M1 non-standard Yes Details →
1.13.1 01 Mar 2020 H2 M1 non-standard Yes Details →
1.12.2 09 Feb 2020 H2 M1 non-standard Yes Details →
1.12.1 12 May 2019 H2 M1 non-standard Yes Details →
1.11.3 15 Apr 2018 H2 M1 non-standard Yes Details →
1.11.2 20 Nov 2017 H2 M1 non-standard Yes Details →
1.11.1 04 Nov 2017 H2 M1 non-standard Yes Details →
1.10.3 11 Jun 2017 H2 M1 non-standard Yes Details →
1.10.2 02 Jan 2017 H2 M1 non-standard Yes Details →
1.10.1 23 Oct 2016 H2 M1 non-standard Yes Details →
1.9.2 18 May 2016 H2 M1 non-standard Yes Details →
1.9.1 17 Apr 2016 H2 M1 non-standard Yes Details →
1.8.3 02 Aug 2015 H2 M1 non-standard Yes Details →
1.8.2 14 Apr 2015 H2 M2 non-standard Yes Details →
1.8.1 28 Sep 2014 H2 M2 non-standard Yes Details →
1.7.3 11 Nov 2013 H2 M2 non-standard Yes Details →
1.7.2 28 Jan 2013 H2 M2 non-standard Yes Details →
1.7.1 24 Sep 2012 H2 M2 non-standard Yes Details →
1.6.3 28 May 2012 H2 M2 non-standard Yes Details →
1.6.2 28 Mar 2012 H2 M2 non-standard Yes Details →
1.6.1 02 Jul 2011 H2 M2 non-standard Yes Details →
1.6.0 13 Jun 2011 H2 M2 non-standard Yes Details →
1.5.2 27 Feb 2011 H2 M1 non-standard Yes Details →
1.5.1 19 Feb 2011 H2 M1 non-standard Yes Details →
1.4.1 23 Nov 2010 H2 M1 non-standard Yes Details →
1.3.3 19 Sep 2010 H2 M1 non-standard Yes Details →
1.3.2 30 Aug 2010 H2 M1 non-standard Yes Details →
1.3.1 23 Aug 2010 H2 M1 non-standard Yes Details →
1.2.3 04 Aug 2010 H2 M1 non-standard Yes Details →
1.2.2 11 Jul 2010 H2 M1 non-standard Yes Details →
1.2.1 21 Jun 2010 H2 M1 non-standard Yes Details →
1.1.1 08 Jun 2010 H2 M1 non-standard Yes Details →
0.3.1 20 Feb 2010 H2 M1 non-standard Yes Details →
0.2.2 07 Feb 2010 H2 M1 non-standard Yes Details →
0.2.1b 05 Feb 2010 H2 M1 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2022 2
  • 2026 2

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

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.jsoup:jsoup

Is org.jsoup:jsoup safe to use?

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

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

No. 1.23.2, 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.jsoup:jsoup should I use?

1.23.2 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.jsoup:jsoup have?

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

2 vulnerabilities were recorded for org.jsoup:jsoup in the last 12 months, and the oldest entry in this database dates to 23 Aug 2021. 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.jsoup:jsoup 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.jsoup:jsoup for upcoming vulnerabilities?

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