dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-15496

MEDIUM · 6.3 CVSS v3.1 Published 2026-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was found in SonicCloudOrg sonic-agent up to 2.7.2. The impacted element is the function evalIsFailed of the file sonic-agent/src/main/java/org/cloud/sonic/agent/tests/script/GroovyScriptImpl.java of the component Groovy Script Handler. The manipulation results in os command injection. The attack can be launched remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way. This vulnerability only affects products that are no longer supported by the maintainer.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

OS command injection vulnerability in the evalIsFailed function of GroovyScriptImpl.java in SonicCloudOrg sonic-agent up to v2.7.2. The Groovy Script Handler processes user-manipulated input without proper sanitization, allowing remote attackers to inject and execute arbitrary OS commands via the vulnerable function.

MitigationThis affects end-of-life versions no longer supported by the vendor. If the product cannot be upgraded, implement strict input validation at any upstream layer, disable the vulnerable Groovy script execution feature if not required, and restrict network access to the affected service.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify sonic-agent installation and version
    Locate the sonic-agent installation directory. Check for a version file (such as version.txt, build.gradle, or pom.xml) or run 'java -jar sonic-agent.jar --version' if executable. Compare the discovered version to v2.7.2 or earlier.
    Affected if The installed version is v2.7.2 or any earlier version.
  2. Locate the GroovyScriptImpl.java file
    Search the sonic-agent installation directory for the file GroovyScriptImpl.java or its compiled class file (GroovyScriptImpl.class). This file contains the vulnerable evalIsFailed function.
    Affected if The file exists in the installation, indicating the vulnerable component is present.
  3. Determine if Groovy script execution is enabled
    Inspect the sonic-agent configuration files (such as application.yml, application.properties, or config.groovy) for any settings related to Groovy script execution, groovy-enabled, script-handler, or groovy-handler. Check if these settings are present and set to true or enabled.
    Affected if Groovy script execution feature is explicitly enabled in the configuration.
  4. Check network exposure of the script handler
    Review network listeners and API endpoint definitions in the configuration or code. Look for any endpoints that expose the Groovy Script Handler functionality to network requests. Check for mappings such as '/groovy', '/script/execute', or similar patterns.
    Affected if The Groovy Script Handler is exposed via network-accessible endpoints without authentication.
  5. Inspect runtime process for command injection indicators
    Monitor the sonic-agent process for unexpected shell executions using process monitoring tools (such as 'ps' on Linux or Process Explorer on Windows). Review application logs for any suspicious command patterns or errors related to the evalIsFailed function.
    Affected if Unexpected shell commands or suspicious patterns appear in process activity or logs.

A user is affected if they are running sonic-agent v2.7.2 or earlier with the Groovy script execution feature enabled and exposed to network access, allowing unauthenticated attackers to inject OS commands through the evalIsFailed function.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

This affects end-of-life versions no longer supported by the vendor. If the product cannot be upgraded, implement strict input validation at any upstream layer, disable the vulnerable Groovy script execution feature if not required, and restrict network access to the affected service.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15496 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15496 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data