LiveActive security incident?Get immediate response
CVE Record

CVE-2026-15496: SonicCloudOrg sonic-agent Groovy Script GroovyScriptImpl.java evalIsFailed os command injection

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.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-15496 is an OS command injection issue in SonicCloudOrg sonic-agent’s Groovy Script Handler. Public sources say versions 2.7.0 through 2.7.2 are affected, remote exploitation is possible, and proof-of-concept exploit material is public. The affected product is reportedly no longer supported, so replacement or isolation may be more realistic than patching.

Executive priority

Prioritize this for any environment still using sonic-agent 2.7.x. The issue enables command execution, exploit material is public, and affected versions are reportedly unsupported. If present in production, treat remediation as time-sensitive even though active exploitation is not confirmed.

Technical view

The flaw affects evalIsFailed in sonic-agent/src/main/java/org/cloud/sonic/agent/tests/script/GroovyScriptImpl.java. Manipulated Groovy script handling can lead to OS command injection, mapped to CWE-77 and CWE-78. The CVSS v2 vector is 6.5 with network access, low complexity, and single authentication required. VulDB reports public exploit availability.

Likely exposure

Organizations running SonicCloudOrg sonic-agent 2.7.0, 2.7.1, or 2.7.2 are the stated exposure group. Risk is highest where sonic-agent or its script-handling features are reachable by users outside a tightly controlled admin group.

Exploitation context

Sources support public exploit availability, but not confirmed active exploitation. The CVSS vector indicates authentication is required. Because the product is described as unsupported and the vendor did not respond, defenders should not assume a vendor patch is available.

Researcher notes

Evidence is mainly from VulDB/CVE records and a public exploit repository reference. The affected component and function are named, but no vendor advisory or patch is cited. The CVSS vector shows authenticated remote attack requirements, so validation should focus on version, reachability, and script-execution permissions.

Mitigation direction

  • Inventory SonicCloudOrg sonic-agent deployments and versions immediately.
  • Remove, replace, or isolate affected unsupported versions.
  • Restrict access to sonic-agent management and Groovy script functionality.
  • Allow only trusted administrators to use script execution features.
  • Monitor host activity for unexpected child processes from sonic-agent.
  • Check project or vendor channels for any later remediation guidance.

Validation and detection

  • Confirm whether sonic-agent 2.7.0, 2.7.1, or 2.7.2 is installed.
  • Verify network exposure of sonic-agent interfaces and management paths.
  • Review who can authenticate and run Groovy script features.
  • Inspect logs for unusual Groovy script execution events.
  • Review endpoint telemetry for suspicious sonic-agent process behavior.
  • Document compensating controls if immediate replacement is not possible.
Prepared
Confidence
medium
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-77: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · medium confidence lookup

CWE-78: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-15496 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (2.0)
Known Exploited
No
Published

Vector: AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

4CVSS vectors
6Timeline events
0ADP providers
6Source links

CVSS vector scores

4 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 2.0MediumAV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR86.4VulDB
6.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R2.83.4VulDB
6.3CVSS 3.0MediumCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R2.83.4VulDB
5.3CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PVulDB

Vulnerability scoring details

Base CVSS 4.0 score

5.3Medium
CVSS 4.0 vector shape for CVE-2026-15496Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timelineVulDB

    Advisory disclosed

  2. Source timelineVulDB

    VulDB entry created

  3. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  4. Source timelineVulDB

    VulDB entry last update

  5. CVE publishedCVE Program

    The CVE record was published.

  6. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SonicCloudOrgsonic-agent2.7.0, 2.7.1, 2.7.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.