CVE-2026-19200

HIGHPre-NVD 8.98.9
EchelonGraph scoreMEDIUM confidence

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

Score 8.9 from GitHub Security Advisory (severity: HIGH) published 2026-08-24. A secondary CVSS source baseline 8.9; 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 week
8.9EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.9Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

The Velociraptor verify() VQL function allows a user to verify an artifact for syntatic and other issues. Due to an implementation fault in this VQL function, the global artifact repository is used which allows callers to overwrite existing artifacts without the required permissions.  The attacker need only have the NOTEBOOK_EDIT permission (e.g. an analyst role) to be able to call this function.

CVSS v3
8.9
EG Score
8.9HIGHmedium confidence
EG Risk
40
EG Risk 40/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)
Severity89% × 45%
The EG Score, 8.9 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (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: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.2%
EPSS %ILE
12th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

Exploitation none (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.

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

August 24, 2026

Last Modified

October 12, 2026

Advisory Details (2)

Auto-updated Aug 24, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
GitHub pull request

Bugfix: Only allow OrgId to be set from HTTP headers

Fix merged in Velocidex/velociraptor PR #4962 on 2026-08-07 — awaiting tagged release

https://github.com/Velocidex/velociraptor/pull/4962
Web page

CVE-2026-19200 Analyst overwrites live built-in artifacts through …

http://docs.velociraptor.app/announcements/advisories/cve-2026-19200/

Vendor Advisories for CVE-2026-19200(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-19200?
CVE-2026-19200 is a high-severity vulnerability; its CVE record was published on August 24, 2026. The Velociraptor verify() VQL function allows a user to verify an artifact for syntatic and other issues. Due to an implementation fault in this VQL function, the global artifact repository is used which allows callers to overwrite existing artifacts without the required permissions. The attacker…
When was the CVE record for CVE-2026-19200 published?
The CVE record for CVE-2026-19200 was published on August 24, 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 October 12, 2026; the record at its source may have been updated since.
Is CVE-2026-19200 actively exploited?
CVE-2026-19200 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-19200?
CVE-2026-19200 has a CVSS base score of 8.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-19200?
An upstream fix for CVE-2026-19200 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-19200 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-19200

Explore →

Is Your Infrastructure Affected by CVE-2026-19200?

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

Book a Demo →Browse All CVEs