vciy

CVE-2022-28877

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.

Local Privilege Escalation Vulnerability in F-Secure & WithSecure Windows Endpoint Products

CVE-2022-288773 of 4 sources documented this
17

rank 17 = 0 + 17 + 0 + 0 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.00420  ·  without this subject the record ranks 17

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 6.7, from NVD  ·  without this subject the record ranks 0

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 17

How much of the world it touches

NVD CPE configurations

0 products in the CPE ranges  ·  without this subject the record ranks 17

Someone else already set the date

CISA KEV remediation due date

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

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

$12,000 = $4.99M incident cost x 0.5743756121449558 exposure x 0.0042 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.0042EPSSNOT IN KEVas of 2026-09-20
Severity4.3 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementfallenreceipt
PLATEAU10Minimal movement since 2022-07-22, 1515 days at 0.00, as of 2026-09-14. 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

Sources disagree here.

Severity score
F-SecureUS4.3 MEDIUMreceipt
NVD6.7 MEDIUMreceipt
What it costs
F-SecureUSPartial confidentiality, integrity and availability lossreceipt
NVDComplete confidentiality, integrity and availability lossreceipt

Both shown, dated. We don't pick winners. disagreement-rules@v1

Running F-Secure and WithSecure Endpoint…? 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 · high privileges required · user interaction required · low attack complexityreceipt
ImpactPartial confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.1 · the CNA'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.

Fixed inNo fix version in held sources, as the index stood on 14 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, the CNA4.3 MEDIUMreceipt
CVSS, NVD6.7 MEDIUMreceipt
Exploit probability0.0042 · top 64% of all CVEsreceipt
Assigned byF-SecureUSreceipt
Recorded changes18 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productF-Secure and WithSecure All F-Secure and WithSecure Endpoint Protection Products for Windowsreceipt

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

This vulnerability allows local user to delete arbitrary file in the system and bypassing security protection which can be abused for local privilege escalation on affected F-Secure & WithSecure windows endpoint products. An attacker must have code execution rights on the victim machine prior to successful exploitation. receipt

NVD's analysis a second authority

severity
6.7 CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
also scored by
[email protected] 4.3 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:L

The CNA scored it 4.3 and NVD 6.7. Both are shown because both were published; we do not pick one.

check it yourself f-secure.com withsecure.com receipt

Movement the material steps

22 Jul 20220.02485
7 Mar 20234.2e-4 · scoring model v2023.03.01
17 Mar 20250.00016 · scoring model v2025.03.14
15 Jun 20260.00333 · scoring model v2026.06.15
14 Sep 20260.0042
Show all 18 observations
22 Jul 20220.02485
28 Jul 20220.01005
7 Mar 20234.2e-4
8 Mar 20230.00042
17 Mar 20250.00016
19 Mar 20250.00021
29 Mar 20250.00039
30 Mar 20250.00021
15 Apr 20250.00023
17 May 20250.00025
22 Jul 20250.00124
23 Jul 20250.00162
22 Sep 20250.00187
15 Jun 20260.00333
26 Jun 20260.00336
18 Jul 20260.00402
7 Aug 20260.00411
14 Sep 20260.0042

18 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.0042Published2022-07-21Index as of2026-09-14

The record had been public for 4 years, 1 month when this index was last written.

Published 2022-07-21 receipt · Index as of 2026-09-14 derived

Siblings and hubs

Records related to this one

Fixed with these, by one advisory

advisory published by f-secure.com

Listed because one advisory covers them, not because they are the same defect. Each record's own state is on its own page.

Grouping: held values

Browse the index from here

These are index-wide views, not findings about CVE-2022-28877.

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.