vciy

CVE-2020-7209

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.

LinuxKI v6.0-1 and earlier is vulnerable to an remote code execution which is resolved in release 6.0-2.

CVE-2020-72094 of 4 sources documented this
52

rank 52 = 25 + 25 + 0 + 2 + 0

rank@v1 · this cycle

Someone is already using it

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

EPSS 0.98751  ·  without this subject the record ranks 27

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 27

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 52

How much of the world it touches

NVD CPE configurations

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

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$4.93Mover the next 30 days, if this record is yours
Movement+$981,000on 2022-02-04, the last material move, 4 years, 5 months before this reading
Basisassumeda published average, not your estate

$4.93M = $4.99M incident cost x 1 exposure x 0.98751 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.98751EPSSNOT IN KEVas of 2026-09-20
Severity9.8 CRITICALreceipt
Harmtotal loss · unauthenticatedreceipt
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2022-02-04, 1622 days at 0.99, as of 2026-07-15. 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 LinuxKI? 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 confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classNo CWE mapping in held sources.

CISA KEV & Federal Remediation Deadline from the record and CISA

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

First unaffected version, by branchlinuxki 6.0-2receipt
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.98751 · top 0.08% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byhpereceipt
Recorded changes48 · last 17 Sep 2026derived

Affected & Fixed Versions as published

Affected productLinuxKIreceipt
Published rangeshp linuxki < 6.0-2receipt

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

LinuxKI v6.0-1 and earlier is vulnerable to an remote code execution which is resolved in release 6.0-2. receipt

NVD's analysis a second authority

severity
9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
affected versions
hp linuxki < 6.0-2

check it yourself github.com packetstormsecurity.com packetstormsecurity.com receipt

Dated events

2021-09-14EPSS moved 0.76 to 0.302026-06-15EPSS moved 0.93 to 0.99

Movement the material steps

14 Apr 20210.75688
14 Sep 20210.29642 · crossed 0.50
16 Sep 20210.75688 · crossed 0.50
4 Feb 20220.95351 · crossed 0.90
7 Mar 20230.97348 · scoring model v2023.03.01
17 Mar 20250.93719 · scoring model v2025.03.14
15 Jun 20260.98846 · scoring model v2026.06.15
15 Jul 20260.98751

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

Show all 48 observations
14 Apr 20210.75688
14 Sep 20210.29642
16 Sep 20210.75688
4 Feb 20220.95351
7 Mar 20230.97348
15 Apr 20230.97325
8 May 20230.97174
31 May 20230.97217
2 Jul 20230.97134
18 Jul 20230.97223
22 Aug 20230.97202
26 Sep 20230.97151
12 Oct 20230.97171
30 Oct 20230.97175
2 Dec 20230.97092
3 Jan 20240.97190
5 Feb 20240.97243
7 Mar 20240.97202
8 Apr 20240.97193
9 May 20240.97227
10 Jul 20240.97167
27 Sep 20240.97227
29 Oct 20240.97158
17 Dec 20240.96790
18 Dec 20240.96877
3 Jan 20250.96868
5 Feb 20250.96824
12 Mar 20250.96733
17 Mar 20250.93719
18 Mar 20250.93711
19 Mar 20250.93719
20 Mar 20250.93711
23 Mar 20250.93719
24 Mar 20250.93711
26 Mar 20250.93719
27 Mar 20250.93747
9 May 20250.93309
13 Jun 20250.93391
2 Nov 20250.93801
18 Nov 20250.91544
21 Nov 20250.93801
30 Dec 20250.93776
1 Jan 20260.93717
3 Jan 20260.93631
10 Feb 20260.93446
28 Apr 20260.93187
15 Jun 20260.98846
15 Jul 20260.98751

48 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.98751Published2020-02-12Index as of2026-07-15

Exploit probability more than doubled between 2021-09-14 and 2021-09-16 (0.29642 → 0.75688) and the record had been public for 6 years, 5 months when this index was last written.

Published 2020-02-12 receipt · Index as of 2026-07-15 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2020-7209.

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.