Homepage

Improper Input Validation Affecting kyverno-notation-aws package, versions <1.1-r1

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.48% (38th 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-MINIMOSLATEST-KYVERNONOTATIONAWS-18219759
  • published23 Jul 2026
  • disclosed23 Jul 2025
Report a new vulnerability Found a mistake?

Introduced: 23 Jul 2025

CVE-2025-47281  (opens in a new tab)
CWE-20  (opens in a new tab)
CWE-248  (opens in a new tab)

How to fix?

Upgrade Minimos:latest kyverno-notation-aws to version 1.1-r1 or higher.

NVD Description

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

Kyverno is a policy engine designed for cloud native platform engineering teams. In versions 1.14.1 and below, a Denial of Service (DoS) vulnerability exists due to improper handling of JMESPath variable substitutions. Attackers with permissions to create or update Kyverno policies can craft expressions using the {{@}} variable combined with a pipe and an invalid JMESPath function (e.g., {{@ | non_existent_function }}). This leads to a nil value being substituted into the policy structure. Subsequent processing by internal functions, specifically getValueAsStringMap, which expect string values, results in a panic due to a type assertion failure (interface {} is nil, not string). This crashes Kyverno worker threads in the admission controller and causes continuous crashes of the reports controller pod. This is fixed in version 1.14.2.