CVE-2022-46908

CRITICALNVD 7.39.8
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-12-12. NVD baseline CVSS 7.3; sources differ by 2.5.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 5 sources updated this weekElevated

Also known asEUVD-2022-49687 (ENISA EUVD) · GHSA-993x-6558-2xmj (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

SQLite through 3.40.0, when relying on --safe for execution of an untrusted CLI script, does not properly implement the azProhibitedFunctions protection mechanism, and instead allows UDF functions such as WRITEFILE.

CVSS v3
7.3
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
39th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-09). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 12, 2022

Last Modified

October 14, 2026

Advisory Details (7)

Auto-updated Oct 14, 2026
Patch available.
Web pageMentions a patch (unverified)

SSA-398330

https://cert-portal.siemens.com/productcert/html/ssa-398330.html
Web page

SQLite: Multiple Vulnerabilities (GLSA 202311-03) — Gentoo security

https://security.gentoo.org/glsa/202311-03
Web page

SQLite: Check-in [cefc032473]

https://sqlite.org/src/info/cefc032473ac5ad2
Web page

SQLite User Forum: Why does --safe not prevent readfile()?

https://sqlite.org/forum/forumpost/07beac8056151b2f
Web page

Just a few days ago I found a serious security issue in SQLite: https://sqlite.o... | Hacker News

https://news.ycombinator.com/item?id=33948588

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntusqlite3-tools (3.42.0-1ubuntu0.1) @ mantic2026-11-01ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
sqlite3—
  • every version up to 3.40.0-2: fixed in 3.40.0-2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
sqlite3—
  • every version up to 3.40.0-2: fixed in 3.40.0-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
sqlite3—
  • every version up to 3.40.0-2: fixed in 3.40.0-2
—

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 30× in last 7d / 119× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 301 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 201 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-10 03:17 UTCEG score recompute
  2. 2026-11-10 03:17 UTCGHSA enrichmentGHSA-993x-6558-2xmj · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-11-09 16:30 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  4. 2026-11-09 05:11 UTCEG score recompute
  5. 2026-11-09 05:11 UTCVendor advisory
  6. 2026-11-09 05:11 UTCGHSA enrichmentGHSA-993x-6558-2xmj · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-11-08 16:34 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  8. 2026-11-08 07:05 UTCEG score recompute
  9. 2026-11-08 07:05 UTCVendor advisory
  10. 2026-11-08 07:05 UTCGHSA enrichmentGHSA-993x-6558-2xmj · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-11-07 16:34 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  12. 2026-11-07 08:57 UTCEG score recompute
  13. 2026-11-07 08:57 UTCVendor advisory
  14. 2026-11-07 08:57 UTCGHSA enrichmentGHSA-993x-6558-2xmj · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-11-06 16:31 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  16. 2026-11-06 10:51 UTCEG score recompute
  17. 2026-11-06 10:51 UTCVendor advisory
  18. 2026-11-06 10:51 UTCGHSA enrichmentGHSA-993x-6558-2xmj · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-11-05 16:32 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  20. 2026-11-05 12:45 UTCEG score recompute
  21. 2026-11-05 12:45 UTCVendor advisory
  22. 2026-11-05 12:45 UTCGHSA enrichmentGHSA-993x-6558-2xmj · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-11-04 16:30 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  24. 2026-11-04 14:39 UTCEG score recompute
  25. 2026-11-04 14:39 UTCVendor advisory
