CVE-2025-65037
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 control of generation of code ('code injection') in Azure Container Apps allows an unauthorized attacker to execute code 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 code injection vulnerability in Azure Container Apps allows an unauthenticated attacker to inject and execute arbitrary code remotely over the network. The vulnerability stems from improper control of code generation within the Azure Container Apps service, potentially enabling full compromise of containerized workloads.
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
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Identify Azure Container Apps usageRun 'az containerapp list --resource-group <your-rg>' or check Azure Portal for any deployed Container Apps in your subscriptionsAffected if Any Azure Container App resource exists in your environment
-
Check for public network exposureReview Container App ingress configuration using 'az containerapp show --name <app> --resource-group <rg> --query properties.configuration.ingress' and verify if external IP/URL is exposed to the internetAffected if Ingress is set to 'External' and the Container App is reachable from the internet without authentication
-
Review audit and activity logs for anomalous commandsIn Azure Portal, navigate to Container App > Monitoring > Log Analytics and query SecurityEvent or AuditLogs for unexpected process execution, especially from Azure service IPsAffected if Logs show suspicious process creation or code execution that did not originate from your application code
-
Check for unexpected environment variables or secretsRun 'az containerapp show --name <app> --resource-group <rg> --query properties.configuration.secrets' and verify all secrets were created by your deployment pipelineAffected if Unknown secrets or environment variables exist that your team did not create
-
Monitor for unexpected outbound network connectionsUse Azure Network Watcher or NSG flow logs to identify outbound connections from Container Apps to unknown external IPs, especially on uncommon portsAffected if Container Apps are establishing outbound connections to IPs or services you do not recognize
Your environment is affected if you have any Azure Container Apps deployed, particularly those with external/public ingress enabled, as the vulnerability allows unauthenticated remote code execution in the service itself.
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 Azure security advisories for the applicable patch and apply updates when available. Review and restrict container app configurations, implement network segmentation, and follow least-privilege principles for Azure Container Apps deployments until the vendor patch is released.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-65037 — 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-2025-65037 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