Interpretation Conflict Affecting kibana-8 package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.34% (27th 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-MINIMOSLATEST-KIBANA8-16917217
  • published28 May 2026
  • disclosed17 Jul 2026

Introduced: 28 May 2026

CVE-2026-44974  (opens in a new tab)
CWE-436  (opens in a new tab)

How to fix?

There is no fixed version for Minimos:latest kibana-8.

NVD Description

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

@hapi/content provided HTTP Content-* headers parsing. Prior to 6.0.2, Content.disposition() retained the last occurrence of each duplicate parameter while Content.type() retained the first occurrence of duplicate charset and boundary parameters, creating a parameter-smuggling primitive when another component in the request-processing chain resolves duplicates the opposite way. This can allow an upload filename allowlist bypass in headers such as Content-Disposition: form-data; name="file"; filename="safe.txt"; filename="shell.php". This issue is fixed in version 6.0.2.