vciy

CVE-2023-26068

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.

Certain Lexmark devices through 2023-02-19 mishandle Input Validation (issue 2 of 4).

CVE-2023-260683 of 4 sources documented this
39

rank 39 = 3 + 25 + 1 + 10 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.11634  ·  without this subject the record ranks 36

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 14

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2025-11-21  ·  without this subject the record ranks 38

How much of the world it touches

NVD CPE configurations

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

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$581,000over the next 30 days, if this record is yours
Movement+$1.22Mon 2023-09-19, the last material move, 2 years, 8 months before this reading
Basisassumeda published average, not your estate

$581,000 = $4.99M incident cost x 1 exposure x 0.11634 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.11634EPSSNOT IN KEVas of 2026-09-20
Severity9.8 CRITICALreceipt
Harmtotal loss · unauthenticatedreceipt
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementthreshold crossedreceipt
RISING10Risen from 0.00043 to 0.11634 across 32 observations. arc-rules@v1

Foresight · where to check next

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

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 confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.1 · 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.

First unaffected version, by branchcslbl firmware cslbl.081.232; cslbn firmware cslbn.081.232; csnzj firmware csnzj.081.232; cstpc firmware cstpc.081.232; cxlbl firmware cxlbl.081.232; cxlbn firmware cxlbn.081.232receipt
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.11634 · top 4% of all CVEsreceipt
Blast breadth20 products across 1 vendorderived
Assigned bymitrereceipt
Recorded changes32 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Named in the CPE rangesLexmark cxtpc firmware; Lexmark cstpc firmware; Lexmark mxtct firmware; and 17 morereceipt
Published rangeslexmark cxtpc firmware < cxtpc.081.232; lexmark cstpc firmware < cstpc.081.232; lexmark mxtct firmware < mxtct.081.232; lexmark mxtpm firmware < mxtpm.081.232receipt
Show all 20 published ranges
lexmark cxtpc firmware < cxtpc.081.232
lexmark cstpc firmware < cstpc.081.232
lexmark mxtct firmware < mxtct.081.232
lexmark mxtpm firmware < mxtpm.081.232
lexmark cxtmm firmware < cxtmm.081.232
lexmark mslsg firmware < mslsg.081.232
lexmark mxlsg firmware < mxlsg.081.232
lexmark mslbd firmware < mslbd.081.232
lexmark mxlbd firmware < mxlbd.081.232
lexmark msngm firmware < msngm.081.232
lexmark mxngm firmware < mxngm.081.232
lexmark mxtgm firmware < mxtgm.081.232
lexmark msngw firmware < msngw.081.232
lexmark mstgw firmware < mstgw.081.232
lexmark mxtgw firmware < mxtgw.081.232
lexmark cslbn firmware < cslbn.081.232
lexmark cslbl firmware < cslbl.081.232
lexmark cxlbn firmware < cxlbn.081.232
lexmark cxlbl firmware < cxlbl.081.232
lexmark csnzj firmware < csnzj.081.232

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

Certain Lexmark devices through 2023-02-19 mishandle Input Validation (issue 2 of 4). 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
weakness
CWE-20
affected versions
lexmark cxtpc firmware < cxtpc.081.232; lexmark cstpc firmware < cstpc.081.232; lexmark mxtct firmware < mxtct.081.232; and 17 more, listed in full below
also scored by
9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

check it yourself support.lexmark.com publications.lexmark.com packetstormsecurity.com receipt

Dated events

2023-09-19EPSS moved 0.00 to 0.252026-06-15EPSS moved 0.81 to 0.12

Movement the material steps

11 Apr 20230.00043
19 Sep 20230.24635 · crossed 0.10
17 Mar 20250.6621 · crossed 0.50 · scoring model v2025.03.14
19 Sep 20250.77654
18 Nov 20250.6621
3 Jan 20260.77712
15 Jun 20260.11634 · crossed 0.50 · scoring model v2026.06.15
Show all 32 observations
11 Apr 20230.00043
9 May 20230.00122
12 May 20230.00089
19 Sep 20230.24635
20 Sep 20230.16498
17 Nov 20230.17877
10 Mar 20240.20435
16 Apr 20240.19121
12 May 20240.20911
15 Jul 20240.19324
20 Sep 20240.24401
31 Oct 20240.28060
15 Nov 20240.30916
29 Nov 20240.31233
17 Dec 20240.30913
17 Mar 20250.6621
23 Mar 20250.67067
24 Mar 20250.6621
29 Mar 20250.67067
30 Mar 20250.6621
15 Apr 20250.71795
28 Apr 20250.75873
19 Sep 20250.77654
1 Nov 20250.78427
18 Nov 20250.6621
21 Nov 20250.76183
28 Nov 20250.76175
3 Jan 20260.77712
7 Mar 20260.79844
11 Apr 20260.79493
28 Apr 20260.81339
15 Jun 20260.11634

32 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.11634Published2023-04-10Index as of2026-06-15

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

Published 2023-04-10 receipt · Index as of 2026-06-15 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 8 of 8KEV listed · 2023receipt
CVE-2022-29499matches 8 of 8KEV listed · 2022receipt
CVE-2021-21985 · VMware vCenter Server and VMware Cloud…matches 8 of 8KEV listed · 2021receipt
CVE-2018-19949 · QNAP Systems Inc. QTSmatches 8 of 8KEV listed · 2020receipt
CVE-2019-0604 · Microsoft SharePoint Servermatches 8 of 8KEV listed · 2019receipt
CVE-2019-7193 · QNAP NAS devicesmatches 8 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-2023-26068.

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.