vciy

CVE-2022-35737

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.

SQLite 1.0.12 through 3.39.x before 3.39.2 sometimes allows an array-bounds overflow if billions of bytes are used in a string argument to a C API.

CVE-2022-357373 of 4 sources documented this
43

rank 43 = 18 + 19 + 1 + 5 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.21454  ·  without this subject the record ranks 25

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 24

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2026-05-25  ·  without this subject the record ranks 42

How much of the world it touches

NVD CPE configurations

4 products in the CPE ranges  ·  without this subject the record ranks 38

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$655,000over the next 30 days, if this record is yours
Movement+$287,000on 2026-05-25, the last material move, 2 months before this reading
Basisassumeda published average, not your estate

$655,000 = $4.99M incident cost x 0.6121449559255632 exposure x 0.21454 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.21454EPSSNOT IN KEVas of 2026-09-20
Severity7.5 HIGHreceipt
Harmunauthenticated · networkreceipt
Exploitationpublic proof-of-conceptreceipt
Defenseunaffected versions publishedreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2026-06-30, 31 days at 0.21, as of 2026-07-31. 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

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.1 · NVD's vectorreceipt
Weakness classCWE-129 Improper Validation of Array Indexreceipt
Published consequencesCWE-129: Integrity, Availability: DoS: Crash, Exit, or Restart; Integrity: Modify Memory; Confidentiality, Integrity: Modify Memory, Read Memory…[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 branchsqlite 3.39.2; universal forwarder 8.2.12; universal forwarder 9.0.6receipt
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 · 2 public repositories, 2022-10-24.

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

Authority who says so

CVSS, NVD7.5 HIGHreceipt
Exploit probability0.21454 · top 3% of all CVEsreceipt
Blast breadth2 products across 2 vendorsderived
Assigned bymitrereceipt
Recorded changes50 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Named in the CPE rangesSqlite; Splunk universal forwarderreceipt
Published rangessqlite >= 1.0.12 < 3.39.2; splunk universal forwarder >= 8.2.0 < 8.2.12; splunk universal forwarder >= 9.0.0 < 9.0.6; splunk universal forwarder 9.1.0receipt

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

SQLite 1.0.12 through 3.39.x before 3.39.2 sometimes allows an array-bounds overflow if billions of bytes are used in a string argument to a C API. receipt

NVD's analysis a second authority

severity
7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
weakness
CWE-129
affected versions
sqlite >= 1.0.12 < 3.39.2; splunk universal forwarder >= 8.2.0 < 8.2.12; splunk universal forwarder >= 9.0.0 < 9.0.6; and 1 more, listed in full below
also scored by
7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

check it yourself sqlite.org kb.cert.org sqlite.org security.netapp.com blog.trailofbits.com security.gentoo.org receipt

Dated events

2025-03-17EPSS moved 0.00 to 0.592026-06-30EPSS moved 0.11 to 0.19

Movement the material steps

3 Aug 20220.00885
7 Mar 20237.6e-4 · scoring model v2023.03.01
17 Mar 20250.58761 · crossed 0.10 and 0.50 · scoring model v2025.03.14
22 May 20260.48776 · crossed 0.50
25 May 20260.58185 · crossed 0.50
15 Jun 20260.11431 · crossed 0.50 · scoring model v2026.06.15
31 Jul 20260.21454
Show all 47 observations
3 Aug 20220.00885
6 Sep 20220.00954
16 Sep 20220.01018
1 Nov 20220.01108
7 Mar 20237.6e-4
8 Mar 20230.00076
4 Jul 20230.00090
10 Aug 20230.00126
8 Nov 20230.00154
14 Jan 20240.00184
24 Feb 20240.00207
10 Mar 20240.00212
24 Mar 20240.00254
25 Oct 20240.00329
17 Dec 20240.00332
9 Mar 20250.00402
17 Mar 20250.58761
19 Mar 20250.67655
20 Mar 20250.58761
27 Mar 20250.67655
28 Mar 20250.58761
29 Mar 20250.67655
30 Mar 20250.58761
30 May 20250.65609
24 Jul 20250.62887
26 Jul 20250.63953
21 Aug 20250.61204
24 Aug 20250.63953
29 Aug 20250.64445
11 Sep 20250.63953
17 Oct 20250.61204
18 Oct 20250.63953
23 Oct 20250.64445
26 Oct 20250.52518
5 Nov 20250.51941
18 Nov 20250.5406
21 Nov 20250.51941
22 Nov 20250.52518
5 Dec 20250.51941
22 May 20260.48776
25 May 20260.58185
29 May 20260.54845
11 Jun 20260.54278
15 Jun 20260.11431
30 Jun 20260.19193
9 Jul 20260.17981
31 Jul 20260.21454

47 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.21454Published2022-08-03Public PoC2022-10-24Index as of2026-07-31

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

Published 2022-08-03 receipt · Public PoC 2022-10-24 receipt · Index as of 2026-07-31 derived

Siblings and hubs

Records related to this one

Browse the index from here

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

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.