Server-Side Request Forgery (SSRF) Affecting kube-logging-operator package, versions <6.3.2-r3


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.02% (6th 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-CHAINGUARDLATEST-KUBELOGGINGOPERATOR-15285813
  • published16 Feb 2026
  • disclosed9 Feb 2026

Introduced: 9 Feb 2026

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

How to fix?

Upgrade Chainguard kube-logging-operator to version 6.3.2-r3 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kube-logging-operator package and not the kube-logging-operator package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

Faraday is an HTTP client library abstraction layer that provides a common interface over many adapters. Prior to 2.14.1, Faraday's build_exclusive_url method (in lib/faraday/connection.rb) uses Ruby's URI#merge to combine the connection's base URL with a user-supplied path. Per RFC 3986, protocol-relative URLs (e.g. //evil.com/path) are treated as network-path references that override the base URL's host/authority component. This means that if any application passes user-controlled input to Faraday's get(), post(), build_url(), or other request methods, an attacker can supply a protocol-relative URL like //attacker.com/endpoint to redirect the request to an arbitrary host, enabling Server-Side Request Forgery (SSRF). This vulnerability is fixed in 2.14.1.

CVSS Base Scores

version 3.1