CVE-2026-65012

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

Score 5.3 from GitHub Security Advisory published 2026-07-22. A secondary CVSS source baseline 5.3; 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

Also known asEUVD-2026-47744 (ENISA EUVD) · GHSA-r6m9-hrqm-hx9h (GitHub Security Advisories)Source: ENISA EUVD

5.3EG
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: 5.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

InvokeAI before 6.13.7 contains an unauthenticated directory enumeration vulnerability in the GET /api/v2/models/scan_folder endpoint that accepts attacker-controlled scan_path parameters. Unauthenticated attackers can recursively enumerate arbitrary server filesystem directories and use HTTP response codes to determine file existence and readability, bypassing multi-user mode access controls.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
55
EG Risk 55/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)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 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 or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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
38th
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 (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-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-10-29). 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: 14 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 public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 22, 2026

Last Modified

October 24, 2026

Advisory Details (5)

Auto-updated Jul 22, 2026
Patch available. Sources: github_commit, github_pr, github_release.
Web page

InvokeAI < 6.13.7 Unauthenticated Directory Enumeration via scan_folder | Advisories | VulnCheck

https://www.vulncheck.com/advisories/invokeai-unauthenticated-directory-enumeration-via-scan-folder
GitHub release Patch Available

v6.13.7

Patch available: invoke-ai/InvokeAI v6.13.7

https://github.com/invoke-ai/InvokeAI/releases/tag/v6.13.7
GitHub pull request

fix(api): require auth on model-manager and app-info endpoints (#9365)

Fix merged in invoke-ai/InvokeAI PR #9367 on 2026-07-21 — awaiting tagged release

https://github.com/invoke-ai/InvokeAI/pull/9367
Web page

[Security] InvokeAI: unauthenticated arbitrary-directory enumeration via /models/scan_folder in multi-user mode · Issue #9365 · invoke-ai/InvokeAI · GitHub

https://github.com/invoke-ai/InvokeAI/issues/9365
GitHub commit

commit d315b8967f54 (invoke-ai/InvokeAI)

Fix landed in invoke-ai/InvokeAI commit d315b8967f54 — awaiting tagged release

https://github.com/invoke-ai/InvokeAI/commit/d315b8967f548732912bd9b390853ed4af97d8cb

Vendor Advisories for CVE-2026-65012(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× 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 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 216 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 116 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-65012?
CVE-2026-65012 is a medium-severity vulnerability; its CVE record was published on July 22, 2026. InvokeAI before 6.13.7 contains an unauthenticated directory enumeration vulnerability in the GET /api/v2/models/scan_folder endpoint that accepts attacker-controlled scan_path parameters. Unauthenticated attackers can recursively enumerate arbitrary server filesystem directories and use HTTP…
When was CVE-2026-65012 made public?
CVE-2026-65012 was made public on July 19, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 22, 2026. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-65012 actively exploited?
CVE-2026-65012 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-65012?
CVE-2026-65012 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-65012?
A fix for CVE-2026-65012 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-65012 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-65012?

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