CRLF Injection Affecting elasticsearch-8.15 package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

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-MINIMOSLATEST-ELASTICSEARCH815-18281491
  • published24 Jul 2026
  • disclosed28 Jul 2026

Introduced: 24 Jul 2026

NewCVE-2026-59921  (opens in a new tab)
CWE-93  (opens in a new tab)

How to fix?

There is no fixed version for Minimos:latest elasticsearch-8.15.

NVD Description

Note: Versions mentioned in the description apply only to the upstream elasticsearch-8.15 package and not the elasticsearch-8.15 package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

Netty is an asynchronous, event-driven network application framework. Prior to versions 4.1.136.Final and 4.2.16.Final, HttpPostRequestEncoder constructs multipart HTTP request bodies by directly concatenating user-supplied filenames and field names into Content-Disposition MIME headers without validating or sanitizing CRLF characters (\r\n). Since MIME headers are delimited by CRLF, an attacker who controls the filename can inject arbitrary MIME headers into the multipart body part. The root cause is that neither the encoder nor the FileUpload implementations' setFilename() methods, which only check for null, neutralize CRLF characters before the filename is embedded into the header. This issue has been fixed in versions 4.1.136.Final and 4.2.16.Final.

CVSS Base Scores

version 3.1