Skip to content

[Snyk] Fix for 2 vulnerabilities#11823

Closed
q1blue wants to merge 2 commits intomasterfrom
snyk-fix-ed58825b6ace285318bdb55f88e39bc5
Closed

[Snyk] Fix for 2 vulnerabilities#11823
q1blue wants to merge 2 commits intomasterfrom
snyk-fix-ed58825b6ace285318bdb55f88e39bc5

Conversation

@q1blue
Copy link
Copy Markdown
Collaborator

@q1blue q1blue commented Feb 7, 2026

snyk-top-banner

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

Snyk changed the following file(s):

  • packages/backend-app-api/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
  84  
low severity Server-side Request Forgery (SSRF)
SNYK-JS-WEBPACK-15235969
  84  

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:

🦉 Server-side Request Forgery (SSRF)


EntelligenceAI PR Summary

This PR transitions backend-app-api dependencies from workspace protocol to explicit version pinning for improved version control and publication readiness.

  • Updated @backstage/backend-common to version 0.24.1
  • Updated @backstage/backend-plugin-api to version 0.1.0
  • Updated @backstage/config-loader to version 0.1.1
  • Updated @backstage/plugin-permission-node to version 0.1.0
  • Changes made in packages/backend-app-api/package.json

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Feb 7, 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, addresses critical security concerns by updating key Backstage dependencies. The primary goal is to mitigate two Server-side Request Forgery (SSRF) vulnerabilities, thereby enhancing the overall security posture of the application. The changes are confined to the package.json file, specifying exact versions for previously workspace-linked dependencies.

Highlights

  • Dependency Updates: Several @backstage dependencies in packages/backend-app-api/package.json have been updated from workspace:^ to specific versions: @backstage/backend-common to 0.24.1, @backstage/backend-plugin-api to 0.1.0, @backstage/config-loader to 0.1.1, and @backstage/plugin-permission-node to 0.1.0.
  • Vulnerability Fixes: These dependency upgrades are intended to resolve two low-severity Server-side Request Forgery (SSRF) vulnerabilities, identified as SNYK-JS-WEBPACK-15235959 and SNYK-JS-WEBPACK-15235969, which had a score of 84 each.
Changelog
  • packages/backend-app-api/package.json
    • Updated @backstage/backend-common from workspace:^ to 0.24.1.
    • Updated @backstage/backend-plugin-api from workspace:^ to 0.1.0.
    • Updated @backstage/config-loader from workspace:^ to 0.1.1.
    • Updated @backstage/plugin-permission-node from workspace:^ to 0.1.0.
Activity
  • This pull request was automatically created by Snyk to fix reported vulnerabilities.
  • The yarn.lock file was not updated by Snyk, requiring manual intervention before merging.
  • The PR aims to fix two low-severity Server-side Request Forgery (SSRF) vulnerabilities.
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 7, 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.

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

Walkthrough

This pull request updates the dependency management strategy for the backend-app-api package by replacing workspace protocol references with explicit version numbers for four core Backstage dependencies. The changes affect @backstage/backend-common (0.24.1), @backstage/backend-plugin-api (0.1.0), @backstage/config-loader (0.1.1), and @backstage/plugin-node (0.1.0). This transition from workspace-based resolution to pinned versions suggests preparation for package publication or the establishment of stricter version control for these critical backend dependencies, ensuring reproducible builds and explicit dependency tracking outside of the monorepo context.

Changes

