CVE-2021-41228 is a high-severity (CVSS 7.8) OS Command Injection vulnerability in tensorflow. 1 public exploit reference exists, so weaponization risk is real. A fix is available for tensorflow — see the affected versions and patch details below.
Code injection in `saved_model_cli`
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2021-41228 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
tensorflow🐍tensorflow🐍tensorflow🐍tensorflow-cpu🐍tensorflow-cpu🐍tensorflow-cpu🐍tensorflow-gpu🐍tensorflow-gpu+1 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Impact
TensorFlow's saved_model_cli tool is vulnerable to a code injection as it calls eval on user supplied strings
def preprocess_input_exprs_arg_string(input_exprs_str):
...
for input_raw in filter(bool, input_exprs_str.split(';')):
...
input_key, expr = input_raw.split('=', 1)
input_dict[input_key] = eval(expr)
...
This can be used by attackers to run arbitrary code on the plaform where the CLI tool runs.
However, given that the tool is always run manually, the impact of this is not severe. We have patched this by adding a safe flag which defaults to True and an explicit warning for users.
Patches
We have patched the issue in GitHub commit 8b202f08d52e8206af2bdb2112a62fafbc546ec7.
The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
For more information
Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.
Attribution
This vulnerability has been reported by Omer Kaspi from Vdoo.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | tensorflow | ≥ 2.5.0&&< 2.5.2 | 2.5.2pip install --upgrade 'tensorflow==2.5.2' |
| 🐍PyPI | tensorflow | all versions | 2.4.4pip install --upgrade 'tensorflow==2.4.4' |
| 🐍PyPI | tensorflow | ≥ 2.6.0&&< 2.6.1 | 2.6.1pip install --upgrade 'tensorflow==2.6.1' |
| 🐍PyPI | tensorflow-cpu | ≥ 2.5.0&&< 2.5.2 | 2.5.2pip install --upgrade 'tensorflow-cpu==2.5.2' |
| 🐍PyPI | tensorflow-cpu | all versions | 2.4.4pip install --upgrade 'tensorflow-cpu==2.4.4' |
| 🐍PyPI | tensorflow-cpu | ≥ 2.6.0&&< 2.6.1 | 2.6.1pip install --upgrade 'tensorflow-cpu==2.6.1' |
Affected Products
tensorflowgoogleResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tensorflow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update tensorflow to 2.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-41228 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is CVE-2021-41228 in your dependencies?
Find it across PyPI, including transitive dependencies.