External risk intelligence

AAD App Proxy Privilege Escalation Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 10.0)

CVE-2026-97785

Azure Active Directory (AAD) App Proxy is designed specifically to provide secure remote access to internal web applications from the public internet. As an edge gateway service that mediates traffic between the public internet and internal resources, it is public-facing by design in its normal, intended deployment pattern.

Authentication Bypass

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

Improper authentication in Azure AD App Proxy could allow an unauthenticated attacker to gain elevated privileges over the network.

  • Unauthorized access could lead to privilege escalation.
  • Affects external access to internal applications.
  • Confirm relevance and exposure of this service.

Attack Path

How an attacker could exploit the issue

An attacker could target the AAD App Proxy over the network. Because it acts as a gateway for remote access, an unauthenticated attacker could potentially exploit this vulnerability to gain elevated privileges.

  • No prior authentication is needed.
  • The service is reachable over the network.
  • Risk includes privilege escalation.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability in AAD App Proxy could allow an unauthorized attacker to gain elevated privileges over a network when supported by the advisory. This means an attacker could potentially access internal resources with higher permissions than they should have.

  • Internal network access.
  • Unauthenticated network access.
  • Privilege escalation.

Operational Fix

Recommended remediation, mitigation, and detection steps

Given that the vulnerability affects Azure AD App Proxy, which is a gateway service for external access to internal applications, the primary responsibility likely lies with the teams managing identity and access, and the applications exposed through this proxy. The first practical step is to confirm which internal applications are exposed via App Proxy, assess their business criticality, and identify the accountable application or service owners. Subsequently, a plan for remediation or mitigation can be developed based on the assessed risk.

  • Identity and Application teams own the issue.
  • Verify exposed applications and their criticality.
  • Plan remediation with application owners.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Azure AD App Proxy?

Azure AD App Proxy is a service used to provide secure remote access to internal web applications. It acts as a gateway, allowing users outside the corporate network to reach private apps without needing a traditional VPN. It serves as a bridge, managing traffic flow between the public internet and your organization's internal, hosted web resources.

What does improper authentication mean for CVE-2026-97785?

This vulnerability is classified as CWE-287, which refers to improper authentication. In plain terms, the software fails to correctly verify the identity of a user or system attempting to connect. Because of this weakness, an unauthorized person could potentially bypass security checks and gain elevated privileges, essentially tricking the system into granting them access or permissions they should not possess.

Does an attacker need existing credentials to trigger CVE-2026-97785?

No, prior authentication is not required to trigger this vulnerability. The flaw allows an unauthenticated attacker to interact with the service directly over the network. It is important to note that the vulnerability is tied to the way the proxy handles authentication requests; simply being on the same local network is not a requirement, as the service is designed for remote connectivity.

Is my system at risk if I use Azure AD App Proxy?

According to Halo Surface Signal, this component is public-facing by design because it is intended to bridge external internet traffic to your internal applications. If you utilize this service to enable remote access, your deployment is considered to have external exposure. You should prioritize evaluating your use of this proxy, as its role as an edge gateway makes it reachable from the internet.

How should I start addressing this vulnerability?

The first step is to identify all internal applications currently being served through Azure AD App Proxy. Once you have a complete list, work with the specific application owners to determine the business criticality of each resource. This information helps your identity and access management teams prioritize which applications need immediate attention and plan the necessary remediation steps to protect your internal resources.

References