CVE-2026-30352: A remote code execution (RCE) vulnerability in the /devserver/start endpoint of leonvanzyl autocoder commit...
A remote code execution (RCE) vulnerability in the /devserver/start endpoint of leonvanzyl autocoder commit 79d02a allows attackers to execute arbitrary code via providing a crafted command parameter.
Security readout for executives and security teams
Plain-English summary
CVE-2026-30352 is a critical remote code execution issue reported in leonvanzyl/autocoder at commit 79d02a. If the affected development server endpoint is reachable, an unauthenticated attacker could run arbitrary code through a crafted command parameter. The public record does not identify formal affected versions, a patch, or active exploitation.
Executive priority
Prioritize immediately if autocoder is used in any exposed or shared environment. The business risk is full system compromise, but urgency depends on whether the vulnerable development endpoint is actually deployed and reachable.
Technical view
The issue is described as CWE-77 command injection in the /devserver/start endpoint. CVSS 3.1 is 9.8, network exploitable, low complexity, no privileges, and no user interaction, with high confidentiality, integrity, and availability impact. Affected product/version metadata is incomplete in the CVE source bundle.
Likely exposure
Likely exposure is limited to deployments of leonvanzyl/autocoder that include commit 79d02a or equivalent vulnerable code and expose the devserver start endpoint to untrusted users or networks. The CVE record lists affected vendor, product, and versions as n/a, so teams must confirm exposure from source and deployment evidence.
Exploitation context
The source bundle supports remote code execution potential but does not show CISA KEV listing or cite active exploitation. A referenced gist may contain vulnerability details, but the provided bundle does not establish exploitation in the wild. Treat internet-exposed devserver deployments as urgent until proven unaffected.
Researcher notes
The key evidence gap is affected-version precision. The CVE names a commit and endpoint, but affected vendor/product fields are n/a and no patch is cited. Validation should focus on source provenance, endpoint exposure, runtime privilege, and whether deployed code matches the reported vulnerable path.
Mitigation direction
Check the upstream repository and CVE record for maintainer remediation guidance.
Remove public or untrusted access to the devserver endpoint.
Disable the devserver feature where it is not operationally required.
Run affected services with least privilege and tight network controls.
Upgrade or pin only after upstream identifies a fixed revision.
Validation and detection
Inventory deployments of leonvanzyl/autocoder and identify commit 79d02a or equivalent code.
Confirm whether /devserver/start is reachable from untrusted networks.
Review access logs for unexpected devserver start requests.
Inspect code paths handling the command parameter for unsafe command execution.
Track CVE updates for clarified affected versions and fixes.
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.
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.
1CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
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.