Vulnerability Database · PyPI · Package report

docling: vulnerability history, versions and safety

docling is a package in the PyPI ecosystem. Vulert records 36 vulnerabilities for it across 120 releases, from May 2026 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
36 vulnerabilities recorded H7 M10 L1 U18
i
4 with no fix published

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

See the unfixed vulnerabilities →
i
36 in the last 12 months

Most recent disclosure 15 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on docling 2.142.0 i

Updated on 23 Oct 2026

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

Package health score 60/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

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 2.142.0 — affected i
  • Vulnerabilities on record 36 over 1 year · 36 in the last year i
  • Latest disclosure 15 Oct 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 4 i
  • Stars 69,248 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, 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 docling, 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.142.0 22 Oct 2026 H2 U2 MIT No Details →
2.141.0 20 Oct 2026 H2 U2 MIT No Details →
2.140.0 16 Oct 2026 H2 U2 MIT No Details →
2.139.0 14 Oct 2026 H2 U2 MIT No Details →
2.138.0 12 Oct 2026 H2 U2 MIT No Details →
2.137.0 09 Oct 2026 H2 U2 MIT No Details →
2.136.0 09 Oct 2026 H2 U2 MIT No Details →
2.135.0 07 Oct 2026 H2 U2 MIT No Details →
2.134.0 06 Oct 2026 H2 U2 MIT No Details →
2.133.0 03 Oct 2026 H2 U2 MIT No Details →
2.132.0 01 Oct 2026 H2 U2 MIT No Details →
2.131.0 29 Sep 2026 H1 M1 L1 U3 MIT Yes Details →
2.130.0 22 Sep 2026 H1 M6 L1 U8 MIT Yes Details →
2.129.0 18 Sep 2026 H1 M6 L1 U8 MIT Yes Details →
2.128.0 16 Sep 2026 H1 M6 L1 U8 MIT Yes Details →
2.127.0 14 Sep 2026 H1 M6 L1 U8 MIT Yes Details →
2.126.0 04 Sep 2026 H1 M6 L1 U8 MIT Yes Details →
2.125.0 03 Sep 2026 H1 M6 L1 U8 MIT Yes Details →
2.124.0 31 Aug 2026 H1 M6 L1 U8 MIT Yes Details →
2.123.1 28 Aug 2026 H1 M6 L1 U8 MIT Yes Details →
2.123.0 26 Aug 2026 H1 M6 L1 U8 MIT Yes Details →
2.122.0 25 Aug 2026 H1 M6 L1 U8 MIT Yes Details →
2.121.0 20 Aug 2026 H1 M6 L1 U8 MIT Yes Details →
2.120.3 18 Aug 2026 H1 M6 L1 U8 MIT Yes Details →
2.120.2 17 Aug 2026 H1 M7 L1 U9 MIT Yes Details →
2.120.1 14 Aug 2026 H1 M7 L1 U9 MIT Yes Details →
2.119.0 10 Aug 2026 H1 M7 L1 U9 MIT Yes Details →
2.118.1 07 Aug 2026 H1 M7 L1 U9 MIT Yes Details →
2.118.0 03 Aug 2026 H1 M8 L1 U10 MIT Yes Details →
2.117.0 30 Jul 2026 H1 M8 L1 U10 MIT Yes Details →
2.116.0 29 Jul 2026 H1 M8 L1 U10 MIT Yes Details →
2.115.0 23 Jul 2026 H1 M8 L1 U10 MIT Yes Details →
2.114.0 20 Jul 2026 H1 M8 L1 U10 MIT Yes Details →
2.113.0 14 Jul 2026 H1 M8 L1 U10 MIT Yes Details →
2.112.0 11 Jul 2026 H1 M8 L1 U10 MIT Yes Details →
2.111.0 08 Jul 2026 H1 M8 L1 U10 MIT Yes Details →
2.110.0 04 Jul 2026 H1 M8 L1 U10 MIT Yes Details →
2.109.0 03 Jul 2026 H1 M8 L1 U10 MIT Yes Details →
2.108.0 01 Jul 2026 H1 M8 L1 U10 MIT Yes Details →
2.107.0 24 Jun 2026 H1 M8 L1 U10 MIT Yes Details →
2.106.0 23 Jun 2026 H1 M7 L1 U9 MIT Yes Details →
2.105.0 22 Jun 2026 H1 M7 L1 U9 MIT Yes Details →
2.104.0 19 Jun 2026 H1 M7 L1 U9 MIT Yes Details →
2.103.0 17 Jun 2026 H1 M7 L1 U9 MIT Yes Details →
2.102.2 15 Jun 2026 H1 M7 L1 U9 MIT Yes Details →
2.102.1 12 Jun 2026 H1 M7 L1 U9 MIT Yes Details →
2.102.0 12 Jun 2026 H1 M7 L1 U9 MIT Yes Details →
2.101.0 10 Jun 2026 H1 M7 L1 U9 MIT Yes Details →
2.100.0 09 Jun 2026 H1 M7 L1 U9 MIT Yes Details →
2.99.0 08 Jun 2026 H1 M7 L1 U9 MIT Yes Details →
2.98.0 08 Jun 2026 H1 M7 L1 U9 MIT Yes Details →
2.97.0 03 Jun 2026 H1 M7 L1 U9 MIT Yes Details →
2.96.1 01 Jun 2026 H1 M7 L1 U9 MIT Yes Details →
2.96.0 28 May 2026 H1 M7 L1 U9 MIT Yes Details →
2.95.0 21 May 2026 H1 M7 L1 U9 MIT Yes Details →
2.94.0 18 May 2026 H1 M7 U8 MIT Yes Details →
2.93.0 07 May 2026 H1 M7 U8 MIT Yes Details →
2.92.0 29 Apr 2026 H1 M7 U8 MIT Yes Details →
2.91.0 23 Apr 2026 H1 M7 U8 MIT Yes Details →
2.90.0 17 Apr 2026 H3 M8 U11 MIT Yes Details →
2.89.0 16 Apr 2026 H3 M8 U11 MIT Yes Details →
2.88.0 13 Apr 2026 H3 M8 U11 MIT Yes Details →
2.87.0 13 Apr 2026 H3 M8 U11 MIT Yes Details →
2.86.0 10 Apr 2026 H3 M8 U11 MIT Yes Details →
2.85.0 07 Apr 2026 H3 M8 U11 MIT Yes Details →
2.84.0 01 Apr 2026 H3 M8 U11 MIT Yes Details →
2.83.0 31 Mar 2026 H3 M8 U11 MIT Yes Details →
2.82.0 25 Mar 2026 H3 M8 U10 MIT Yes Details →
2.81.0 20 Mar 2026 H2 M7 U8 MIT Yes Details →
2.80.0 14 Mar 2026 H2 M7 U8 MIT Yes Details →
2.79.0 12 Mar 2026 H2 M7 U8 MIT Yes Details →
2.78.0 10 Mar 2026 H2 M7 U8 MIT Yes Details →
2.77.0 06 Mar 2026 H2 M7 U8 MIT Yes Details →
2.76.0 02 Mar 2026 H2 M7 U8 MIT Yes Details →
2.75.0 24 Feb 2026 H2 M7 U8 MIT Yes Details →
2.74.0 17 Feb 2026 H2 M7 U8 MIT Yes Details →
2.73.1 13 Feb 2026 H3 M7 U9 MIT Yes Details →
2.73.0 11 Feb 2026 H3 M7 U9 MIT Yes Details →
2.72.0 03 Feb 2026 H3 M6 U8 MIT Yes Details →
2.71.0 30 Jan 2026 H3 M6 U8 MIT Yes Details →
2.70.0 23 Jan 2026 H3 M6 U8 MIT Yes Details →
2.69.1 21 Jan 2026 H3 M6 U8 MIT Yes Details →
2.69.0 20 Jan 2026 H3 M6 U8 MIT Yes Details →
2.68.0 13 Jan 2026 H3 M6 U8 MIT Yes Details →
2.67.0 09 Jan 2026 H3 M6 U8 MIT Yes Details →
2.66.0 24 Dec 2025 H3 M6 U8 MIT Yes Details →
2.65.0 15 Dec 2025 H3 M6 U8 MIT Yes Details →
2.64.1 09 Dec 2025 H3 M6 U8 MIT Yes Details →
2.64.0 02 Dec 2025 H3 M6 U8 MIT Yes Details →
2.63.0 20 Nov 2025 H3 M6 U8 MIT Yes Details →
2.62.0 17 Nov 2025 H3 M6 U8 MIT Yes Details →
2.61.2 10 Nov 2025 H3 M6 U8 MIT Yes Details →
2.61.1 06 Nov 2025 H3 M6 U8 MIT Yes Details →
2.61.0 06 Nov 2025 H5 M6 U10 MIT No Details →
2.60.1 04 Nov 2025 H5 M6 U10 MIT No Details →
2.60.0 31 Oct 2025 H5 M6 U10 MIT No Details →
2.59.0 30 Oct 2025 H5 M6 U10 MIT No Details →
2.58.0 22 Oct 2025 H5 M6 U10 MIT No Details →
2.57.0 15 Oct 2025 H5 M6 U10 MIT No Details →
2.56.1 13 Oct 2025 H5 M6 U10 MIT No Details →
2.56.0 13 Oct 2025 H5 M6 U10 — No Details →
2.55.1 03 Oct 2025 H5 M6 U10 — No Details →
2.55.0 30 Sep 2025 H5 M6 U10 — No Details →
2.54.0 22 Sep 2025 H5 M6 U10 — No Details →
2.53.0 17 Sep 2025 H5 M6 U10 — No Details →
2.52.0 11 Sep 2025 H5 M6 U10 — No Details →
2.51.0 05 Sep 2025 H5 M6 U10 — No Details →
2.50.0 03 Sep 2025 H5 M6 U10 — No Details →
2.49.0 01 Sep 2025 H5 M6 U10 — No Details →
2.48.0 26 Aug 2025 H5 M6 U10 — No Details →
2.47.1 23 Aug 2025 H5 M6 U10 — No Details →
2.47.0 22 Aug 2025 H5 M6 U10 — No Details →
2.46.0 20 Aug 2025 H5 M6 U10 — No Details →
2.45.0 18 Aug 2025 H5 M6 U10 — No Details →
2.44.0 12 Aug 2025 H5 M3 U8 — No Details →
2.43.0 28 Jul 2025 H5 M3 U8 — No Details →
2.42.2 24 Jul 2025 H5 M3 U8 — No Details →
2.42.1 22 Jul 2025 H5 M3 U8 — No Details →
2.42.0 18 Jul 2025 H5 M3 U8 — No Details →
2.41.0 10 Jul 2025 H5 M3 U8 — No Details →

The newest 120 of 230 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 36

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 36 of the 36 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 docling

Is docling safe to use?

Vulert records 36 vulnerabilities for docling in PyPI: 0 critical, 7 high, 10 medium and 1 low, plus 18 not yet rated. 4 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is docling's Vulert package health score?

Vulert scores docling 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 docling affected?

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

How many vulnerabilities does docling have?

36 vulnerabilities are recorded for docling in the PyPI ecosystem: 0 critical, 7 high, 10 medium and 1 low, plus 18 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 docling vulnerabilities disclosed?

36 vulnerabilities were recorded for docling in the last 12 months, and the oldest entry in this database dates to 11 May 2026. 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 docling 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 docling for upcoming vulnerabilities?

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