This might be a false positive, but requirements.txt around line 16 looked worth a second pair of eyes.
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).
Something like this might fix it:
--- a/requirements.txt
+++ b/requirements.txt
@@ -16 +16 @@
-transformers==4.36.0
+transformers==4.48.0
# Alternative: allow future security patch releases while constraining the major version:
# transformers>=4.48.0,<5.0.0
# Then update and verify:
# pip install -r requirements.txt --upgrade
# pip-audit -r requirements.txt (or re-run Trivy/Trivy-based scan)
# pytest # validate model-loading and inference code against the new version
For reference: rule CVE-2024-11392. Rated high.
I do not maintain this project, so I may well be missing context — if this is intentional or already handled elsewhere, please just close it.
Found with automated scanning (RedGem) and reviewed before opening. If it is not useful, closing it is completely fine.
This might be a false positive, but
requirements.txtaround line 16 looked worth a second pair of eyes.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).
Something like this might fix it:
For reference: rule
CVE-2024-11392. Rated high.I do not maintain this project, so I may well be missing context — if this is intentional or already handled elsewhere, please just close it.
Found with automated scanning (RedGem) and reviewed before opening. If it is not useful, closing it is completely fine.