GHSA-m5vv-6r4h-3vj9 is a medium-severity (CVSS 5.5) CWE-362 vulnerability in github.com/Azure/azure-sdk-for-go/sdk/azidentity. A fix is available for github.com/Azure/azure-sdk-for-go/sdk/azidentity — see the affected versions and patch details below.
Azure Identity Libraries and Microsoft Authentication Library Elevation of Privilege Vulnerability
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-m5vv-6r4h-3vj9.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-m5vv-6r4h-3vj9 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 376,715 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/Azure/azure-sdk-for-go/sdk/azidentity☕com.azure:azure-identity☕com.microsoft.azure:msal4j📦@azure/identity📦@azure/msal-node.NETMicrosoft.Identity.Client.NETAzure.Identity.NETMicrosoft.Identity.Client+1 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go, Maven packages — download data is not available via public APIs for these ecosystems.
Description
Azure Identity Libraries and Microsoft Authentication Library Elevation of Privilege Vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/Azure/azure-sdk-for-go/sdk/azidentity | all versions | 1.6.0-beta.4.0.20240610221955-50774cd97099go get github.com/Azure/azure-sdk-for-go/sdk/azidentity@v1.6.0-beta.4.0.20240610221955-50774cd97099 |
| ☕Maven | com.azure:azure-identity | all versions | 1.12.2com.azure:azure-identity:1.12.2 |
| ☕Maven | com.microsoft.azure:msal4j | ≥ 1.14.4-beta&&< 1.15.1 | 1.15.1com.microsoft.azure:msal4j:1.15.1 |
| 📦npm | @azure/identity | all versions | 4.2.1npm install @azure/identity@4.2.1 |
| 📦npm | @azure/msal-node | ≥ 2.7.0&&< 2.9.2 | 2.9.2npm install @azure/msal-node@2.9.2 |
| .NETNuGet | Microsoft.Identity.Client | ≥ 4.49.1&&< 4.60.4 | 4.60.4dotnet add package Microsoft.Identity.Client --version 4.60.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/Azure/azure-sdk-for-go/sdk/azidentity, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/Azure/azure-sdk-for-go/sdk/azidentity to 1.6.0-beta.4.0.20240610221955-50774cd97099 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m5vv-6r4h-3vj9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-m5vv-6r4h-3vj9 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-m5vv-6r4h-3vj9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Red Hat build of Apache Camel for Spring boot is not affected as 4.4.1 was released containing a fixed version of the Azure Identity Library.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat build of Apache Camel 4 for Quarkus 3 | azure-identity | RHSA-2024:7052 |
| Red Hat Developer Hub 1.3 on RHEL 9 | rhdh/rhdh-hub-rhel9:1.3-100 | RHBA-2024:7523 |
| cert-manager operator for Red Hat OpenShift 1.15 | cert-manager/jetstack-cert-manager-acmesolver-rhel9:v1.15.4 | RHSA-2025:0536 |
Frequently Asked Questions
Is GHSA-m5vv-6r4h-3vj9 in your dependencies?
O3 Security finds GHSA-m5vv-6r4h-3vj9 across Go, Maven, npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.