Skip to main content

Copilot Studio CVE-2026-80098

| EUVDEUVD-2026-70794 CRITICAL
Improper Verification of Cryptographic Signature (CWE-347)
2026-09-03 secure@microsoft.com GHSA-r9hf-26xj-x88v
10.0
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach Copilot Studio endpoint over network
  2. Delivery
    Forge token with invalid signature
  3. Exploit
    Service fails signature verification
  4. Execution
    Assert elevated identity/role
  5. Persist
    Cross scope to other authority
  6. Impact
    Access/control unauthorized resources

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Signature verification
Exploitation Conditions

Exploitation requires network reachability to the Copilot Studio service endpoint that performs the flawed signature check, and the ability to present a crafted token (the 'Jwt Attack' tag points to a JWT). Per CVSS AV:N/AC:L/PR:N/UI:N no authentication, no user interaction, and no special access are needed, so the practical prerequisite is simply reaching the vulnerable service and supplying a token whose signature the service fails to verify correctly; the limiting factor is that only Microsoft's hosted Copilot Studio deployment is affected and the vulnerable code path is server-side, so once Microsoft remediates the service-side flow the condition no longer holds for tenants.

Impact

The signals conflict and must be weighed carefully. CVSS is a maximal 10.0 (AV:N/AC:L/PR:N/UI:N/S:C, all impacts High) and SSVC marks the technical impact as 'total' with automatable 'yes', which argues for treating this as a top-priority remediation. Against that, SSVC exploitation is 'none', EPSS is only 0.29% (22nd percentile), there is no CISA KEV listing, and no public exploit was identified - so this is a critical-by-design but not-yet-widely-exploited issue. For a cloud SaaS the practical mitigation burden is largely on Microsoft's side rather than on customers, which tempers customer-side urgency somewhat; nonetheless, because signature-verification bypasses are automatable and can be trivially scripted once details leak, any organization running Copilot Studio agents should confirm Microsoft's service-side fix is applied and monitor for anomalous privileged actions rather than wait for EPSS to climb.

Exploit ScenarioDerived

An unauthenticated attacker on the network crafts a token with a forged or unverified signature and submits it to a Copilot Studio endpoint that fails to properly validate the signature (CWE-347). The service accepts the forged identity/role, granting the attacker elevated privileges that cross into another security scope (S:C), allowing access to or control over resources they should not reach. No public proof-of-concept has been identified, but SSVC marks the attack as automatable.

Monitor Track and reassess. Why: Vendor states no customer action required.
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv2 – Sep 08, 2026

Privilege elevation in Microsoft Copilot Studio lets a network-based, unauthenticated attacker bypass cryptographic signature verification (CWE-347) to gain elevated privileges across a scope boundary, per CVSS:3.1 AV:N/PR:N/S:C rated 10.0. The flaw appears to involve forged or improperly validated JWT tokens, per the 'Jwt Attack' tagging, and because Copilot Studio is a multi-tenant cloud service the scope-change vector implies impact beyond the initially compromised authority. No public exploit identified at time of analysis, and EPSS is low at 0.29% (22nd percentile), but SSVC rates technical impact as total and automatable as yes.

Earlier versions of this analysis (1)
v1 Sep 03, 2026 - 23:45 CVSS 9.3

Privilege escalation in Microsoft Copilot Studio lets an unauthenticated network attacker forge or replay authentication material because the service fails to properly verify a cryptographic signature (CWE-347). The 'Jwt Attack' tag indicates the flaw centers on JWT signature validation, allowing token spoofing that elevates privileges across the multi-tenant cloud service (scope change). Microsoft rates it 9.3 Critical; no public exploit identified at time of analysis and it is not listed in CISA KEV.

RemediationAI

Because Copilot Studio is a Microsoft-operated cloud service, the fix is delivered service-side by Microsoft; consult the MSRC update guide at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-80098 to confirm the mitigation is deployed and whether any tenant-side action is required - Patch available per vendor advisory, with no discrete customer-installable version published. As compensating controls while confirming remediation, review Copilot Studio and Power Platform audit logs for unexpected privilege grants or agent actions, tighten conditional-access and network restrictions around who can reach the service, rotate any long-lived tokens or connection secrets used by agents, and enforce least-privilege on the identities that agents run under; the trade-off of tighter conditional access is potential disruption to legitimate low-code developers and automated agent flows.

Affected VersionsENISA

Microsoft Copilot Studio - (version not specified)

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Copilot Studio is Microsoft's low-code platform for building custom AI agents/copilots over the Power Platform, exposed as a network-accessible SaaS (cpe:2.3:a:microsoft:copilot_studio). CWE-347 (Improper Verification of Cryptographic Signature) is the root cause: the service accepts a security token - consistent with the 'Jwt Attack' tag, most plausibly a JWT - without correctly validating its signature. When signature validation is weak (e.g. accepting 'alg: none', failing to verify against the trusted signing key, or confusing symmetric/asymmetric keys), an attacker can mint or tamper with a token to assert an identity or role they do not legitimately hold, yielding privilege elevation. The CVSS S:C (scope changed) reflects that a break in the authenticating component's guarantees propagates to resources under a different security authority - characteristic of token-forgery bugs in shared, multi-tenant identity flows.

Know when Copilot Studio gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 10.0 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
vuln.today AI 10.0 CRITICAL

Network-reachable service accepting a forged token needs no auth or interaction (AV:N/AC:L/PR:N/UI:N); token forgery in a multi-tenant service crosses scope (S:C) with full C/I/A impact.

3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

3
Analysis Updated
Sep 08, 2026 - 18:13 vuln.today
v2 - CVSS changed
CVSS changed
Sep 08, 2026 - 18:07 NVD
9.3 (CRITICAL) 10.0 (CRITICAL)
CVE Published
Sep 03, 2026 - 23:17 nvd
CRITICAL 9.3

DescriptionNVD

Improper verification of cryptographic signature in Copilot Studio allows an unauthorized attacker to elevate privileges over a network.

Executive ViewAI

Why It Matters

Microsoft Copilot Studio contains a critical privilege elevation vulnerability (CVSS 10.0) allowing unauthenticated attackers to forge authentication tokens and gain elevated privileges across customer tenants in the shared cloud environment. All organizations using Copilot Studio are exposed to complete account compromise and unauthorized access to sensitive business data and integrations without any authentication requirement. This represents one of the most severe cloud service vulnerabilities, with no patch currently available.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: restrict network access to Copilot Studio via IP whitelisting and mandatory VPN requirement; enforce multi-factor authentication for all administrative users; implement approval workflows for privilege escalation requests; audit and disconnect integrations to production systems; establish real-time monitoring for cryptographic validation anomalies and unusual privilege escalation patterns; maintain comprehensive audit logging of all administrative activity for forensic investigation.

Threat Intelligence Overview

EPSS Score
0.3%
Top 78% exploitable
Prevalence
Medium
Microsoft SaaS with growing enterprise adoption, not universally deployed
Threat Intel
1
1 sources
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:N/A
Service Type
Hosted
Vendor-managed, no client patch needed
Social Media
2
Sightings
Data Quality
7 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
Vendor states no customer action required
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Total

Priority Score

50
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +50
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy