Cross-site Scripting (XSS) Affecting kibana-8.18-config package, versions *


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.04% (13th 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 Learn

Learn about Cross-site Scripting (XSS) vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-MINIMOSLATEST-KIBANA818CONFIG-15955082
  • published9 Apr 2026
  • disclosed27 Mar 2026

Introduced: 27 Mar 2026

NewCVE-2026-33916  (opens in a new tab)
CWE-79  (opens in a new tab)
CWE-1321  (opens in a new tab)

How to fix?

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

NVD Description

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

Handlebars provides the power necessary to let users build semantic templates. In versions 4.0.0 through 4.7.8, resolvePartial() in the Handlebars runtime resolves partial names via a plain property lookup on options.partials without guarding against prototype-chain traversal. When Object.prototype has been polluted with a string value whose key matches a partial reference in a template, the polluted string is used as the partial body and rendered without HTML escaping, resulting in reflected or stored XSS. Version 4.7.9 fixes the issue. Some workarounds are available. Apply Object.freeze(Object.prototype) early in application startup to prevent prototype pollution. Note: this may break other libraries, and/or use the Handlebars runtime-only build (handlebars/runtime), which does not compile templates and reduces the attack surface.

CVSS Base Scores

version 3.1