Skip to content

[Snyk] Fix for 2 vulnerabilities#12327

Closed
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-5a01c458f1911c571bc3f0c22899e773
Closed

[Snyk] Fix for 2 vulnerabilities#12327
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-5a01c458f1911c571bc3f0c22899e773

Conversation

@q1blue
Copy link
Copy Markdown
Collaborator

@q1blue q1blue commented Feb 14, 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/graphql-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
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-AJV-15274295
  157  
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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Allocation of Resources Without Limits or Throttling


EntelligenceAI PR Summary

This PR upgrades dependencies in the GraphQL backend plugin for improved security, stability, and version consistency.

  • Upgraded Apollo Server from v4 to v5.4.0 (major version change)
  • Updated Express from v4.17.1 to v4.22.0 for security and stability improvements
  • Pinned @backstage/backend-common, @backstage/config, and @backstage/plugin-catalog-graphql to specific versions
  • Replaced workspace protocol references with explicit version numbers for Backstage dependencies

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Feb 14, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@snyk-io
Copy link
Copy Markdown

snyk-io Bot commented Feb 14, 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.

@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 resolving two identified vulnerabilities. It achieves this by upgrading several core dependencies to their latest secure versions, thereby mitigating risks associated with Regular Expression Denial of Service and resource allocation without limits.

Highlights

  • Security Vulnerability Fixes: This PR addresses two critical vulnerabilities: a high-severity Regular Expression Denial of Service (ReDoS) (SNYK-JS-AJV-15274295) and a medium-severity Allocation of Resources Without Limits or Throttling (SNYK-JS-QS-15268416).
  • Dependency Upgrades: Key dependencies including @apollo/server, @backstage/backend-common, @backstage/config, @backstage/plugin-catalog-graphql, and express have been upgraded to their latest versions to remediate the identified security issues.
  • Yarn Zero-Install Consideration: Users leveraging Yarn's zero-install feature are advised that the .yarn/cache/ directory will require a manual yarn command execution to update its contents.
  • Manual yarn.lock Update Required: The automated process failed to update the yarn.lock file, necessitating a manual update before merging.
Changelog
  • plugins/graphql-backend/package.json
    • Updated @apollo/server from ^4.0.0 to ^5.4.0.
    • Updated @backstage/backend-common from workspace:^ to 0.24.1.
    • Updated @backstage/config from workspace:^ to 0.1.1.
    • Updated @backstage/plugin-catalog-graphql from workspace:^ to 0.1.1.
    • Updated express from ^4.17.1 to ^4.22.0.
Activity
  • Automatically created by Snyk to propose fixes for two security vulnerabilities.
  • Noted that the yarn.lock file failed to update automatically and requires manual intervention.
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.

@socket-security
Copy link
Copy Markdown

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 argparse under Python-2.0.1

License: Python-2.0.1 - the applicable license policy does not allow this license (4) (package/LICENSE)

From: ?npm/js-yaml@4.1.0npm/argparse@2.0.1

ℹ 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/argparse@2.0.1. 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.

Warn High
License policy violation: npm caniuse-lite under CC-BY-4.0

License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (npm metadata)

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

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

From: ?npm/@docusaurus/core@0.0.0-5591npm/@docusaurus/plugin-client-redirects@0.0.0-5591npm/@docusaurus/preset-classic@0.0.0-5591npm/caniuse-lite@1.0.30001481

ℹ 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/caniuse-lite@1.0.30001481. 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.

Warn High
Obfuscated code: npm entities is 91.0% likely obfuscated

Confidence: 0.91

Location: Package overview

From: ?npm/@docusaurus/core@0.0.0-5591npm/@docusaurus/plugin-client-redirects@0.0.0-5591npm/@docusaurus/preset-classic@0.0.0-5591npm/entities@4.4.0

ℹ Read more on: This package | This alert | What is obfuscated code?

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: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@4.4.0. 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

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

Walkthrough

