Security readout for executives and security teams
Plain-English summary
CVE-2026-24009 affects docling-core, a Docling document-processing library. In specific conditions, unsafe YAML deserialization can allow remote code execution. Risk exists only when vulnerable docling-core versions use PyYAML before 5.4 and the application passes untrusted YAML into load_from_yaml(). The vendor fixed this in docling-core 2.48.4.
Executive priority
Prioritize remediation for internet-facing or partner-facing document workflows that accept YAML or user-supplied document data. Treat as high priority where the vulnerable method is reachable. Lower urgency may be reasonable where untrusted YAML is not processed, but dependency upgrades remain recommended.
Technical view
docling-core versions 2.21.0 through before 2.48.4 exposed PyYAML CVE-2020-14343 through docling_core.types.doc.DoclingDocument.load_from_yaml(). The issue is CWE-502 unsafe deserialization. The fix changes deserialization from yaml.FullLoader to yaml.SafeLoader. CVSS is 8.1 with network attack vector, no privileges or user interaction, but high attack complexity.
Likely exposure
Exposure is limited to applications using affected docling-core versions, PyYAML before 5.4, and untrusted YAML input to load_from_yaml(). Systems that do not process attacker-controlled YAML through this function are less likely exposed based on the advisory.
Exploitation context
The source bundle does not indicate active exploitation, and the CVE is not listed as KEV. Exploitation requires a vulnerable dependency combination and a reachable path where untrusted YAML is parsed by the affected method. Attack complexity is rated high.
Researcher notes
The advisory describes a conditional RCE exposure from unsafe PyYAML usage, not a broad default compromise of all docling-core installations. Focus triage on dependency versions and data-flow reachability to load_from_yaml(). The published fix is the loader change in commit 3e8d628 and release 2.48.4.
Mitigation direction
- Upgrade docling-core to version 2.48.4 or later.
- If upgrade is delayed, ensure PyYAML is version 5.4 or greater.
- Avoid passing untrusted YAML to load_from_yaml() until remediated.
- Review vendor advisory and release notes for environment-specific guidance.
Validation and detection
- Inventory applications using docling-core versions 2.21.0 to before 2.48.4.
- Check installed PyYAML versions in those application environments.
- Review code paths for load_from_yaml() handling untrusted YAML.
- Confirm docling-core 2.48.4 or later is deployed after remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-24009 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/docling-project/docling-core/security/advisories/GHSA-vqxf-v2gg-x3hcCVE reference · x_refsource_CONFIRM
- https://github.com/docling-project/docling-core/issues/482CVE reference · x_refsource_MISC
- https://github.com/docling-project/docling-core/commit/3e8d628eeeae50f0f8f239c8c7fea773d065d80cCVE reference · x_refsource_MISC
- https://github.com/advisories/GHSA-8q59-q68h-6hv4CVE reference · x_refsource_MISC
- https://github.com/docling-project/docling-core/releases/tag/v2.48.4CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.