Doesn't upgrading next to latest ( 15.3.2 ) resolve babel vulnerability, why does it still show? | Next.js | Page 1

modern comet May 27, 2025, 6:18 PM

#

I've been trying to resolve this vulnerability for a while ow and can seem to get it done.

Ive tried upgrading next, and overriding babel in package.json to 7.26.10. However, it still seems to show the vulnerability is not resolved.

lavish badgeBOT May 27, 2025, 6:18 PM

#

Post created!

🔎 This post has been indexed in our web forum and will be seen by search engines so other users can find it outside Discord

🕵️ Your user profile is private by default and won't be visible to users outside Discord, if you want to be visible in the web forum you can add the "Public Profile" role in id:customize

✅ You can mark a message as the answer for your post with Right click -> Apps -> Mark Solution
(if you don't see the option, try refreshing Discord with Ctrl + R)

modern comet May 27, 2025, 6:47 PM

#

I see the correct version in the standalone build but the incorrect version still persists

#Doesn't upgrading next to latest ( 15.3.2 ) resolve babel vulnerability, why does it still show?