Server-Side Request Forgery (SSRF) Affecting kibana-9.2-config package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.01% (2nd 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 Server-Side Request Forgery (SSRF) vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-MINIMOSLATEST-KIBANA92CONFIG-15308974
  • published19 Feb 2026
  • disclosed9 Feb 2026

Introduced: 9 Feb 2026

CVE-2026-25528  (opens in a new tab)
CWE-918  (opens in a new tab)

How to fix?

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

NVD Description

Note: Versions mentioned in the description apply only to the upstream kibana-9.2-config package and not the kibana-9.2-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. The LangSmith SDK's distributed tracing feature is vulnerable to Server-Side Request Forgery via malicious HTTP headers. An attacker can inject arbitrary api_url values through the baggage header, causing the SDK to exfiltrate sensitive trace data to attacker-controlled endpoints. When using distributed tracing, the SDK parses incoming HTTP headers via RunTree.from_headers() in Python or RunTree.fromHeaders() in Typescript. The baggage header can contain replica configurations including api_url and api_key fields. Prior to the fix, these attacker-controlled values were accepted without validation. When a traced operation completes, the SDK's post() and patch() methods send run data to all configured replica URLs, including any injected by an attacker. This vulnerability is fixed in version 0.6.3 of the Python SDK and 0.4.6 of the JavaScript SDK.