Authenticated Groovy code execution via traverseContent
Published May 19, 2026 · Updated May 19, 2026
Code injection in the traverseContent service in Apache OFBiz before 24.09.06 allows remote authenticated users to execute Groovy code. The service passes insufficiently validated traversal input into Groovy evaluation logic; the patches remove that service and related ContentWorker traversal code. Low-privileged OFBiz access is required, and successful exploitation runs code with the operating-system permissions of the OFBiz process.
Summary
What happened
Code injection in the traverseContent service in Apache OFBiz before 24.09.06 allows remote authenticated users to execute Groovy code. The service passes insufficiently validated traversal input into Groovy evaluation logic; the patches remove that service and related ContentWorker traversal code. Low-privileged OFBiz access is required, and successful exploitation runs code with the operating-system permissions of the OFBiz process.
The record
- CVE
- CVE-2026-46586
- Published
- May 19, 2026
- Updated
- May 19, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache OFBiz
- Classifications
- CWE-94, CWE-95, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 19, 2026CVE publishedPublication date reported by the CVE source.
- May 19, 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 <24.09.06
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
No public exploit references are available in this record.
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