CVE-2025-24986
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 isolation or compartmentalization in Azure PromptFlow 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 confidenceAzure PromptFlow contains an improper isolation vulnerability where the service fails to properly compartmentalize execution environments, allowing an unauthorized attacker to execute arbitrary code over a network. This represents a sandbox escape or insufficient isolation between tenants or 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 data< 1.17.2< 1.6.0CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
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 PromptFlow Core versionRun 'pip show promptflow' or 'pip list | grep promptflow' to list installed PromptFlow packages and their versionsAffected if The installed version is lower than 1.17.2
-
Identify PromptFlow Tools versionRun 'pip show promptflow-tools' or check the tools package version via 'pip list'Affected if The installed version is lower than 1.6.0
-
Verify execution environment isolation configurationReview PromptFlow runtime settings and compute configuration in Azure Portal or via 'pf runtime list' command to confirm whether custom runtimes with proper isolation are configuredAffected if The deployment uses default runtimes without custom compartment isolation, or shared compute targets
-
Confirm multi-tenant or untrusted input handlingExamine flow definitions and test whether PromptFlow executions can receive or process inputs from untrusted or external sources across network boundariesAffected if The PromptFlow service handles inputs from untrusted network sources or executes flows from multiple tenants on shared compute resources
You are affected if PromptFlow Core is below 1.17.2 or PromptFlow Tools is below 1.6.0, AND the service processes untrusted inputs or runs multi-tenant workloads without proper execution environment compartmentalization.
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.
dbcve · scoped1.6.01.17.2
Review and enforce proper network isolation and execution environment compartmentalization in Azure PromptFlow deployments; apply any available Azure security updates or configuration hardening guidelines.
Azure Promptflow Core: 1.17.2 | Azure Promptflow Tools: 1.6.0
- Identify current versions of Azure Promptflow Core and Azure Promptflow Tools in your environment
- Upgrade Azure Promptflow Core to version 1.17.2 or later
- Upgrade Azure Promptflow Tools to version 1.6.0 or later
- Verify both upgrades completed successfully
- Test the application in a non-production environment to ensure functionality is maintained
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24986 — 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-24986 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