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
Elevated

Also known asEUVD-2026-77809 (ENISA EUVD) · GHSA-xrcf-6jh3-ggvx (GitHub Security Advisories) · GO-2026-5979 (OSV.dev)Source: ENISA EUVD

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 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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 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.
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
62nd
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.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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: 3 days if the affected system is publicly exposed; 60 days 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 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.

The score's inputs: 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 / 60× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 380 rows 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 280 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Same product

3 shown

Go:github.com/julien040/anyquery

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 (62nd 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.

Book a Demo →Browse All CVEs