CVE-2026-108749 docling-project CVE debrief

Who should care

Defenders responsible for docling-serve deployments, especially those using affected versions, should assess their exposure and consider implementing compensating controls to prevent unauthorized access to memory telemetry.

Why it matters

CVE-2026-108749 is a missing authentication vulnerability in docling-serve that allows unauthenticated access to memory management endpoints, potentially leading to unauthorized access to sensitive information and disruption of service.

• Potential unauthorized access to sensitive memory telemetry.
• Possible disruption of service due to forced heap enumeration.
• Need for verification of affected versions in environment.
• Potential for attackers to gather information about system memory usage.

Technical summary

The docling-serve application, versions 1.14.0 through 1.36.0, contains a missing authentication vulnerability. Specifically, the /v1/memory/stats and /v1/memory/counts endpoints omit the require_auth dependency, allowing unauthenticated attackers to access process and cgroup memory telemetry, object type histograms, and force repeated gc.collect() heap enumeration. This could lead to unauthorized access to sensitive information and disruption of service. Defenders should prioritize verifying the presence of this vulnerability in their environments, especially if using affected versions of docling-serve.

Defensive priority

Defenders should prioritize verifying the presence of this vulnerability in their environments, especially if using affected versions of docling-serve. They should also assess the potential impact of unauthorized access to memory telemetry and consider implementing compensating controls.

Recommended defensive actions

• Verify the presence of docling-serve in your environment and check if it is within the affected version range.
• Assess the potential impact of unauthorized access to memory telemetry and consider implementing compensating controls.
• Monitor for any suspicious activity related to the /v1/memory/stats and /v1/memory/counts endpoints.
• Consider updating to a version of docling-serve that addresses this vulnerability, if available.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and source item provide details about the vulnerability, including its description, affected versions, and references to additional information. However, there is limited information about potential exploits or impacts.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.