Unauthenticated code execution via GroovyShell.evaluate
Published Aug 16, 2026 · Updated Aug 16, 2026
Code injection in Notice System Management 2.0 allows remote attackers to execute arbitrary Groovy code through the /execute endpoint. NoticeController sends the request's code parameter directly to GroovyShell.evaluate without sanitization, an allowlist, or a sandbox. The route contains no authorization check and the published request supplies no credentials, so operating-system commands run with the server process's privileges.
Summary
What happened
Code injection in Notice System Management 2.0 allows remote attackers to execute arbitrary Groovy code through the /execute endpoint. NoticeController sends the request's code parameter directly to GroovyShell.evaluate without sanitization, an allowlist, or a sandbox. The route contains no authorization check and the published request supplies no credentials, so operating-system commands run with the server process's privileges.
The record
- CVE
- CVE-2026-19932
- Published
- Aug 16, 2026
- Updated
- Aug 16, 2026
- Vendor
- DefaultFuction
- Product
- Notice System Management
- Classifications
- CWE-94, CWE-74, T1190, T1059
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 16, 2026CVE publishedPublication date reported by the CVE source.
- Aug 16, 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=2.0
What conditions does exploitation require?
What is affected?
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
- GitHub issue reproduction for Groovy code injectionfunctional · 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