CVE-2026-35428
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 · uneditedImproper neutralization of special elements used in a command ('command injection') in Azure Cloud Shell allows an unauthorized attacker to perform spoofing over a network.
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 confidenceA command injection vulnerability (CWE-78) exists in Azure Cloud Shell where improper neutralization of special elements allows an unauthorized attacker to inject arbitrary commands. The flaw enables spoofing over a network, indicating the attacker can potentially execute commands with the privileges of the Cloud Shell service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS 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
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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.
-
Verify Azure Cloud Shell accessCheck if Cloud Shell is available in your Azure subscription by logging into the Azure Portal and looking for the Cloud Shell icon (>_) in the top toolbar, or by accessing https://shell.azure.com/Affected if Cloud Shell is accessible and can be launched
-
Identify active Cloud Shell sessionsReview Azure Activity Logs for 'Connect to CloudShell' events. In Azure Portal, go to Monitor > Activity Log and filter by operation name containing 'CloudShell'Affected if Unexpected Cloud Shell sessions are visible in logs or were initiated from unfamiliar locations
-
Inspect Cloud Shell file system for suspicious scriptsIn an active Cloud Shell session, list files in the home directory (~) and /tmp for unexpected scripts or executables using 'ls -la ~' and 'ls -la /tmp'Affected if Unknown scripts or executables exist in the Cloud Shell file system that were not created by authorized users
-
Review running processes in Cloud ShellIn an active Cloud Shell session, run 'ps aux' to list running processes and check for unfamiliar commands or reverse shellsAffected if Unexpected processes are running that do not correspond to user-initiated commands
-
Check for unauthorized network connectionsIn an active Cloud Shell session, run 'netstat -an' or 'ss -tunap' to inspect outbound network connections from the Cloud Shell environmentAffected if Outbound connections exist to unknown or suspicious external IP addresses
A user is affected if they have access to Azure Cloud Shell and evidence shows unauthorized command execution, unexpected processes, or suspicious network connections originating from the Cloud Shell environment.
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 dataMonitor Microsoft's security advisories for the Azure Cloud Shell patch. Implement network segmentation and conditional access policies to limit exposure to Azure Cloud Shell until the vendor patch is applied.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35428 — 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-35428 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