This PR updates critical dependencies in the GraphQL backend plugin, focusing on major version upgrades and dependency management improvements. The most significant change is upgrading Apollo Server from v4 to v5.4.0, which represents a major version bump that may introduce breaking changes and new features. Express is updated from v4.17.1 to v4.22.0 to incorporate security patches and stability improvements. Additionally, three Backstage internal dependencies are transitioned from workspace protocol references to pinned specific versions, ensuring consistent and predictable versioning across different deployment environments.

Changes

File(s) Summary
plugins/graphql-backend/package.json Upgraded Apollo Server from v4 to v5.4.0 (major version bump), updated Express from v4.17.1 to v4.22.0, and pinned three Backstage internal dependencies (@backstage/backend-common, @backstage/config, @backstage/plugin-catalog-graphql) to specific versions instead of workspace protocol references.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Client
    participant Express as Express Router<br/>(v4.17.1 → v4.22.0)
    participant GraphQLBackend as GraphQL Backend Plugin
    participant ApolloServer as Apollo Server<br/>(v4.0.0 → v5.4.0)
    participant CatalogGraphQL as Catalog GraphQL Plugin<br/>(workspace → v0.1.1)
    participant BackendCommon as Backend Common<br/>(workspace → v0.24.1)
    participant Config as Config Service<br/>(workspace → v0.1.1)

    Note over Client,Config: Dependency Version Updates Only<br/>No Code Logic Changes

    Client->>Express: HTTP GraphQL Request
    Express->>GraphQLBackend: Route to GraphQL endpoint
    GraphQLBackend->>Config: Load configuration
    Config-->>GraphQLBackend: Config data
    GraphQLBackend->>ApolloServer: Initialize with schema
    GraphQLBackend->>CatalogGraphQL: Get catalog schema modules
    CatalogGraphQL-->>GraphQLBackend: Schema definitions
    GraphQLBackend->>ApolloServer: Register schema & resolvers
    ApolloServer->>BackendCommon: Use common backend utilities
    ApolloServer-->>GraphQLBackend: Server ready
    GraphQLBackend->>ApolloServer: Execute GraphQL query
    ApolloServer-->>GraphQLBackend: Query results
    GraphQLBackend-->>Express: Response data
    Express-->>Client: HTTP Response

    Note over ApolloServer: Major version upgrade<br/>may include breaking changes
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 from Snyk aims to fix two security vulnerabilities by updating dependencies. While updating dependencies is important, the current changes introduce critical issues by incorrectly handling yarn workspace dependencies. Specifically, it replaces workspace:^ references with pinned versions, and in some cases, these are significant downgrades (@backstage/config from 1.0.8 to 0.1.1, and @backstage/plugin-catalog-graphql from ~0.3.22 to 0.1.1). This will almost certainly break the application. Additionally, the PR description notes that yarn.lock was not updated, which is another sign of problems with the automated update process. The changes to @backstage dependencies should be reverted, and the upgrade should be performed manually to ensure workspace integrity and correct version resolution. The update of @apollo/server to a new major version (^5.4.0) should also be tested carefully for breaking changes.

Comment on lines +37 to +39
"@backstage/backend-common": "0.24.1",
"@backstage/config": "0.1.1",
"@backstage/plugin-catalog-graphql": "0.1.1",
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

These changes incorrectly replace workspace:^ dependencies with pinned versions, leading to significant and breaking downgrades for several packages. This approach is not suitable for a monorepo and will likely break the application.

  • @backstage/config is downgraded from 1.0.8 to 0.1.1.
  • @backstage/plugin-catalog-graphql is downgraded from ~0.3.22 to 0.1.1.

Please revert these changes to use the workspace:^ protocol. The underlying vulnerabilities should be addressed by updating the packages within the workspace correctly, not by pinning to incorrect and outdated versions.

    "@backstage/backend-common": "workspace:^",
    "@backstage/config": "workspace:^",
    "@backstage/plugin-catalog-graphql": "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 21, 2026
@github-actions github-actions Bot closed this Feb 28, 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