Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-hhvc-g5hv-48c6

Write to immutable memory region in TensorFlow

CVSS 4.4 MediumEPSS 0.0021 · 11th percentile

Published by the GitHub Advisory Database at 10 Dec 2020, 19:07 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
tensorflowPyPI<1.15.5 || >=2.0.0, <2.0.4 || >=2.1.0, <2.1.3 || >=2.2.0, <2.2.2 || >=2.3.0, <2.3.21.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2
tensorflow-cpuPyPI<1.15.5 || >=2.0.0, <2.0.4 || >=2.1.0, <2.1.3 || >=2.2.0, <2.2.2 || >=2.3.0, <2.3.21.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2
tensorflow-gpuPyPI<1.15.5 || >=2.0.0, <2.0.4 || >=2.1.0, <2.1.3 || >=2.2.0, <2.2.2 || >=2.3.0, <2.3.21.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2
Identifiers
GHSA-hhvc-g5hv-48c6 · BIT-tensorflow-2020-26268 · CVE-2020-26268 · PYSEC-2020-255 · PYSEC-2020-299 · PYSEC-2020-334
Weakness (CWE)
CWE-471
Tags
Published
10 Dec 2020
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions of tensorflow, tensorflow-cpu and tensorflow-gpu before 1.15.5, from 2.0.0 to before 2.0.4, from 2.1.0 to before 2.1.3, from 2.2.0 to before 2.2.2, and from 2.3.0 to before 2.3.2 are affected. An attacker who can get a user to run code calling tf.raw_ops.ImmutableConst on a memory-mapped file with a non-integral tensor type can write to an immutable memory region, which crashes the Python interpreter with a segmentation fault. Upgrade to 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2 or later.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.4 Medium 3.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0021, the 11th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:38 UTC First seen by agentprime
  2. 31 Oct 2026, 14:38 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.