vciy

CVE-2021-3737

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

A flaw was found in python

CVE-2021-37374 of 4 sources documented this
32

rank 32 = 3 + 19 + 0 + 10 + 0

rank@v1 · scheduled

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.11586  ·  without this subject the record ranks 29

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.5, from NVD  ·  without this subject the record ranks 13

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 32

How much of the world it touches

NVD CPE configurations

20 products in the CPE ranges  ·  without this subject the record ranks 22

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 32

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$354,000over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$354,000 = $4.99M incident cost x 0.6121449559255632 exposure x 0.11586 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.11586EPSSNOT IN KEVas of 2026-09-20
Severity7.5 HIGHreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2026-06-15, 52 days at 0.12, as of 2026-08-06. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Running python? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no privileges required · no user interaction · low attack complexityreceipt
ImpactComplete availability lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-835 Loop with Unreachable Exit Condition ('Infinite Loop'); CWE-400 Uncontrolled Resource Consumptionreceipt
Published consequencesCWE-835: Availability: DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Amplification[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

First unaffected version, by branchpython 3.6.14; python 3.7.11; python 3.8.11; python 3.9.6receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, NVD7.5 HIGHreceipt
Exploit probability0.11586 · top 4% of all CVEsreceipt
Blast breadth10 products across 5 vendorsderived
Assigned byredhatreceipt
Recorded changes78 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productpythonreceipt
Published rangespython >= 3.6.0 < 3.6.14; python >= 3.7.0 < 3.7.11; python >= 3.8.0 < 3.8.11; python >= 3.9.0 < 3.9.6receipt
Show all 20 published ranges
python >= 3.6.0 < 3.6.14
python >= 3.7.0 < 3.7.11
python >= 3.8.0 < 3.8.11
python >= 3.9.0 < 3.9.6
redhat codeready linux builder 8.0
redhat codeready linux builder for ibm z systems 8.0
redhat codeready linux builder for power little endian 8.0
redhat enterprise linux 6.0
redhat enterprise linux 7.0
redhat enterprise linux 8.0
redhat enterprise linux for ibm z systems 8.0
redhat enterprise linux for power little endian 8.0
fedoraproject fedora 33
fedoraproject fedora 34
canonical ubuntu linux 14.04
canonical ubuntu linux 16.04
canonical ubuntu linux 18.04
canonical ubuntu linux 20.04
canonical ubuntu linux 21.04
oracle communications cloud native core binding support function 22.1.3

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

A flaw was found in python. An improperly handled HTTP response in the HTTP client code of python may allow a remote attacker, who controls the HTTP server, to make the client script enter an infinite loop, consuming CPU time. The highest threat from this vulnerability is to system availability. receipt

NVD's analysis a second authority

severity
7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
weakness
CWE-835; CWE-400
affected versions
python >= 3.6.0 < 3.6.14; python >= 3.7.0 < 3.7.11; python >= 3.8.0 < 3.8.11; and 17 more, listed in full below
also scored by
7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

check it yourself bugs.python.org github.com bugzilla.redhat.com github.com ubuntu.com oracle.com +4 morereceipt

Movement the material steps

5 Mar 20220.01132
7 Mar 20230.0021 · scoring model v2023.03.01
17 Mar 20250.00106 · scoring model v2025.03.14
15 Jun 20260.11586 · crossed 0.10 · scoring model v2026.06.15
6 Aug 20260.11586

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 78 observations
5 Mar 20220.01132
8 Mar 20220.01232
16 Mar 20220.01319
26 Jul 20220.01408
7 Mar 20230.0021
8 Mar 20230.00210
11 Mar 20230.00252
6 Apr 20230.00303
8 May 20230.00392
9 Jun 20230.00412
1 Jul 20230.00674
6 Jul 20230.00954
15 Aug 20230.01133
25 Sep 20230.01276
10 Oct 20230.01302
24 Oct 20230.01559
17 Nov 20240.01652
17 Dec 20240.01105
17 Mar 20250.00106
22 Mar 20250.00104
23 Mar 20250.0012
28 Mar 20250.00104
29 Mar 20250.00498
30 Mar 20250.0012
3 Apr 20250.00104
4 Apr 20250.0012
17 Apr 20250.00104
18 Apr 20250.0012
1 May 20250.00104
11 May 20250.0012
15 May 20250.00124
22 May 20250.0012
1 Jun 20250.00104
4 Jun 20250.0012
1 Jul 20250.00104
4 Jul 20250.0012
5 Jul 20250.00128
23 Jul 20250.00121
30 Jul 20250.00122
1 Aug 20250.00105
5 Aug 20250.00122
11 Aug 20250.00138
1 Sep 20250.00119
4 Sep 20250.00138
1 Oct 20250.00159
4 Oct 20250.00205
27 Oct 20250.00138
28 Oct 20250.00205
1 Nov 20250.00159
4 Nov 20250.00243
18 Nov 20250.0503
21 Nov 20250.00243
1 Dec 20250.00189
4 Dec 20250.00243
18 Dec 20250.0025
20 Dec 20250.00166
21 Dec 20250.0025
22 Dec 20250.00166
26 Dec 20250.00162
27 Dec 20250.00164
28 Dec 20250.00162
1 Jan 20260.00126
4 Jan 20260.00162
17 Jan 20260.00149
20 Jan 20260.00153
27 Jan 20260.00166
1 Feb 20260.00129
4 Feb 20260.00162
7 Feb 20260.00119
13 Feb 20260.00122
27 Feb 20260.00119
1 Mar 20260.00092
4 Mar 20260.00119
15 Jun 20260.11586
14 Jul 20260.11994
25 Jul 20260.11585
28 Jul 20260.11994
6 Aug 20260.11586

78 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.11586Published2022-03-04Index as of2026-08-06

Exploit probability more than doubled between 2025-03-28 and 2025-03-29 (0.00104 → 0.00498) and the record had been public for 4 years, 5 months when this index was last written.

Published 2022-03-04 receipt · Index as of 2026-08-06 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2021-3737.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.