vciy

CVE-2021-31807

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.

An issue was discovered in Squid before 4.15 and 5.x before 5.0.6

CVE-2021-318073 of 4 sources documented this
32

rank 32 = 4 + 16 + 2 + 10 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.15972  ·  without this subject the record ranks 28

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 6.5, from NVD  ·  without this subject the record ranks 16

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2025-06-19  ·  without this subject the record ranks 30

How much of the world it touches

NVD CPE configurations

19 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$488,000over the next 30 days, if this record is yours
Movement-$901,000on 2022-02-04, the last material move, 4 years, 4 months before this reading
Basisassumeda published average, not your estate

$488,000 = $4.99M incident cost x 0.6121449559255632 exposure x 0.15972 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.15972EPSSNOT IN KEVas of 2026-09-20
Severity6.5 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementscoring model changedreceipt
RISING10Risen from 0.00777 to 0.15972 across 37 observations. arc-rules@v1

Foresight · where to check next

Qualcomm, Inc.Microsoft WindowsMicrosoft OfficeThe LinuxCVE-2013-2596CVE-2013-272931807

This record is one instance of CWE-190, integer overflow or wraparound. The index holds 3586 prior instances of this class, 21 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

Check a version against this record

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 · low privileges required · no user interaction · low attack complexityreceipt
ImpactComplete availability lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-190 Integer Overflow or Wraparoundreceipt
Published consequencesCWE-190: Availability: DoS: Crash, Exit, or Restart, DoS: Resource Consumption (Memory), DoS: Instability; Integrity: Modify Memory; Confidentiality, Availability, Access Control: Execute…[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 branchsquid 4.15; squid 5.0.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, NVD6.5 MEDIUMreceipt
Exploit probability0.15972 · top 3% of all CVEsreceipt
Blast breadth2 products across 2 vendorsderived
Assigned bymitrereceipt
Recorded changes37 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Named in the CPE rangesSquid-cache squid; Fedoraproject fedorareceipt
Published rangessquid-cache squid >= 3.0 < 4.15; squid-cache squid >= 5.0 < 5.0.6; squid-cache squid 2.5.stable2; squid-cache squid 2.5.stable3receipt
Show all 19 published ranges
squid-cache squid >= 3.0 < 4.15
squid-cache squid >= 5.0 < 5.0.6
squid-cache squid 2.5.stable2
squid-cache squid 2.5.stable3
squid-cache squid 2.5.stable4
squid-cache squid 2.5.stable5
squid-cache squid 2.5.stable6
squid-cache squid 2.5.stable7
squid-cache squid 2.5.stable8
squid-cache squid 2.5.stable9
squid-cache squid 2.5.stable10
squid-cache squid 2.5.stable11
squid-cache squid 2.5.stable12
squid-cache squid 2.5.stable13
squid-cache squid 2.5.stable14
squid-cache squid 2.6
squid-cache squid 2.7
fedoraproject fedora 33
fedoraproject fedora 34

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

An issue was discovered in Squid before 4.15 and 5.x before 5.0.6. An integer overflow problem allows a remote server to achieve Denial of Service when delivering responses to HTTP Range requests. The issue trigger is a header that can be expected to exist in HTTP traffic without any malicious intent. receipt

NVD's analysis a second authority

severity
6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
weakness
CWE-190
affected versions
squid-cache squid >= 3.0 < 4.15; squid-cache squid >= 5.0 < 5.0.6; squid-cache squid 2.5.stable2; and 16 more, listed in full below

check it yourself github.com squid-cache.org lists.fedoraproject.org lists.fedoraproject.org lists.debian.org security.netapp.com +2 morereceipt

Dated events

2021-10-22EPSS moved 0.02 to 0.122025-03-17EPSS moved 0.01 to 0.342026-06-15EPSS moved 0.34 to 0.16

Movement the material steps

9 Jun 20210.00777
22 Oct 20210.11964 · crossed 0.10
6 Jan 20220.37879
4 Feb 20220.08384 · crossed 0.10
7 Mar 20230.00829 · scoring model v2023.03.01
17 Mar 20250.33712 · crossed 0.10 · scoring model v2025.03.14
29 Mar 20250.43921
30 Mar 20250.33712
19 Jun 20250.44193
31 Dec 20250.33801
15 Jun 20260.15972 · scoring model v2026.06.15
Show all 37 observations
9 Jun 20210.00777
11 Jun 20210.01294
14 Jun 20210.0155
17 Jul 20210.01806
22 Oct 20210.11964
6 Jan 20220.37879
4 Feb 20220.08384
1 Apr 20220.01034
7 Mar 20230.00829
12 Oct 20230.04253
17 Oct 20230.03216
25 Oct 20230.02260
8 Nov 20230.03216
9 Feb 20240.03208
17 Dec 20240.02186
23 Feb 20250.01100
17 Mar 20250.33712
29 Mar 20250.43921
30 Mar 20250.33712
19 Jun 20250.44193
30 Jul 20250.3759
16 Aug 20250.39405
25 Aug 20250.37332
27 Sep 20250.37424
28 Sep 20250.37683
1 Oct 20250.44287
9 Oct 20250.47571
27 Oct 20250.40921
28 Oct 20250.47571
18 Nov 20250.38638
21 Nov 20250.47571
27 Dec 20250.40921
28 Dec 20250.47571
30 Dec 20250.44287
31 Dec 20250.33801
16 Jan 20260.33712
15 Jun 20260.15972

37 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.15972Published2021-06-08Index as of2026-06-15

The record had been public for 5 years when this index was last written.

Published 2021-06-08 receipt · Index as of 2026-06-15 derived

The pattern, elsewhere

This record is one instance of CWE-190, integer overflow or wraparound. The index holds 3586 prior instances of this class, 21 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2026-21385 · Qualcomm, Inc. Snapdragonmatches 5 of 8KEV listed · 2026receipt
CVE-2024-38080 · Microsoft Windows Server 2022matches 5 of 8KEV listed · 2024receipt
CVE-2023-21823 · Microsoft Office for Androidmatches 5 of 8KEV listed · 2023receipt
CVE-2018-14634 · The Linux Foundation kernelmatches 5 of 8KEV listed · 2018receipt
CVE-2013-2596matches 5 of 8KEV listed · 2013receipt
CVE-2013-2729matches 5 of 8KEV listed · 2013receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

3586 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Browse the index from here

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

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.