Information Exposure Affecting kibana-8.19-config package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.04% (11th 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 Information Exposure vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-MINIMOSLATEST-KIBANA819CONFIG-16328193
  • published1 May 2026
  • disclosed23 Apr 2026

Introduced: 23 Apr 2026

NewCVE-2026-41182  (opens in a new tab)
CWE-200  (opens in a new tab)
CWE-359  (opens in a new tab)
CWE-532  (opens in a new tab)

How to fix?

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

NVD Description

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

LangSmith Client SDKs provide SDK's for interacting with the LangSmith platform. Prior to version 0.5.19 of the JavaScript SDK and version 0.7.31 of the Python SDK, the LangSmith SDK's output redaction controls (hideOutputs in JS, hide_outputs in Python) do not apply to streaming token events. When an LLM run produces streaming output, each chunk is recorded as a new_token event containing the raw token value. These events bypass the redaction pipeline entirely — prepareRunCreateOrUpdateInputs (JS) and _hide_run_outputs (Python) only process the inputs and outputs fields on a run, never the events array. As a result, applications relying on output redaction to prevent sensitive LLM output from being stored in LangSmith will still leak the full streamed content via run events. Version 0.5.19 of the JavaScript SDK and version 0.7.31 of the Python SDK fix the issue.