Script termination via eager parenthesized subexpression evaluation
Published Apr 22, 2026 · Updated Apr 22, 2026
Incorrect short-circuit evaluation in uutils coreutils before 0.8.0 allows local users to terminate scripts through crafted expr input. The expr parser calls evaluated() while parsing a parenthesized subexpression, forcing arithmetic in dead OR and AND branches before execution. The input must reach a locally invoked expr command; division by zero in a branch that should be skipped instead raises a fatal error and prematurely stops GNU-compatible shell control flow.
Summary
What happened
Incorrect short-circuit evaluation in uutils coreutils before 0.8.0 allows local users to terminate scripts through crafted expr input. The expr parser calls evaluated() while parsing a parenthesized subexpression, forcing arithmetic in dead OR and AND branches before execution. The input must reach a locally invoked expr command; division by zero in a branch that should be skipped instead raises a fatal error and prematurely stops GNU-compatible shell control flow.
The record
- CVE
- CVE-2026-35378
- Published
- Apr 22, 2026
- Updated
- Apr 22, 2026
- Vendor
- uutils
- Product
- coreutils
- Classifications
- CWE-768, CAPEC-153, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 22, 2026CVE publishedPublication date reported by the CVE source.
- Apr 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.8.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream parenthesized dead-branch reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo