Arbitrary Command Injection Affecting kube-logging-operator package, versions <6.6.0-r2


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.49% (39th 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-CHAINGUARDLATEST-KUBELOGGINGOPERATOR-17338500
  • published15 Jun 2026
  • disclosed22 Jun 2026

Introduced: 15 Jun 2026

NewCVE-2026-47240  (opens in a new tab)
CWE-77  (opens in a new tab)
CWE-93  (opens in a new tab)

How to fix?

Upgrade Chainguard kube-logging-operator to version 6.6.0-r2 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.

Net::IMAP implements Internet Message Access Protocol (IMAP) client functionality in Ruby. Prior to 0.6.5 and 0.5.15, several Net::IMAP commands accept a "raw data" argument that is sent verbatim after validation to prevent command injection. However, if a server does not support non-synchronizing literals, it may still be possible to inject arbitrary IMAP commands inside non-synchronizing literals. A server without support for non-synchronizing literals may interpret the "+}\r\n" as the end of a malformed command line and respond with a tagged BAD. In that case, the contents of the literal will be interpreted as one or more new pipelined commands, allowing a CRLF command injection attack to succeed. This affects criteria for #search and #uid_search; search_keys for #sort, #thread, #uid_sort, and #uid_thread; and attr for #fetch and #uid_fetch. This vulnerability is fixed in 0.6.5 and 0.5.15.