CVE-2026-30352
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 · uneditedA 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.
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 confidenceRemote code execution vulnerability in leonvanzyl autocoder's /devserver/start endpoint allows attackers to execute arbitrary commands by providing a crafted command parameter, likely due to insufficient input sanitization before passing to a system call.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if leonvanzyl autocoder is installedSearch for the autocoder package in your system using: pip list | grep -i autocoder, or check for project directories containing 'autocoder' in the name, or look for service processes named 'autocoder'Affected if leonvanzyl autocoder package or service is present on the system
-
Verify the /devserver endpoint existsInspect the autocoder codebase for routes or endpoints matching '/devserver/start' or '/devserver' - check route definition files or API endpoint configurationsAffected if The /devserver/start endpoint is defined in the application's route configuration
-
Check if the devserver feature is enabledReview autocoder configuration files (e.g., config.json, settings.py, .env) for any devserver-related settings or flags that enable the start endpointAffected if Devserver functionality is enabled in the configuration
-
Determine network exposure of the endpointCheck if the service is bound to a network interface (0.0.0.0 or public IP) rather than localhost only - inspect startup parameters, docker-compose ports, or reverse proxy configurationsAffected if The endpoint is accessible from network addresses other than localhost/127.0.0.1
-
Inspect input handling on the command parameterReview the source code handling the /devserver/start endpoint to determine if the command parameter is passed directly to shell execution functions (system, exec, popen) without sanitizationAffected if The command parameter is directly concatenated into a shell command without validation
You are affected if leonvanzyl autocoder is installed with the /devserver/start endpoint enabled and accessible over the network, and the application passes the command parameter directly to shell execution without input validation.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict input validation and sanitization for the command parameter, or refactor to avoid shell execution entirely by using parameterized methods; additionally, restrict network access to the /devserver/start endpoint.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30352 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-30352 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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