Skip to content

Conversation

@josephch405
Copy link

@josephch405 josephch405 requested review from a team as code owners December 4, 2025 23:24
@josephch405
Copy link
Author

@microsoft-github-policy-service agree

@MakakWasTaken
Copy link

This would fix the issue, as it would force the version to be higher than 9.0.2, which is the version that causes the error. However "^9.0.0" does also resolve to 9.0.3. So to fix it for now, just remove the @azure/msal-node package and then add it again afterwards. This should make it resolve to the new 9.0.3 version which fixes this vulnerability.

I am using yarn, so to do this it would be:
yarn remove @azure/msal-node
and then
yarn add @azure/msal-node.

I am not sure if the upgrade command will have the same effect, but it might if you explicitly tell it to upgrade @azure/msal-node.

Hope this helps :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants