Read the docs
TI-2026-24709 Aliases CVE-2026-32173GHSA-85hw-hqj5-m956

Azure SRE Agent Information Disclosure Vulnerability

Priority MEDIUM 45CWE-287Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Information disclosure
Confidentiality · integrity · availability
High · None · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from Microsoft.

Summary

Improper authentication in Azure SRE Agent allows an unauthorized attacker to disclose information over a network.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00925 60th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
MicrosoftAzure SRE Agent Gateway - SignalR Hub-—No fix listedCNA
  • Azure SRE Agent Gateway - SignalR Hub VendorMicrosoft Affected - Fixed in — No fix listed CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:microsoft:azure_sre_agent:-:*:*:*:*:*:*:*not specified by NVDVulnerableMicrosoft
  • cpe:2.3:a:microsoft:azure_sre_agent:-:*:*:*:*:*:*:* Versions not specified by NVD Vulnerable ·Microsoft

Remediation

No fixed version listed by the sources yet.

Vendor assessments

Microsoft

Microsoft's page for this CVE →

Impact
Information Disclosure
Exploited
No
Publicly disclosed
No
Exploitability
—

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-32173
  2. 2026-10-03 Alias added: GHSA-85hw-hqj5-m956

References

Patch 1

  • TI-2026-69822 Missing authorization in Azure SRE Agent allows privilege elevation CVSS 3.1CRITICAL 9.6
  • TI-2026-44916 Azure SRE Agent Elevation of Privilege Vulnerability CVSS 3.1CRITICAL 9.9

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences