Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
9.9

Kyverno UI Docker images may execute unexpected commands

published 8 days ago
Summary

The "quote" function in a library used by the Kyverno policy reporter UI Docker images can treat a comment as normal text, causing the rest of a command line to be interpreted as code. An attacker could inject a line break that makes the system run unintended commands. Update the images to version 1.11.0 or later, which blocks this behavior, and redeploy the containers.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
Ecosystem VendorProductAffected versions
Docker Hardened Images:Alpine:3.24 docker hardened images kyverno-policy-reporter-ui-dev All versions
Docker Hardened Images:Alpine:3.24 docker hardened images kyverno-policy-reporter-ui-fips-dev All versions
Docker Hardened Images:Alpine:3.24 docker hardened images kyverno-policy-reporter-ui-fips All versions
Docker Hardened Images:Alpine:3.24 docker hardened images kyverno-policy-reporter-ui All versions
Docker Hardened Images:Debian:13 docker hardened images langfuse-2 All versions
Original advisory text
shell-quote's `quote()` function emits a `{ comment }` token as `#` followed by its text, which comments out the rest…
shell-quote's `quote()` function emits a `{ comment }` token as `#` followed by its text, which comments out the rest of the shell line, including the opening quote of any later string token. A line terminator (\n, \r, U+2028, U+2029) in that later string therefore ends the comment, and the rest of the string is parsed as shell input: `quote(['echo', 'ok', { comment: 'x' }, 'a\nid;#'])` runs `id` in sh, bash, dash, ksh and zsh. `parse()` emits a comment token for a `#` in the middle of a word (for example `http://example.com/#frag`), so callers that combine `parse()` output with another untrusted string, such as `quote(parse(untrustedCommand).concat(untrustedArg))`, are affected. The fix for CVE-2026-9277 rejected line terminators in the comment's own text, but not in the tokens after it. Fixed in 1.11.0: `quote()` throws a `TypeError` when a string after a `{ comment }` token contains a line terminator.
Fix within
Internet-facing 14 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit (estimated)
  • Gives an attacker full control (estimated)
Severity
9.9 Critical
Timeline
Published13 Nov 2026
Updated16 Nov 2026
First seen16 Nov 2026
Sources
Track software like this
Free during beta