Skip to content

[Snyk] Security upgrade node-sass from 6.0.1 to 9.0.0 #27

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
karimkawambwa wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Security upgrade node-sass from 6.0.1 to 9.0.0 #27

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@
"compression-webpack-plugin": "9",
"css-loader": "^6.2.0",
"mini-css-extract-plugin": "^2.1.0",
"node-sass": "^6.0.1",
"node-sass": "^9.0.0",
Copy link
Copy Markdown

@sentry sentry bot Jan 25, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The yarn.lock file was not updated, so the old, vulnerable version of node-sass will be installed, and the security fix will not be applied.
Severity: MEDIUM

Suggested Fix

Run yarn install or yarn upgrade node-sass locally to regenerate the yarn.lock file with the correct dependency version (^9.0.0) and commit the updated file. This will ensure the intended version is installed during builds.

Prompt for AI Agent 
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L17

Potential issue: The `package.json` file was updated to use `node-sass` version `^9.0.0`
to address a security vulnerability. However, the `yarn.lock` file was not updated and
still specifies version `^6.0.1`. When `yarn install` is run, it will prioritize the
lockfile and install the older, vulnerable version of `node-sass`. As a result, the
intended security fix will not be applied, and the project will remain exposed to the
vulnerability the pull request was meant to resolve.

Did we get this right? 👍 / 👎 to inform future reviews.

"postcss": "^8.3.6",
"postcss-import": "^14.0.2",
"postcss-loader": "^6.1.1",
Expand Down