Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
MEDIUM severity

Segfault while copying constant resource tensorGHSA-786j-5qwq-r36x

MEDIUMFix: tensorflow/tensorflow@7731e8d

GHSA-786j-5qwq-r36x is a medium-severity (CVSS 5.5) CWE-824 vulnerability in tensorflow. A fix is available for tensorflow — see the affected versions and patch details below.

Also known asBIT-tensorflow-2021-41204CVE-2021-41204PYSEC-2021-397PYSEC-2021-614PYSEC-2021-812
Published
Updated
Affected
9 pkgs
Patched
9 / 9
Exploits
None indexed
Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs3th percentile — riskier than 3% of all scored CVEsHighest risk
0.00%0.21%0.43%0.64%0.1%0.1%Sep 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-786j-5qwq-r36x by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

9 pkgs affected
🐍tensorflow🐍tensorflow🐍tensorflow🐍tensorflow-cpu🐍tensorflow-cpu🐍tensorflow-cpu🐍tensorflow-gpu🐍tensorflow-gpu+1 more

Real-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

During TensorFlow's Grappler optimizer phase, constant folding might attempt to deep copy a resource tensor. This results in a segfault, as these tensors are supposed to not change.

Patches

We have patched the issue in GitHub commit 7731e8dfbe4a56773be5dc94d631611211156659.

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

Affected Packages

9 total 9 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPItensorflow≥ 2.6.0&&< 2.6.12.6.1pip install --upgrade 'tensorflow==2.6.1'
🐍PyPItensorflow≥ 2.5.0&&< 2.5.22.5.2pip install --upgrade 'tensorflow==2.5.2'
🐍PyPItensorflowall versions2.4.4pip install --upgrade 'tensorflow==2.4.4'
🐍PyPItensorflow-cpu≥ 2.6.0&&< 2.6.12.6.1pip install --upgrade 'tensorflow-cpu==2.6.1'
🐍PyPItensorflow-cpu≥ 2.5.0&&< 2.5.22.5.2pip install --upgrade 'tensorflow-cpu==2.5.2'
🐍PyPItensorflow-cpuall versions2.4.4pip install --upgrade 'tensorflow-cpu==2.4.4'

Affected Products

1 product · 3 configurations
Application
tensorflowgoogle
≥ 2.6.0 && < 2.6.1
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    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.

  2. Fix

    Update tensorflow to 2.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-786j-5qwq-r36x is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact During TensorFlow's Grappler optimizer phase, constant folding might attempt to deep copy a resource tensor. This results in a segfault, as these tensors are supposed to not change. ### Patches We have patched the issue in GitHub commit [7731e8dfbe4a56773be5dc94d631611211156659](https://github.com/tensorflow/tensorflow/commit/7731e8dfbe4a56773be5dc94d631611211156659). 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 mor
O3 Security · Impact-Aware SCA

Is GHSA-786j-5qwq-r36x in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
Segfault while copying constant resource tensor