Security readout for executives and security teams
Plain-English summary
A flaw in Azure AI Foundry agents published to Microsoft 365 could let an unauthenticated remote attacker gain privileges. Successful exploitation could expose confidential information across a changed security boundary. Microsoft rates it 8.6, making affected deployments a high-priority review even though public sources supplied here do not confirm active exploitation.
Executive priority
Treat this as a high-priority exposure review because no authentication or user action is reportedly required and confidentiality impact is high. Prioritize environments containing sensitive data. Escalate immediately if Microsoft confirms applicability; the supplied evidence does not establish active exploitation.
Technical view
CVE-2026-35435 is an improper access-control vulnerability, classified as CWE-284, affecting Azure AI Foundry Microsoft 365 published agents. The CVSS 3.1 vector indicates network reachability, low complexity, no required privileges or user interaction, changed scope, and high confidentiality impact. The supplied data identifies no integrity or availability impact and provides no affected version range.
Likely exposure
Potential exposure is limited to organizations using Azure AI Foundry agents published to Microsoft 365. Exact affected versions, configurations, and tenant conditions are not specified in the supplied sources, so vulnerability managers should inventory these agents and compare each deployment with Microsoft's advisory.
Exploitation context
The supplied CVSS metrics describe exploitation as remotely reachable, low complexity, unauthenticated, and requiring no user interaction. However, the CVE is not listed in CISA KEV within the supplied bundle, and no cited source confirms active exploitation or public exploit availability.
Researcher notes
The available record supports CWE-284 and CVSS 8.6 with scope change and confidentiality-only impact. It does not identify affected versions, the faulty authorization boundary, remediation mechanics, detection indicators, or exploit evidence. Avoid assuming all Azure AI Foundry deployments are vulnerable; the description specifically names Microsoft 365 published agents.
Mitigation direction
- Review Microsoft's CVE advisory for the current remediation and affected-service guidance.
- Apply every remediation or service-side action Microsoft identifies for affected agents.
- Restrict or suspend unnecessary Microsoft 365 published agents until their status is confirmed.
- Apply least-privilege access controls to retained agents and their connected resources.
Validation and detection
- Inventory Azure AI Foundry agents published to Microsoft 365.
- Compare each deployment against Microsoft's documented affected conditions and remediation status.
- Confirm Microsoft-recommended remediation is active for every exposed agent.
- Review relevant identity and audit records for unexplained privilege changes or confidential-data access.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-35435 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N/E:U/RL:O/RC:C
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N/E:U/RL:O/RC:C3.94microsoftVulnerability scoring details
Base CVSS 3.1 score
8.6HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N/E:U/RL:O/RC:C
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Azure AI Foundry Elevation of Privilege VulnerabilityCVE reference, microsoft · vendor-advisory, patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.