File(s) Summary
packages/backend-app-api/package.json Replaced workspace protocol references with explicit version numbers for four Backstage dependencies: @backstage/backend-common (0.24.1), @backstage/backend-plugin-api (0.1.0), @backstage/config-loader (0.1.1), and @backstage/plugin-permission-node (0.1.0).

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant App as backend-app-api
    participant PM as Package Manager
    participant WS as Workspace Packages
    participant NPM as NPM Registry
    
    Note over App,NPM: Before: Using workspace protocol
    
    App->>PM: Resolve dependencies
    PM->>WS: Request @backstage/backend-common (workspace:^)
    WS-->>PM: Return local workspace version
    PM->>WS: Request @backstage/backend-plugin-api (workspace:^)
    WS-->>PM: Return local workspace version
    PM->>WS: Request @backstage/config-loader (workspace:^)
    WS-->>PM: Return local workspace version
    PM->>WS: Request @backstage/plugin-permission-node (workspace:^)
    WS-->>PM: Return local workspace version
    PM-->>App: Dependencies resolved from workspace
    
    Note over App,NPM: After: Using fixed versions
    
    App->>PM: Resolve dependencies
    PM->>NPM: Request @backstage/backend-common@0.24.1
    NPM-->>PM: Return published version 0.24.1
    PM->>NPM: Request @backstage/backend-plugin-api@0.1.0
    NPM-->>PM: Return published version 0.1.0
    PM->>NPM: Request @backstage/config-loader@0.1.1
    NPM-->>PM: Return published version 0.1.1
    PM->>NPM: Request @backstage/plugin-permission-node@0.1.0
    NPM-->>PM: Return published version 0.1.0
    PM-->>App: Dependencies resolved from registry
Loading

▶️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.

@socket-security
Copy link
Copy Markdown

socket-security Bot commented Feb 7, 2026

@socket-security
Copy link
Copy Markdown

socket-security Bot commented Feb 7, 2026

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
License policy violation: npm typescript under W3C-20150513

License: W3C-20150513 - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: LicenseRef-W3C-Community-Final-Specification-Agreement - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: MIT-Khronos-old - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

From: ?npm/@microsoft/api-extractor@7.33.7npm/typescript@4.8.4

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/typescript@4.8.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

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 pull request, automatically generated by Snyk, aims to resolve two Server-side Request Forgery (SSRF) vulnerabilities by updating dependencies. However, the proposed changes are highly problematic and will likely break the application. The PR modifies packages/backend-app-api/package.json to replace workspace:^ dependencies with specific published versions. Critically, for several packages like @backstage/backend-plugin-api and @backstage/config-loader, the specified versions are major downgrades from the versions currently in the workspace. This will almost certainly introduce breaking changes. Furthermore, as noted in the PR description, the yarn.lock file has not been updated, which means these changes would not take effect and the vulnerabilities would persist even if this PR were merged. Due to the high risk of breaking the application, these changes should not be merged as-is. It is recommended to close this PR and investigate a proper upgrade path for the vulnerable transitive dependencies.

Comment on lines +35 to +43
"@backstage/backend-common": "0.24.1",
"@backstage/backend-plugin-api": "0.1.0",
"@backstage/backend-tasks": "workspace:^",
"@backstage/cli-common": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/config-loader": "workspace:^",
"@backstage/config-loader": "0.1.1",
"@backstage/errors": "workspace:^",
"@backstage/plugin-auth-node": "workspace:^",
"@backstage/plugin-permission-node": "workspace:^",
"@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.

critical

The proposed dependency changes are highly likely to break the application by downgrading core packages to incompatible older versions.

Specifically:

  • @backstage/backend-plugin-api is being downgraded from the workspace version 0.5.5-next.0 to 0.1.0.
  • @backstage/config-loader is being downgraded from the workspace version 1.4.0-next.0 to 0.1.1.

Such major downgrades will introduce breaking API changes and cause build failures or runtime errors. Additionally, changing from workspace:^ to pinned versions detaches this package from the monorepo's dependency management, which can lead to inconsistencies.

It is recommended to revert these changes and find a safe upgrade path to resolve the vulnerabilities.

Suggested change
"@backstage/backend-common": "0.24.1",
"@backstage/backend-plugin-api": "0.1.0",
"@backstage/backend-tasks": "workspace:^",
"@backstage/cli-common": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/config-loader": "workspace:^",
"@backstage/config-loader": "0.1.1",
"@backstage/errors": "workspace:^",
"@backstage/plugin-auth-node": "workspace:^",
"@backstage/plugin-permission-node": "workspace:^",
"@backstage/plugin-permission-node": "0.1.0",
"@backstage/backend-common": "workspace:^",
"@backstage/backend-plugin-api": "workspace:^",
"@backstage/backend-tasks": "workspace:^",
"@backstage/cli-common": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/config-loader": "workspace:^",
"@backstage/errors": "workspace:^",
"@backstage/plugin-auth-node": "workspace:^",
"@backstage/plugin-permission-node": "workspace:^",

@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 14, 2026
@github-actions github-actions Bot closed this Mar 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants