CVE-2026-108749: docling-serve 1.14.0 through 1.36.0 Missing Authentication via Memory Management Endpoints

Q: Who is exposed to this issue?

Instances running docling-serve versions 1.14.0 through 1.36.0 are exposed if attackers can reach the /v1/memory/stats or /v1/memory/counts endpoints over the network. The endpoints can be accessed without the configured DOCLING_SERVE_API_KEY.

Q: What can an unauthenticated attacker obtain or do?

An attacker can read process and cgroup memory telemetry and object-type histograms. They can also repeatedly trigger gc.collect() heap enumeration through the affected memory endpoints.

Q: Does configuring DOCLING_SERVE_API_KEY protect these endpoints?

No. The affected endpoints omit the require_auth dependency, allowing requests to bypass the configured API-key authentication.

Q: How can I determine whether an instance is affected?

Check whether the deployment runs docling-serve from 1.14.0 through 1.36.0. On those versions, verify whether /v1/memory/stats and /v1/memory/counts return data without supplying the configured API key.

Published Oct 11, 2026

Updated

docling-serve 1.14.0 through 1.36.0 contains a missing authentication vulnerability that allows unauthenticated attackers to access /v1/memory/stats and /v1/memory/counts because they omit the requireauth dependency. Attackers can bypass the configured DOCLINGSERVEAPIKEY to read process and cgroup memory telemetry, object type histograms, and force repeated gc.collect() heap enumeration.

Affected Software

1 affected component

pypi/docling-serve>=1.14.0<=1.36.0

Event History

Oct 11, 2026

CVE Published

via MITRE·12:19 PM

Data Sourced

via MITRE·12:19 PM

DescriptionSeverityWeakness

Data Sourced

via NVD·01:17 PM

DescriptionSeverityWeakness

Frequently Asked Questions

Who is exposed to this issue?

Instances running docling-serve versions 1.14.0 through 1.36.0 are exposed if attackers can reach the /v1/memory/stats or /v1/memory/counts endpoints over the network. The endpoints can be accessed without the configured DOCLING_SERVE_API_KEY.

What can an unauthenticated attacker obtain or do?

An attacker can read process and cgroup memory telemetry and object-type histograms. They can also repeatedly trigger gc.collect() heap enumeration through the affected memory endpoints.

Does configuring DOCLING_SERVE_API_KEY protect these endpoints?

No. The affected endpoints omit the require_auth dependency, allowing requests to bypass the configured API-key authentication.

How can I determine whether an instance is affected?

Check whether the deployment runs docling-serve from 1.14.0 through 1.36.0. On those versions, verify whether /v1/memory/stats and /v1/memory/counts return data without supplying the configured API key.

CVE-2026-108749: docling-serve 1.14.0 through 1.36.0 Missing Authentication via Memory Management Endpoints

Affected Software

Event History

Frequently Asked Questions

Who is exposed to this issue?

What can an unauthenticated attacker obtain or do?

Does configuring DOCLING_SERVE_API_KEY protect these endpoints?

How can I determine whether an instance is affected?

Company

Resources

Contact

Frequently Asked Questions

Who is exposed to this issue?

What can an unauthenticated attacker obtain or do?

Does configuring DOCLING_SERVE_API_KEY protect these endpoints?

How can I determine whether an instance is affected?