vciy

CVE-2016-2569

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.

Squid 3.x before 3.5.15 and 4.x before 4.0.7 does not properly append data to String objects, which allows remote servers to cause a denial of…

CVE-2016-25693 of 4 sources documented this
51

rank 51 = 20 + 19 + 2 + 10 + 0

rank@v1 · this cycle

Someone is already using it

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

EPSS 0.31187  ·  without this subject the record ranks 31

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 32

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2025-10-28  ·  without this subject the record ranks 49

How much of the world it touches

NVD CPE configurations

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

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$953,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

$953,000 = $4.99M incident cost x 0.6121449559255632 exposure x 0.31187 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.31187EPSSNOT IN KEVas of 2026-09-20
Severity7.5 HIGHreceipt
Harmunauthenticated · networkreceipt
Exploitationpublic proof-of-conceptreceipt
Defenseno fix version held
Movementrisenreceipt
PLATEAU10Minimal movement since 2026-06-15, 83 days at 0.31, as of 2026-09-06. arc-rules@v1

Foresight · where to check next

CVE-2022-47966CVE-2022-29499VMware vCenterQNAP Systems Inc.MicrosoftQNAP NAS devices2569

This record is one instance of CWE-20, improper input validation. The index holds 13347 prior instances of this class, 73 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 · no privileges required · no user interaction · low attack complexityreceipt
ImpactComplete availability lossreceipt
Scored fromCVSS v3.0 · NVD's vectorreceipt
Weakness classCWE-20 Improper Input Validationreceipt
Published consequencesCWE-20: Availability: DoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory); Confidentiality: Read Memory, Read Files or Directories…[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

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

Fixed inNo fix version in held sources, as the index stood on 6 Sep 2026.
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: Proof-of-concept published · 1 public repository, 2018-02-03.

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

Authority who says so

CVSS, NVD7.5 HIGHreceipt
Exploit probability0.31187 · top 2% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bymitrereceipt
Recorded changes42 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Named in the CPE rangesSquid-cache squidreceipt
Published rangessquid-cache squid 3.0; squid-cache squid 3.0.stable1; squid-cache squid 3.0.stable2; squid-cache squid 3.0.stable3receipt
Show all 20 published ranges
squid-cache squid 3.0
squid-cache squid 3.0.stable1
squid-cache squid 3.0.stable2
squid-cache squid 3.0.stable3
squid-cache squid 3.0.stable4
squid-cache squid 3.0.stable5
squid-cache squid 3.0.stable6
squid-cache squid 3.0.stable7
squid-cache squid 3.0.stable8
squid-cache squid 3.0.stable9
squid-cache squid 3.0.stable10
squid-cache squid 3.0.stable11
squid-cache squid 3.0.stable12
squid-cache squid 3.0.stable13
squid-cache squid 3.0.stable14
squid-cache squid 3.0.stable15
squid-cache squid 3.0.stable16
squid-cache squid 3.0.stable17
squid-cache squid 3.0.stable18
squid-cache squid 3.0.stable19

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

Squid 3.x before 3.5.15 and 4.x before 4.0.7 does not properly append data to String objects, which allows remote servers to cause a denial of service (assertion failure and daemon exit) via a long string, as demonstrated by a crafted HTTP Vary header. receipt

NVD's analysis a second authority

severity
7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
weakness
CWE-20
affected versions
squid-cache squid 3.0; squid-cache squid 3.0.stable1; squid-cache squid 3.0.stable2; and 17 more, listed in full below

check it yourself usn.ubuntu.com security.gentoo.org squid-cache.org lists.opensuse.org rhn.redhat.com squid-cache.org +5 morereceipt

Dated events

2023-03-07EPSS moved 0.16 to 0.932026-06-15EPSS moved 0.70 to 0.31

Movement the material steps

4 Feb 20220.16306
7 Mar 20230.93137 · crossed 0.50 and 0.90 · scoring model v2023.03.01
17 Mar 20250.74153 · crossed 0.90 · scoring model v2025.03.14
7 Sep 20250.57555
1 Oct 20250.67602
27 Oct 20250.57555
28 Oct 20250.67602
15 Jun 20260.3067 · crossed 0.50 · scoring model v2026.06.15
6 Sep 20260.31187
Show all 39 observations
4 Feb 20220.16306
7 Mar 20230.93137
8 May 20230.95338
29 May 20230.95722
5 Jul 20230.96623
8 Jul 20230.94292
8 Aug 20230.94965
10 Sep 20230.94443
16 Nov 20230.94965
22 Feb 20240.95495
28 Mar 20240.95672
10 Aug 20240.90967
13 Aug 20240.95672
17 Dec 20240.95740
17 Mar 20250.74153
19 Mar 20250.72869
20 Mar 20250.74153
27 Mar 20250.72869
28 Mar 20250.74153
29 Mar 20250.72869
30 Mar 20250.74153
30 Jul 20250.65757
20 Aug 20250.67989
7 Sep 20250.57555
1 Oct 20250.67602
27 Oct 20250.57555
28 Oct 20250.67602
13 Dec 20250.71402
27 Dec 20250.62242
28 Dec 20250.71402
18 Feb 20260.70733
23 Feb 20260.70316
15 Jun 20260.3067
18 Jun 20260.31411
1 Jul 20260.31187
23 Aug 20260.35367
30 Aug 20260.31187
5 Sep 20260.35367
6 Sep 20260.31187

39 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.31187Published2016-02-27Public PoC2018-02-03Index as of2026-09-06

The record had been public for 10 years, 6 months when this index was last written.

Published 2016-02-27 receipt · Public PoC 2018-02-03 receipt · Index as of 2026-09-06 derived

The pattern, elsewhere

This record is one instance of CWE-20, improper input validation. The index holds 13347 prior instances of this class, 73 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2022-47966matches 6 of 8KEV listed · 2023receipt
CVE-2022-29499matches 6 of 8KEV listed · 2022receipt
CVE-2021-21985 · VMware vCenter Server and VMware Cloud…matches 6 of 8KEV listed · 2021receipt
CVE-2018-19949 · QNAP Systems Inc. QTSmatches 6 of 8KEV listed · 2020receipt
CVE-2019-0604 · Microsoft SharePoint Servermatches 6 of 8KEV listed · 2019receipt
CVE-2019-7193 · QNAP NAS devicesmatches 6 of 8KEV listed · 2019receipt

"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

13347 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-2016-2569.

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.