Improper Input Validation Affecting nextcloud-server-34 package, versions <34.0.2-r0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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-NEXTCLOUDSERVER34-18969945
- published20 Aug 2026
- disclosed12 Jun 2026
Introduced: 12 Jun 2026
CVE-2026-54133 (opens in a new tab)How to fix?
Upgrade Minimos:latest nextcloud-server-34 to version 34.0.2-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream nextcloud-server-34 package and not the nextcloud-server-34 package as distributed by Minimos.
See How to fix? for Minimos:latest relevant fixed versions and status.
jmespath.php allows users to use JMESPath, software for declaratively specifying how to extract elements from a JSON document, in PHP applications with PHP data structures. Versions prior to 2.9.1 can generate and execute attacker-controlled PHP code when JmesPath\CompilerRuntime is used with an attacker-controlled JMESPath expression. The compiler emits parsed JMESPath function names into generated PHP source without sufficient escaping. A crafted expression can cause the generated cache file to contain executable attacker-controlled PHP, which is then loaded by the compiler runtime. The issue is patched in 2.9.1 and later. As a workaround, disable JP_PHP_COMPILE and do not use JmesPath\CompilerRuntime with attacker-controlled expressions. Use the default AstRuntime for untrusted expressions. Applications that must continue accepting untrusted JMESPath expressions before upgrading should ensure those expressions are never evaluated by the compiler runtime.