vciy

CVE-2019-11072

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.

lighttpd before 1.4.54 has a signed integer overflow, which might allow remote attackers to cause a denial of service (application crash) or possibly…

CVE-2019-110723 of 4 sources documented this
46

rank 46 = 18 + 25 + 1 + 2 + 0

rank@v1 · this cycle

Someone is already using it

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

EPSS 0.73762  ·  without this subject the record ranks 28

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 9.8, from NVD  ·  without this subject the record ranks 21

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2025-10-04  ·  without this subject the record ranks 45

How much of the world it touches

NVD CPE configurations

1 product in the CPE ranges  ·  without this subject the record ranks 44

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$3.68Mover the next 30 days, if this record is yours
Movement+$294,000on 2026-03-04, the last material move, 6 months before this reading
Basisassumeda published average, not your estate

$3.68M = $4.99M incident cost x 1 exposure x 0.73762 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.73762EPSSNOT IN KEVas of 2026-09-20
Severity9.8 CRITICALreceipt
Harmtotal loss · unauthenticatedreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2026-06-15, 83 days at 0.74, as of 2026-09-06. arc-rules@v1

Foresight · where to check next

CVE-2013-2729Qualcomm, Inc.kernelApple macOSGoogle ChromeCVE-2016-101011072

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 · no privileges required · no user interaction · low attack complexityreceipt
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.0 · 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.

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: 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, NVD9.8 CRITICALreceipt
Exploit probability0.73762 · top 0.55% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bymitrereceipt
Recorded changes58 · last 18 Sep 2026derived

Affected & Fixed Versions as published

Named in the CPE rangesLighttpdreceipt
Published rangeslighttpd <= 1.4.53receipt

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

lighttpd before 1.4.54 has a signed integer overflow, which might allow remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a malicious HTTP GET request, as demonstrated by mishandling of /%2F? in burl_normalize_2F_to_slash_fix in burl.c. NOTE: The developer states "The feature which can be abused to cause the crash is a new feature in lighttpd 1.4.50, and is not enabled by default. It must be explicitly configured in the config file (e.g. lighttpd.conf). Certain input will trigger an abort() in lighttpd when that feature is enabled. receipt

Read the rest of the CNA's description

lighttpd detects the underflow or realloc() will fail (in both 32-bit and 64-bit executables), also detected in lighttpd. Either triggers an explicit abort() by lighttpd. This is not exploitable beyond triggering the explicit abort() with subsequent application exit.

NVD's analysis a second authority

severity
9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
weakness
CWE-190
affected versions
lighttpd <= 1.4.53

check it yourself redmine.lighttpd.net github.com securityfocus.com receipt

Dated events

2022-02-04EPSS moved 0.06 to 0.122023-03-07EPSS moved 0.01 to 0.912026-06-15EPSS moved 0.12 to 0.74

Movement the material steps

14 Apr 20210.013
4 Feb 20220.12492 · crossed 0.10
1 Apr 20220.01136 · crossed 0.10
7 Mar 20230.90544 · crossed 0.10 and 0.50 and 0.90 · scoring model v2023.03.01
14 Feb 20240.86409 · crossed 0.90
8 May 20240.72556
17 Dec 20240.36847 · crossed 0.50
17 Mar 20250.05023 · crossed 0.10 · scoring model v2025.03.14
13 Sep 20250.11247 · crossed 0.10
1 Oct 20250.06257 · crossed 0.10
4 Oct 20250.13671 · crossed 0.10
1 Nov 20250.06257 · crossed 0.10
4 Nov 20250.13671 · crossed 0.10
18 Nov 20250.06855 · crossed 0.10
21 Nov 20250.13671 · crossed 0.10
1 Dec 20250.06257 · crossed 0.10
4 Dec 20250.13671 · crossed 0.10
1 Jan 20260.063 · crossed 0.10
4 Jan 20260.12284 · crossed 0.10
1 Feb 20260.06188 · crossed 0.10
4 Feb 20260.12083 · crossed 0.10
1 Mar 20260.06188 · crossed 0.10
4 Mar 20260.12083 · crossed 0.10
15 Jun 20260.73762 · crossed 0.50 · scoring model v2026.06.15
6 Sep 20260.73762

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

Show all 58 observations
14 Apr 20210.013
6 Jan 20220.05581
4 Feb 20220.12492
1 Apr 20220.01136
7 Mar 20230.90544
14 Feb 20240.86409
3 Apr 20240.87737
21 Apr 20240.77505
8 May 20240.72556
31 Aug 20240.66289
17 Dec 20240.36847
17 Mar 20250.05023
21 Mar 20250.01217
22 Mar 20250.05023
29 Mar 20250.04795
30 Mar 20250.05023
16 Apr 20250.01217
17 Apr 20250.05023
1 May 20250.01217
4 May 20250.05023
1 Jun 20250.01217
4 Jun 20250.05023
1 Jul 20250.01217
4 Jul 20250.05023
30 Jul 20250.03466
1 Aug 20250.00825
2 Aug 20250.02342
5 Aug 20250.08115
16 Aug 20250.08318
21 Aug 20250.08115
1 Sep 20250.02342
4 Sep 20250.08115
13 Sep 20250.11247
1 Oct 20250.06257
4 Oct 20250.13671
27 Oct 20250.11247
28 Oct 20250.13671
1 Nov 20250.06257
4 Nov 20250.13671
18 Nov 20250.06855
21 Nov 20250.13671
1 Dec 20250.06257
4 Dec 20250.13671
25 Dec 20250.12284
27 Dec 20250.1007
28 Dec 20250.12284
1 Jan 20260.063
4 Jan 20260.12284
24 Jan 20260.12083
1 Feb 20260.06188
4 Feb 20260.12083
1 Mar 20260.06188
4 Mar 20260.12083
15 Jun 20260.73762
23 Aug 20260.6931
30 Aug 20260.73762
5 Sep 20260.6931
6 Sep 20260.73762

58 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.73762Published2019-04-10Index as of2026-09-06

Exploit probability more than doubled between 2025-03-21 and 2025-03-22 (0.01217 → 0.05023) and the record had been public for 7 years, 4 months when this index was last written.

Published 2019-04-10 receipt · Index as of 2026-09-06 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-2013-2729matches 8 of 8KEV listed · 2013receipt
CVE-2023-33107 · Qualcomm, Inc. Snapdragonmatches 7 of 8KEV listed · 2023receipt
CVE-2022-0185 · kernelmatches 7 of 8KEV listed · 2022receipt
CVE-2021-30663 · Apple macOSmatches 7 of 8KEV listed · 2021receipt
CVE-2018-6065 · Google Chromematches 7 of 8KEV listed · 2018receipt
CVE-2016-1010matches 7 of 8KEV listed · 2016receipt

"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-2019-11072.

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.