Skip to content

Comments

[Snyk] Security upgrade protobuf from 4.24.4 to 6.33.5#60

Open
pratham-aggr wants to merge 1 commit intomainfrom
snyk-fix-04fd26351527efe5b40389a79edde872
Open

[Snyk] Security upgrade protobuf from 4.24.4 to 6.33.5#60
pratham-aggr wants to merge 1 commit intomainfrom
snyk-fix-04fd26351527efe5b40389a79edde872

Conversation

@pratham-aggr
Copy link
Owner

@pratham-aggr pratham-aggr commented Jan 31, 2026

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

  • backend-api/requirements.txt
⚠️ Warning
yfinance 0.2.65 requires protobuf, which is not installed.
yfinance 0.2.65 requires curl-cffi, which is not installed.
yfinance 0.2.65 requires websockets, which is not installed.

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.
  • Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.


Note

Low Risk
Single dependency constraint change; low risk aside from potential upstream incompatibility with packages that expect older protobuf versions.

Overview
Pins protobuf to >=6.33.5 in backend-api/requirements.txt to address a Snyk-reported vulnerability (even though it’s an indirect dependency, e.g., via yfinance).

Written by Cursor Bugbot for commit 5a13c98. This will update automatically on new commits. Configure here.

The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-PROTOBUF-15090738
@vercel
Copy link

vercel bot commented Jan 31, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
quantflow Error Error Jan 31, 2026 7:08am

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

This PR is being reviewed by Cursor Bugbot

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

matplotlib==3.7.2
seaborn==0.12.2
websockets>=13.0
protobuf>=6.33.5 # not directly required, pinned by Snyk to avoid a vulnerability
Copy link

Choose a reason for hiding this comment

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

Major protobuf version upgrade may break yfinance compatibility

Medium Severity

The upgrade from protobuf 4.24.4 to 6.33.5 represents a 2-major-version jump that may introduce compatibility issues with yfinance==0.2.65, which depends on protobuf. The Snyk warning in the PR description indicates potential dependency concerns. This codebase heavily uses yfinance for market data fetching. If yfinance has an upper-bound version constraint on protobuf (e.g., <5.0), this change could cause dependency resolution failures or runtime errors. This compatibility should be verified before merging.

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants