CVE-2022-26969

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-04-05. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2022-1731 (ENISA EUVD) · GHSA-g27j-74fp-xfpr (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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In Directus before 9.7.0, the default settings of CORS_ORIGIN and CORS_ENABLED are true.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/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.
Exploitation1.0% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (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
63rd
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
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 or medium mission impact; Attend at high (mission-essential systems).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 or medium mission impact; Attend at high (mission-essential systems).

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

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

December 26, 2022

Last Modified

April 14, 2025

Advisory Details (5)

Auto-updated Oct 10, 2026
Patch available. Sources: github_pr, github_release.
Web page

Insecure Defaults in directus | CVE-2022-26969 | Snyk

https://security.snyk.io/vuln/SNYK-JS-DIRECTUS-2441822
GitHub release Patch Available

v9.7.0

Patch available: directus/directus v9.7.0

https://github.com/directus/directus/releases/tag/v9.7.0
GitHub pull request

Default CORS to disabled

Fix merged in directus/directus PR #12022 on 2022-03-07 — awaiting tagged release

https://github.com/directus/directus/pull/12022
Web page

directus/docs/configuration/config-options.md at 8daed9c41baeaf1d08c1e292bf9f0dcef65e48fb · directus/directus · GitHub

https://github.com/directus/directus/blob/8daed9c41baeaf1d08c1e292bf9f0dcef65e48fb/docs/configuration/config-options.md
Web page

Cross-Origin Resource Sharing (CORS) - HTTP | MDN

https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS

Vendor Advisories for CVE-2022-26969(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
npmdirectus @ 9.7.0 (fixes < 9.7.0)—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)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
directus—
  • every version up to 9.7.0: fixed in 9.7.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 44× 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 251 rows on record for this CVE, as 99 entries (1 repeat merged).

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. 1 repeat row among the latest 100 is merged into the row it repeats. The 151 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2022-26969?
CVE-2022-26969 is a critical-severity vulnerability; its CVE record was published on December 26, 2022. In Directus before 9.7.0, the default settings of CORS_ORIGIN and CORS_ENABLED are true.
When was the CVE record for CVE-2022-26969 published?
The CVE record for CVE-2022-26969 was published on December 26, 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 April 14, 2025; the record at its source may have been updated since.
Is CVE-2022-26969 actively exploited?
CVE-2022-26969 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (63rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-26969?
CVE-2022-26969 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2022-26969?
A fix for CVE-2022-26969 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-26969 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-26969

Explore →

Is Your Infrastructure Affected by CVE-2022-26969?

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

Book a Demo →Browse All CVEs