CVE-2026-18149 Affecting prism package, versions <5.16.0-r14


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.36% (30th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-PRISM-20514938
  • published6 Oct 2026
  • disclosed4 Sept 2026

Introduced: 4 Sep 2026

CVE-2026-18149  (opens in a new tab)

How to fix?

Upgrade Chainguard prism to version 5.16.0-r14 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream prism package and not the prism package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

undici's retry handler can leave an already-exposed response body pending forever. When a server returns a successful response that declares a Content-Length, sends only part of the body, and closes the connection, the retry handler retries the request. If the retry returns a non-retryable status such as 400, the handler forwards that new response downstream and replaces its internal response stream, but the original response body that the application still holds is never ended or destroyed. As a result calls that read that body never settle, and the configured body timeout does not fire because its timer is tied to the connection parser rather than the orphaned body. An attacker-controlled server can trigger this with two short responses without keeping a connection open, and repeated requests accumulate pending promises and streams that can exhaust application concurrency or memory. This affects undici versions from 7.11.0 up to 7.29.1 and from 8.0.0 up to 8.10.2. Users should upgrade to undici 7.29.1 or 8.10.2.

CVSS Base Scores

version 3.1