Fix possible fix(deps): 5 vulnerable dependencies in requirements.txt - #3
Open
begininvoke wants to merge 1 commit into
Open
Fix possible fix(deps): 5 vulnerable dependencies in requirements.txt#3begininvoke wants to merge 1 commit into
begininvoke wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Small change to
requirements.txt— a scan flagged the code below and it looked genuine. It is around line 16.CVE-2024-11392 (HIGH, ZDI-CAN-24322): The pinned transformers==4.36.0 in requirements.txt is vulnerable to remote code execution via unsafe deserialization of untrusted data in the handling of MobileViTV2 configuration files. An attacker can craft a malicious configuration/checkpoint file; when a victim loads it (exploitation requires user interaction, e.g., opening a malicious file or visiting a malicious page), insufficient validation of user-supplied data triggers deserialization of untrusted data, allowing arbitrary code execution in the context of the current user. Impact is severe for any workflow that loads models, configs, or checkpoints from external/untrusted sources (user uploads, public model hubs, CI pipelines fetching artifacts). Severity: HIGH (RCE with only user interaction required). Fixed in transformers 4.48.0. Recommended action: upgrade immediately, audit code paths that deserialize externally supplied configs, and re-scan after the upgrade. Note: 4.36 -> 4.48 spans several minor releases, so run the test suite for API compatibility (breaking changes are possible in model APIs and tokenizers).
Upgrade transformers to version 5.5.0 to address multiple high‑severity CVEs (CVE‑2024‑11392, CVE‑2024‑11393, CVE‑2024‑11394, CVE‑2026‑4372, CVE‑2026‑5241).
For reference: rule
CVE-2024-11392. Rated high.Take or leave whichever parts are useful. If this is not the right approach, closing is fine.
Found with automated scanning (RedGem) and reviewed before opening. If it is not useful, closing it is completely fine.