Skip to content

[Snyk] Fix for 3 vulnerabilities#12011

Closed
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-d6a465ce9938116f853dca911e7a6fe2
Closed

[Snyk] Fix for 3 vulnerabilities#12011
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-d6a465ce9938116f853dca911e7a6fe2

Conversation

@q1blue
Copy link
Copy Markdown
Collaborator

@q1blue q1blue commented Feb 13, 2026

snyk-top-banner

Snyk has created this PR to fix 3 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • plugins/permission-backend/package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
low severity Server-side Request Forgery (SSRF)
SNYK-JS-WEBPACK-15235959
  83  
low severity Server-side Request Forgery (SSRF)
SNYK-JS-WEBPACK-15235969
  83  
medium severity Allocation of Resources Without Limits or Throttling
SNYK-JS-QS-15268416
  62  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling
🦉 Server-side Request Forgery (SSRF)


EntelligenceAI PR Summary

This PR updates dependency version specifications in the permission-backend plugin package, transitioning from workspace references to explicit versions and upgrading Express.

  • Replaced workspace:^ protocol with explicit version numbers for five @backstage packages
  • Upgraded express dependency from ^4.17.1 to ^4.22.0
  • Changes made in plugins/permission-backend/package.json
  • Prepares package for publication or ensures consistent versioning across environments

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Feb 13, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @q1blue, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, aims to enhance the security posture of the project by resolving three critical vulnerabilities. It achieves this by updating specific package dependencies to versions that contain the necessary security patches, thereby mitigating potential risks such as Server-side Request Forgery and resource exhaustion.

Highlights

  • Vulnerability Fixes: Addressed three security vulnerabilities, including two Server-side Request Forgery (SSRF) issues (SNYK-JS-WEBPACK-15235959, SNYK-JS-WEBPACK-15235969) and one Allocation of Resources Without Limits or Throttling issue (SNYK-JS-QS-15268416), identified by Snyk.
  • Dependency Updates: Updated several package dependencies in plugins/permission-backend/package.json to their latest secure versions to remediate the identified vulnerabilities.
Changelog
  • plugins/permission-backend/package.json
    • Updated @backstage/backend-common from workspace:^ to 0.24.1.
    • Updated @backstage/backend-plugin-api from workspace:^ to 0.6.19.
    • Updated @backstage/plugin-auth-node from workspace:^ to 0.6.0.
    • Updated @backstage/plugin-permission-common from workspace:^ to 0.1.0.
    • Updated @backstage/plugin-permission-node from workspace:^ to 0.1.0.
    • Updated express from ^4.17.1 to ^4.22.0.
Activity
  • This pull request was automatically created by Snyk to propose fixes for identified vulnerabilities.
  • A warning was noted that the yarn.lock file was not updated, requiring manual intervention for projects utilizing Yarn's zero-installs feature.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@snyk-io
Copy link
Copy Markdown

snyk-io Bot commented Feb 13, 2026

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This Snyk PR updates dependencies to fix 3 vulnerabilities. While the intent is good, there are significant issues. As noted in the PR description, yarn.lock is not updated, which is critical to fix before merging to ensure dependency changes are applied correctly. Additionally, several internal packages are changed from using the workspace: protocol to being pinned to specific versions. This can break the monorepo's dependency integrity and is a significant change to the dependency strategy. I've added a comment with more details.

Comment on lines +40 to +46
"@backstage/backend-common": "0.24.1",
"@backstage/backend-plugin-api": "0.6.19",
"@backstage/config": "workspace:^",
"@backstage/errors": "workspace:^",
"@backstage/plugin-auth-node": "workspace:^",
"@backstage/plugin-permission-common": "workspace:^",
"@backstage/plugin-permission-node": "workspace:^",
"@backstage/plugin-auth-node": "0.6.0",
"@backstage/plugin-permission-common": "0.1.0",
"@backstage/plugin-permission-node": "0.1.0",
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

high

Changing these dependencies from workspace:^ to pinned versions is a significant alteration of the dependency strategy for this monorepo. The workspace: protocol is designed to ensure that packages within the monorepo use the most up-to-date local versions of each other. By pinning to specific published versions, you lose this benefit and risk introducing inconsistencies or using stale code if other packages in the monorepo are updated. It is strongly recommended to resolve the underlying vulnerabilities in a way that preserves the workspace: protocol, for instance by updating the source packages within the monorepo.

@entelligence-ai-pr-reviews
Copy link
Copy Markdown

Walkthrough

This PR updates the dependency management configuration for the permission-backend plugin package. The changes transition from workspace protocol references (workspace:^) to explicit version numbers for five Backstage packages, ensuring consistent versioning across different environments. This modification is typically performed when preparing a package for publication or distribution outside of a monorepo workspace. Additionally, the Express framework dependency is upgraded from version 4.17.1 to 4.22.0, incorporating important security patches and bug fixes that have been released in the interim versions.

Changes

File(s) Summary
plugins/permission-backend/package.json Updated five Backstage dependencies (@backstage/backend-common, @backstage/backend-plugin-api, @backstage/plugin-auth-node, @backstage/plugin-permission-common, @backstage/plugin-permission-node) from workspace protocol references to explicit version numbers; upgraded express from ^4.17.1 to ^4.22.0

▶️AI Code Reviews for VS Code, Cursor, Windsurf
Install the extension

Note for Windsurf Please change the default marketplace provider to the following in the windsurf settings:

Marketplace Extension Gallery Service URL: https://marketplace.visualstudio.com/_apis/public/gallery

Marketplace Gallery Item URL: https://marketplace.visualstudio.com/items

Entelligence.ai can learn from your feedback. Simply add 👍 / 👎 emojis to teach it your preferences. More shortcuts below

Emoji Descriptions:

  • ⚠️ Potential Issue - May require further investigation.
  • 🔒 Security Vulnerability - Fix to ensure system safety.
  • 💻 Code Improvement - Suggestions to enhance code quality.
  • 🔨 Refactor Suggestion - Recommendations for restructuring code.
  • ℹ️ Others - General comments and information.

Interact with the Bot:

  • Send a message or request using the format:
    @entelligenceai + *your message*
Example: @entelligenceai Can you suggest improvements for this code?
  • Help the Bot learn by providing feedback on its responses.
    @entelligenceai + *feedback*
Example: @entelligenceai Do not comment on `save_auth` function !

Also you can trigger various commands with the bot by doing
@entelligenceai command

The current supported commands are

  1. config - shows the current config
  2. retrigger_review - retriggers the review

More commands to be added soon.

@github-actions
Copy link
Copy Markdown

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!

@github-actions github-actions Bot added the stale label Feb 20, 2026
@github-actions github-actions Bot closed this Mar 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants