CVE-2026-50006

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-14. A secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
9.1EG
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: 1.0%CVSS: 9.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Anyquery is an SQL query engine built on top of SQLite. Prior to 0.4.5, anyquery server forwards unauthenticated SQL from its MySQL-compatible server port to SQLite without restricting ATTACH DATABASE filesystem targets. A remote attacker can select any path writable by the Anyquery server process, cause SQLite to create a database file there, and place attacker-controlled table content in that file. This permits arbitrary file creation or overwrite, causing filesystem integrity loss and denial of service; remote code execution is possible only when another service interprets the written file or the process has a suitably privileged writable target. This issue is fixed in version 0.4.5.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
72
EG Risk 72/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (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 yes (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
1.0%
EPSS %ILE
61st
KEV
Not listed

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 yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

July 14, 2026

Last Modified

September 30, 2026

Advisory Details (3)

Auto-updated Sep 15, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

Arbitrary File Write (AFW) which could lead to Remote Code Execution (RCE) via Unrestricted ATTACH DATABASE in Server Mode · Advisory · julien040/anyquery · GitHub

https://github.com/julien040/anyquery/security/advisories/GHSA-xrcf-6jh3-ggvx
GitHub release Patch Available

0.4.5 - Security fixes

Patch available: julien040/anyquery 0.4.5

https://github.com/julien040/anyquery/releases/tag/0.4.5
GitHub commit

commit 27f84fc16831 (julien040/anyquery)

Fix landed in julien040/anyquery commit 27f84fc16831 — awaiting tagged release

https://github.com/julien040/anyquery/commit/27f84fc168310455eaf81ec4ba87eed20298670c

Vendor Advisories for CVE-2026-50006(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/julien040/anyquery—ghsa

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

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/julien040/anyquery—
  • every version on: no fix on record
—

Weakness Classification(5)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 51× 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 287 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 187 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-50006?
CVE-2026-50006 is a critical-severity vulnerability; its CVE record was published on July 14, 2026. Anyquery is an SQL query engine built on top of SQLite. Prior to 0.4.5, anyquery server forwards unauthenticated SQL from its MySQL-compatible server port to SQLite without restricting ATTACH DATABASE filesystem targets. A remote attacker can select any path writable by the Anyquery server process,…
When was the CVE record for CVE-2026-50006 published?
The CVE record for CVE-2026-50006 was published on July 14, 2026. 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 September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-50006 actively exploited?
CVE-2026-50006 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (61st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50006?
CVE-2026-50006 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-50006?
A fix for CVE-2026-50006 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50006 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-2026-50006

Explore →

Is Your Infrastructure Affected by CVE-2026-50006?

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