External risk intelligence

Azure Application Gateway Out-of-Bounds Read Allows Privilege Escalation

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2025-64656

The vulnerable component is an Azure Application Gateway, which is explicitly designed to function as an internet-facing edge service, gateway, or load balancer in standard deployments. As a public-facing infrastructure component, it is by design intended to handle traffic originating from the internet.

Out-of-bounds Read

Microsoft Azure Application Gateway

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

A critical vulnerability has been identified in Azure Application Gateway, a widely used network service. This flaw could allow an unauthorized attacker to gain elevated privileges over a network, potentially impacting the confidentiality, integrity, and availability of systems. Understanding the nature of this exposure is important for assessing any potential risks to our operational environment.

  • A reading error in Application Gateway allows unauthorized privilege elevation.
  • It affects a core network service exposed to the internet.
  • Confirm relevance and exposure to our Azure environments.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by sending specially crafted network requests to an exposed Application Gateway. Because the gateway is designed to handle internet traffic, it is accessible from the network without requiring prior authentication or user interaction. This exposure allows an attacker to target the gateway directly, potentially leading to privilege escalation.

  • Network access required to reach gateway.
  • Specially crafted network requests trigger vulnerability.
  • Privilege escalation through an out-of-bounds read.

Live Threat

Current exploitation, exposure, and threat context

An out-of-bounds read vulnerability in Azure Application Gateway could allow an attacker to elevate privileges over a network. This could affect the integrity and availability of the service, and potentially lead to unauthorized access to system data when the gateway is exposed to the internet.

  • System data and service integrity.
  • Network exposure to unauthorized parties.
  • Privilege escalation and unauthorized access.

Operational Fix

Recommended remediation, mitigation, and detection steps

Application owners and infrastructure teams are likely responsible for addressing this critical vulnerability in Azure Application Gateway, which could allow network-based privilege escalation. The first step is to confirm the presence and reachability of the affected Application Gateway instances, identify their accountable owners, and then prioritize remediation based on business criticality and potential exposure.

  • Confirm accountable application owners.
  • Verify network reachability and criticality.
  • Plan remediation based on risk assessment.

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 Application Gateway?

It is a web traffic load balancer that manages how traffic enters an application. It acts as an edge service, routing requests to various backend resources while handling security and performance duties for cloud-hosted environments.

What does this CVE-2025-64656 vulnerability mean?

This is an out-of-bounds read, classified as CWE-125. It occurs when software accesses memory outside of its intended buffer. In this case, the flaw lets an unauthorized attacker read sensitive data, which can be leveraged to gain higher privileges within the system.

How can an attacker trigger this vulnerability?

An attacker initiates this by sending specially crafted network requests directly to the gateway. The vulnerability does not require authentication or user interaction to occur, but it cannot be triggered by requests that are not specifically engineered to exploit the memory read error.

Is my environment at risk from this CVE?

Halo Surface Signal indicates that because Azure Application Gateway is designed as an internet-facing edge service, it is highly likely to be reachable by external traffic. If your instances are exposed to the internet, they are prime candidates for this attack.

What should I do first to manage this risk?

Start by identifying all deployed Application Gateway instances and verifying which ones are exposed to the internet. Locate the responsible application owners for these assets to coordinate a review of your current network configuration and apply necessary updates.

References