Show 75 more
  1. 2026-11-04 14:39 UTCGHSA enrichmentGHSA-993x-6558-2xmj · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-11-04 08:25 UTCOSV refresh
  3. 2026-11-03 16:39 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  4. 2026-11-03 16:33 UTCVendor advisory
  5. 2026-11-03 16:33 UTCGHSA enrichmentGHSA-993x-6558-2xmj · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-11-02 18:15 UTCEG score recompute
  7. 2026-11-02 18:15 UTCVendor advisory
  8. 2026-11-02 18:15 UTCGHSA enrichmentGHSA-993x-6558-2xmj · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-11-02 16:39 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  10. 2026-11-01 20:06 UTCEG score recompute
  11. 2026-11-01 20:06 UTCVendor advisory
  12. 2026-11-01 20:06 UTCGHSA enrichmentGHSA-993x-6558-2xmj · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-11-01 16:30 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  14. 2026-10-31 21:59 UTCEG score recompute
  15. 2026-10-31 21:59 UTCVendor advisory
  16. 2026-10-31 21:59 UTCGHSA enrichmentGHSA-993x-6558-2xmj · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-31 16:29 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  18. 2026-10-30 23:52 UTCEG score recompute
  19. 2026-10-30 23:52 UTCVendor advisory
  20. 2026-10-30 23:52 UTCGHSA enrichmentGHSA-993x-6558-2xmj · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-30 16:30 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  22. 2026-10-30 01:46 UTCEG score recompute
  23. 2026-10-30 01:46 UTCVendor advisory
  24. 2026-10-30 01:46 UTCGHSA enrichmentGHSA-993x-6558-2xmj · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-29 16:29 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  26. 2026-10-29 03:41 UTCEG score recompute
  27. 2026-10-29 03:41 UTCVendor advisory
  28. 2026-10-29 03:41 UTCGHSA enrichmentGHSA-993x-6558-2xmj · GitHub severity CRITICAL · GitHub CVSS 9.8
  29. 2026-10-28 16:28 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  30. 2026-10-28 05:32 UTCEG score recompute
  31. 2026-10-28 05:32 UTCVendor advisory
  32. 2026-10-28 05:32 UTCGHSA enrichmentGHSA-993x-6558-2xmj · GitHub severity CRITICAL · GitHub CVSS 9.8
  33. 2026-10-27 16:28 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  34. 2026-10-27 07:27 UTCEG score recompute
  35. 2026-10-27 07:27 UTCVendor advisory
  36. 2026-10-27 07:27 UTCGHSA enrichmentGHSA-993x-6558-2xmj · GitHub severity CRITICAL · GitHub CVSS 9.8
  37. 2026-10-26 16:28 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  38. 2026-10-26 06:32 UTCVendor advisory
  39. 2026-10-26 06:32 UTCGHSA enrichmentGHSA-993x-6558-2xmj · GitHub severity CRITICAL · GitHub CVSS 9.8
  40. 2026-10-25 17:56 UTCEG score recompute
  41. 2026-10-25 16:29 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  42. 2026-10-25 08:27 UTCEG score recompute
  43. 2026-10-25 08:27 UTCVendor advisory
  44. 2026-10-25 08:27 UTCGHSA enrichmentGHSA-993x-6558-2xmj · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  46. 2026-10-24 10:21 UTCEG score recompute
  47. 2026-10-24 10:21 UTCVendor advisory
  48. 2026-10-24 10:21 UTCGHSA enrichmentGHSA-993x-6558-2xmj · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-10-23 16:28 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  50. 2026-10-23 12:15 UTCEG score recompute
  51. 2026-10-23 12:15 UTCGHSA enrichmentGHSA-993x-6558-2xmj · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-10-22 16:30 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  53. 2026-10-22 13:59 UTCEG score recompute
  54. 2026-10-22 13:59 UTCVendor advisory
  55. 2026-10-22 13:59 UTCGHSA enrichmentGHSA-993x-6558-2xmj · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  57. 2026-10-21 15:52 UTCVendor advisory
  58. 2026-10-21 15:51 UTCGHSA enrichmentGHSA-993x-6558-2xmj · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-10-20 17:40 UTCEG score recompute
  60. 2026-10-20 17:39 UTCGHSA enrichmentGHSA-993x-6558-2xmj · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  62. 2026-10-19 19:22 UTCEG score recompute
  63. 2026-10-19 19:22 UTCVendor advisory
  64. 2026-10-19 19:22 UTCGHSA enrichmentGHSA-993x-6558-2xmj · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-10-19 16:28 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  66. 2026-10-18 21:16 UTCEG score recompute
  67. 2026-10-18 21:16 UTCVendor advisory
  68. 2026-10-18 21:16 UTCGHSA enrichmentGHSA-993x-6558-2xmj · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-10-18 16:28 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  70. 2026-10-18 08:22 UTCEG score recompute
  71. 2026-10-17 22:55 UTCEG score recompute
  72. 2026-10-17 22:55 UTCVendor advisory
  73. 2026-10-17 22:54 UTCGHSA enrichmentGHSA-993x-6558-2xmj · GitHub severity CRITICAL · GitHub CVSS 9.8
  74. 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  75. 2026-10-17 00:48 UTCEG score recompute

Frequently asked(5)

What is CVE-2022-46908?
CVE-2022-46908 is a critical-severity vulnerability; its CVE record was published on December 12, 2022. SQLite through 3.40.0, when relying on --safe for execution of an untrusted CLI script, does not properly implement the azProhibitedFunctions protection mechanism, and instead allows UDF functions such as WRITEFILE.
When was the CVE record for CVE-2022-46908 published?
The CVE record for CVE-2022-46908 was published on December 12, 2022. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2022-46908 actively exploited?
CVE-2022-46908 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-46908?
CVE-2022-46908 has a CVSS v3 base score of 7.3 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.8 (CRITICAL).
How do I remediate CVE-2022-46908?
A fix for CVE-2022-46908 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-46908 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-46908

Explore →

Is Your Infrastructure Affected by CVE-2022-46908?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.