CVE-2025-21384

CVE-2025-21384 is a high-severity vulnerability in Microsoft Azure Health Bot with a CVSS 3.x base score of 8.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-918.

Key facts

Description

An authenticated attacker can exploit an Server-Side Request Forgery (SSRF) vulnerability in Microsoft Azure Health Bot to elevate privileges over a network.

Frequently asked questions

What is CVE-2025-21384?
An authenticated attacker can exploit an Server-Side Request Forgery (SSRF) vulnerability in Microsoft Azure Health Bot to elevate privileges over a network.
How severe is CVE-2025-21384?
CVE-2025-21384 has a CVSS 3.x base score of 8.3, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability low.
Is CVE-2025-21384 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (47th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-21384?
CVE-2025-21384 affects Microsoft Azure Health Bot. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-21384?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-21384 have an EU (EUVD) identifier?
Yes. CVE-2025-21384 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-9061.
When was CVE-2025-21384 published?
CVE-2025-21384 was published on 2025-04-01 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Microsoft Azure Health Bot

All CVEs affecting Microsoft Azure Health Bot →

Other CWE-918 (Server-Side Request Forgery (SSRF)) vulnerabilities

Browse all CWE-918 (Server-Side Request Forgery (SSRF)) vulnerabilities →