Is this vulnerability remotely exploitable?

It can be, depending on how the application exposes `DoclingDocument.load_from_yaml()`. If YAML content can be supplied over a network interface (such as HTTP APIs, message queues, or remote file uploads), an attacker may be able to exploit the issue remotely by providing crafted YAML that reaches the vulnerable deserialization call.

What level of access does an attacker need to exploit this?

The attacker needs the ability to control or influence the YAML data passed to `DoclingDocument.load_from_yaml()` in an environment using a vulnerable PyYAML and affected docling-core versions. This can be as simple as uploading a document, providing a configuration file, or sending an API request if those inputs are directly or indirectly fed into the method without strong validation.

What is the safest general fix pattern?

The robust fix pattern is to ensure that all YAML parsing of untrusted data uses restricted loaders (such as `SafeLoader` or equivalents) that cannot instantiate arbitrary objects, combined with schema validation of parsed content. Additionally, reviewing the codebase for other deserialization points and standardizing on secure deserialization practices across the application helps avoid similar issues.

Severity:

HIGH RISK

(8.1)

Unsafe YAML Deserialization (CWE-502) in Docling Core DoclingDocument.load_from_yaml

CVE-2026-24009

Published:

Jan 22, 2026

Status:

Awaiting Analysis

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-306

CRITICAL RISK

CRITICAL

(9.8)

Missing Authentication for Forgot-Password Email Change API (CWE-306)

Account Takeover / Loss of Account Control

February 17, 2026

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in node-sonos-http-api TTS Provider for macOS

Remote Code Execution on the Server Host

February 17, 2026

Vulnerability Type

Category:

Unsafe Deserialization

CWE:

CWE-502

Impact:

Remote Code Execution

Severity:

HIGH RISK

(8.1)

CVSS Version:

3.1

Vulnerability Type

Category:

Unsafe Deserialization

CWE:

CWE-502

Impact:

Remote Code Execution

Severity:

HIGH RISK

(8.1)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Unsafe YAML Deserialization (CWE-502) in Docling Core DoclingDocument.load_from_yaml

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

CRITICAL RISK

CRITICAL

(9.8)

Missing Authentication for Forgot-Password Email Change API (CWE-306)

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in node-sonos-http-api TTS Provider for macOS

Vulnerability Type

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare