CVE-2026-15495: SonicCloudOrg sonic-agent Android WebSocket Server AndroidWSServer.java os command injection
A vulnerability has been found in SonicCloudOrg sonic-agent up to 2.7.2. The affected element is an unknown function of the file AndroidWSServer.java of the component Android WebSocket Server. The manipulation of the argument path leads to os command injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may 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.
Security readout for executives and security teams
Plain-English summary
CVE-2026-15495 is a command injection issue in SonicCloudOrg sonic-agent versions 2.7.0 through 2.7.2. A remote authenticated attacker may manipulate a path argument handled by the Android WebSocket Server component to run operating system commands. Public proof-of-concept material is referenced. The affected releases are reported as no longer supported.
Executive priority
Treat as a near-term remediation item for environments using SonicCloudOrg sonic-agent. The risk is not confirmed as actively exploited, but public exploit material and unsupported affected versions increase operational urgency. Prioritize internet-accessible or shared testing infrastructure first.
Technical view
The issue is mapped to CWE-77 and CWE-78 in AndroidWSServer.java. VulDB describes remote exploitation with low attack complexity but requiring authentication, affecting confidentiality, integrity, and availability partially. The CVSS v2 score is 6.5. Vendor contact reportedly received no response, and no vendor fix is identified in the provided sources.
Likely exposure
Exposure is most likely where sonic-agent 2.7.0, 2.7.1, or 2.7.2 is deployed and its Android WebSocket Server is reachable by authenticated users over a network. Internet-facing or broadly accessible agent services raise urgency. The sources state only unsupported versions are affected.
Exploitation context
The exploit has been publicly disclosed, including a referenced GitHub proof of concept. CISA KEV status is not indicated, and the provided sources do not prove active exploitation in the wild. Authentication is required according to the CVSS vector and VulDB CTI labeling.
Researcher notes
Evidence is primarily from VulDB/CVE records and referenced public PoC material. The vulnerable function is not named beyond AndroidWSServer.java, and no vendor advisory or patch is provided in the source bundle. Avoid assuming newer versions are fixed unless confirmed by vendor or repository guidance.
Mitigation direction
Inventory sonic-agent deployments and identify versions 2.7.0, 2.7.1, and 2.7.2.
Restrict network access to the Android WebSocket Server to trusted administrative paths only.
Remove or isolate unsupported sonic-agent instances where business operations allow.
Check SonicCloudOrg project guidance for any migration, replacement, or maintained release path.
Monitor logs for suspicious authenticated activity involving file path handling.
Validation and detection
Confirm installed sonic-agent version on all hosts running the service.
Verify whether the Android WebSocket Server component is enabled and reachable.
Review access controls for accounts permitted to reach the service.
Check network exposure from untrusted segments and the internet.
Review authentication and application logs around suspicious path input handling.
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.
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.
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.
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
7Source 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-77 · source CWE mapping
Improper Neutralization of Special Elements used in a Command ('Command Injection')
Improper Neutralization of Special Elements used in a Command ('Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.