# docling-core (PyPI) vulnerabilities

3 known vulnerabilities (3 high), with the versions each affects and the releases that fix them.

## At a glance

- Latest release: 3.0.0 (Jan 29, 2025): no advisory affects it
- Newest unaffected release: 2.106.0 (Nov 4, 2026)
- Weekly downloads: 1.5M
- Dependents: 14
- Releases: 195 since 0.0.1 (Jul 17, 2024)
- Registry: https://pypi.org/project/docling-core/
- Releases read: Nov 8, 2026

## Version timeline

Affected versions per advisory, in version order:

- CVE-2026-44023: 1.5.0 to 2.74.0 (2.74.1 is outside it)
- CVE-2026-44019: 2.5.0 to 2.74.0 (2.74.1 is outside it)
- CVE-2026-24009: 2.21.0 to 2.48.3 (2.48.4 is outside it)

## Advisories (3)

### [CVE-2026-44023](https://cve.now/CVE-2026-44023): Docling Core has unsafe remote filename resolution

- Severity: High 8.6
- Published: Jul 16, 2026
- Affected: from 1.5.0, fixed in 2.74.1.
- Fixed in 2.74.1 (released Apr 22, 2026, 85 days before disclosure).
- The latest release, 3.0.0, is not affected.

### [CVE-2026-44019](https://cve.now/CVE-2026-44019): Docling Core has insufficient validation of image reference URIs

- Severity: High 8.1
- Published: Jul 16, 2026
- Affected: from 2.5.0, fixed in 2.74.1.
- Fixed in 2.74.1 (released Apr 22, 2026, 85 days before disclosure).
- The latest release, 3.0.0, is not affected.

### [CVE-2026-24009](https://cve.now/CVE-2026-24009): Docling Core vulnerable to Remote Code Execution via unsafe PyYAML usage

- Severity: High 8.1
- Published: Jan 22, 2026
- Affected: from 2.21.0, fixed in 2.48.4.
- Fixed in 2.48.4 (released Oct 1, 2025, 113 days before disclosure).
- The latest release, 3.0.0, is not affected.

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/packages/pypi/docling-core
Site guide for agents: https://cve.now/llms.txt
Uses NVD data; not endorsed by NVD.