CVE-2026-59337

Spring AI could write full prompts to warning logs

Spring / Broadcom · Spring AI · Prompt logging

First documented disclosure · Review checkpoint

Summary

Full prompts could expose user information or proprietary instructions through shared logs.

Severity and exploitation evidence

Low · 3.3/10 · CVSS 3.1. Severity source.

Exploitation not established: The vendor describes the flaw and remediation; the reviewed sources do not establish malicious exploitation.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

Prompt content is written at WARN level and may reach a broader logging audience.

Conditions required

Sensitive prompts are processed and the warning log is collected or read beyond the originating tenant.

Potential impact

Disclosure of prompt content.

Affected versions and configurations

2.0.0–2.0.2, 1.1.0–1.1.9 and 1.0.0–1.0.10.

Fix and mitigation status

2.0.3 (OSS); 2.0.2.1 (enterprise support only). Older supported branches: 1.1.10 and 1.0.11, enterprise support only.

Practical next steps

Upgrade to the applicable corrected release. Public 2.0.3 is available; listed older-branch binaries require enterprise support.

Operating lesson

Apply explicit bounds and trust checks to every path accepting untrusted AI context or input.

Evidence and limits

Original vendor advisory is November 19. All nine exact CVE authority requests returned 404 at review; the numbering and affected/fixed mapping come directly from Spring. GitHub 2.0.3 release was published November 20 at 15: 47: 36Z, before this review cutoff. CVSS 3.1 base scores are calculated from each Spring advisory’s published vector; the vendor severity label is retained separately. No score is borrowed from another source.

Sources