Skip to content

[Snyk] Fix for 2 vulnerabilities#11807

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

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

Conversation

@q1blue
Copy link
Copy Markdown
Collaborator

@q1blue q1blue commented Feb 6, 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):

  • plugins/search-backend-module-elasticsearch/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 locks Backstage dependencies to specific versions in the Elasticsearch search backend module package configuration.

  • Changed @backstage/backend-plugin-api from workspace protocol to pinned version 0.6.19
  • Changed @backstage/plugin-search-common from workspace protocol to pinned version 0.3.1
  • Replaces monorepo workspace resolution with explicit version pinning
  • Likely preparation for external package publication or version compatibility requirements

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Feb 6, 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, focuses on improving the project's security by upgrading specific dependencies. The primary objective is to resolve two identified Server-side Request Forgery (SSRF) vulnerabilities through targeted package version updates, ensuring a more secure application environment.

Highlights

  • Dependency Updates for Security: Updated @backstage/backend-plugin-api to 0.6.19 and @backstage/plugin-search-common to 0.3.1 in plugins/search-backend-module-elasticsearch/package.json to address two Server-side Request Forgery (SSRF) vulnerabilities.
Changelog
  • plugins/search-backend-module-elasticsearch/package.json
    • Updated @backstage/backend-plugin-api from workspace:^ to 0.6.19.
    • Updated @backstage/plugin-search-common from workspace:^ to 0.3.1.
Activity
  • This pull request was automatically created by Snyk to address identified vulnerabilities.
  • A warning was noted indicating that the yarn.lock file failed to update and requires manual intervention before merging.
  • The PR aims to fix two 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 6, 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 PR updates dependency management for the Elasticsearch search backend module by replacing workspace protocol references with pinned versions for two Backstage packages. The @backstage/backend-plugin-api dependency is now locked to version 0.6.19 and @backstage/plugin-search-common to version 0.3.1. This transition from workspace-based resolution to explicit version pinning suggests the package is being prepared for standalone distribution outside the monorepo or addresses specific version compatibility requirements that necessitate fixed dependency versions.

Changes

File(s) Summary
plugins/search-backend-module-elasticsearch/package.json Updated dependency specifications from workspace protocol to pinned versions: @backstage/backend-plugin-api to 0.6.19 and @backstage/plugin-search-common to 0.3.1.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant Reg as Registry
    participant Module as search-backend-module-elasticsearch

    Dev->>PM: npm install / yarn install
    PM->>Module: Read package.json
    Note over Module: Dependencies now pinned:<br/>backend-plugin-api: 0.6.19<br/>plugin-search-common: 0.3.1
    PM->>Reg: Fetch @backstage/backend-plugin-api@0.6.19
    Reg-->>PM: Return package
    PM->>Reg: Fetch @backstage/plugin-search-common@0.3.1
    Reg-->>PM: Return package
    PM->>Reg: Fetch other workspace dependencies
    Reg-->>PM: Return packages
    PM->>Module: Install all dependencies
    PM-->>Dev: Installation complete
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.

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 aims to address two Server-side Request Forgery (SSRF) vulnerabilities by updating the @backstage/backend-plugin-api and @backstage/plugin-search-common dependencies. While the package.json has been updated, it is crucial to ensure the yarn.lock file is also updated to reflect these changes, as indicated in the pull request description. Failure to update the lock file could lead to inconsistent dependency resolution and potentially leave the vulnerabilities unaddressed in certain environments.

"dependencies": {
"@backstage/backend-common": "workspace:^",
"@backstage/backend-plugin-api": "workspace:^",
"@backstage/backend-plugin-api": "0.6.19",
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 pull request description indicates that the yarn.lock file failed to update. It is critical to manually update yarn.lock to ensure these dependency upgrades are consistently applied across all environments and that the identified SSRF vulnerabilities are fully mitigated. Without an updated lock file, builds might still use older, vulnerable versions of these packages.

@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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants