---
id: CVE-2021-37671
aliases:
  - GHSA-qr82-2c78-4m8h
  - BIT-tensorflow-2021-37671
  - PYSEC-2021-293
  - PYSEC-2021-584
  - PYSEC-2021-782
title: Reference binding to nullptr in map operations
summary: Reference binding to nullptr in map operations
severity: high
cvss: 7.8
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'
vendor: tensorflow
product: tensorflow
ecosystem: pip
affected:
  - tensorflow < 2.3.4
  - 'tensorflow >= 2.4.0, < 2.4.3'
  - 'tensorflow >= 2.5.0, < 2.5.1'
  - tensorflow-cpu < 2.3.4
  - 'tensorflow-cpu >= 2.4.0, < 2.4.3'
  - 'tensorflow-cpu >= 2.5.0, < 2.5.1'
  - tensorflow-gpu < 2.3.4
  - 'tensorflow-gpu >= 2.4.0, < 2.4.3'
  - 'tensorflow-gpu >= 2.5.0, < 2.5.1'
patched:
  - tensorflow 2.3.4
  - tensorflow 2.4.3
  - tensorflow 2.5.1
  - tensorflow-cpu 2.3.4
  - tensorflow-cpu 2.4.3
  - tensorflow-cpu 2.5.1
  - tensorflow-gpu 2.3.4
  - tensorflow-gpu 2.4.3
  - tensorflow-gpu 2.5.1
published: '2021-08-25'
updated: '2026-07-08'
source: OSV
sourceUrl: 'https://osv.dev/vulnerability/GHSA-qr82-2c78-4m8h'
references:
  - url: >-
      https://github.com/tensorflow/tensorflow/security/advisories/GHSA-qr82-2c78-4m8h
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2021-37671'
  - url: >-
      https://github.com/tensorflow/tensorflow/commit/532f5c5a547126c634fefd43bbad1dc6417678ac
  - url: >-
      https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2021-584.yaml
  - url: >-
      https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2021-782.yaml
  - url: >-
      https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2021-293.yaml
  - url: 'https://github.com/tensorflow/tensorflow'
tags:
  - osv
  - pip
epss: 0.00173
epssPercentile: 0.05964
ingestedAt: '2026-07-08T18:25:52.479Z'
---

## Overview

### Impact
An attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.Map*` and `tf.raw_ops.OrderedMap*` operations:

```python
import tensorflow as tf
  
tf.raw_ops.MapPeek(
  key=tf.constant([8],dtype=tf.int64),
  indices=[],
  dtypes=[tf.int32],
  capacity=8,
  memory_limit=128)
```

The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/map_stage_op.cc#L222-L248) has a check in place to ensure that `indices` is in ascending order, but does not check that `indices` is not empty.
    
### Patches
We have patched the issue in GitHub commit [532f5c5a547126c634fefd43bbad1dc6417678ac](https://github.com/tensorflow/tensorflow/commit/532f5c5a547126c634fefd43bbad1dc6417678ac).
                       
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
    
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.

### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.

## Affected packages

- `tensorflow < 2.3.4`
- `tensorflow >= 2.4.0, < 2.4.3`
- `tensorflow >= 2.5.0, < 2.5.1`
- `tensorflow-cpu < 2.3.4`
- `tensorflow-cpu >= 2.4.0, < 2.4.3`
- `tensorflow-cpu >= 2.5.0, < 2.5.1`
- `tensorflow-gpu < 2.3.4`
- `tensorflow-gpu >= 2.4.0, < 2.4.3`
- `tensorflow-gpu >= 2.5.0, < 2.5.1`

## Remediation

Upgrade to a patched release:

- `tensorflow 2.3.4`
- `tensorflow 2.4.3`
- `tensorflow 2.5.1`
- `tensorflow-cpu 2.3.4`
- `tensorflow-cpu 2.4.3`
- `tensorflow-cpu 2.5.1`
- `tensorflow-gpu 2.3.4`
- `tensorflow-gpu 2.4.3`
- `tensorflow-gpu 2.5.1`