CVE-2026-59866

CRITICALPre-NVD 9.39.3—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.4%, top 30% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Kiota is an OpenAPI based HTTP Client code generator. Prior to 1.29.1 and 1.32.5, Kiota emitted x-ms-kiota-info clientClassName and clientNamespaceName values without identifier or path sanitization as both generated client class or namespace names and generated output path components when kiota generate ran without -c/--class-name, allowing an attacker-controlled or compromised OpenAPI description to write generated source outside the -o output directory and inject arbitrary text into generated class or namespace declarations. This issue is fixed in version 1.29.1 and 1.32.5 by GenerationConfiguration.SanitizeClientClassName and SanitizeClientNamespaceName.

CVSS v3
9.3
EG Score
9.3(medium)
EG Risk
57(Track)
EG Risk 57/100SSVC: Track

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
Severity93% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
70%
KEV
Not listed

Published

July 16, 2026

Last Modified

August 17, 2026

Advisory Details (4)

Auto-updated Aug 23, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

Arbitrary file write + code-injection via x-ms-kiota-info clientClassName and clientNamespaceName (Microsoft Kiota) · Advisory · microsoft/kiota · GitHub

https://github.com/microsoft/kiota/security/advisories/GHSA-4vv7-jj25-4gh6
github_release Patch Available

v1.32.5

Patch available: microsoft/kiota v1.32.5

https://github.com/microsoft/kiota/releases/tag/v1.32.5
github_pr

fix: sanitizes the client class and namespace names to avoid code injection

Fix merged in microsoft/kiota PR #7884 on 2026-07-01 — awaiting tagged release

https://github.com/microsoft/kiota/pull/7884
github_commit

commit dc812dbbf88e (microsoft/kiota)

Fix landed in microsoft/kiota commit dc812dbbf88e — awaiting tagged release

https://github.com/microsoft/kiota/commit/dc812dbbf88ef7edf53a890d36b2f9d1460e947d

Vendor Advisories for CVE-2026-59866(1)

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

Affected Packages

(2 across 1 ecosystem)
NuGet(2)
PackageVulnerable rangeFixed inDependents
Microsoft.OpenApi.Kiota0.1.0-preview ... 1.9.1 (74 versions)1.32.5—
Microsoft.OpenApi.Kiota.Builder0.2.0-preview ... 1.9.1 (46 versions)1.32.5—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 55× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-01 13:54 UTCEPSS rescore
  2. 2026-09-01 04:40 UTCEPSS rescore
  3. 2026-08-30 19:34 UTCEG score recompute
  4. 2026-08-30 19:17 UTCEPSS rescore
  5. 2026-08-30 03:35 UTCEG score recompute
  6. 2026-08-30 01:22 UTCEPSS rescore
  7. 2026-08-28 21:42 UTCEPSS rescore
  8. 2026-08-27 21:27 UTCEG score recompute
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-26 22:52 UTCEG score recompute
  11. 2026-08-26 14:46 UTCEPSS rescore
  12. 2026-08-25 18:55 UTCEG score recompute
  13. 2026-08-25 13:49 UTCEPSS rescore
  14. 2026-08-24 15:10 UTCEG score recompute
  15. 2026-08-24 11:33 UTCEG score recompute
  16. 2026-08-23 01:28 UTCEG score recompute
  17. 2026-08-23 00:19 UTCEPSS rescore
  18. 2026-08-22 03:13 UTCEG score recompute
  19. 2026-08-21 23:49 UTCEPSS rescore
  20. 2026-08-21 01:31 UTCEG score recompute
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-19 23:55 UTCEG score recompute
  23. 2026-08-19 17:04 UTCEPSS rescore
  24. 2026-08-18 19:56 UTCEG score recompute
  25. 2026-08-18 13:48 UTCEPSS rescore
Show 67 more
  1. 2026-08-17 13:52 UTCEG score recompute
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-16 16:06 UTCEG score recompute
  4. 2026-08-16 14:56 UTCEPSS rescore
  5. 2026-08-16 05:13 UTCEG score recompute
  6. 2026-08-16 02:14 UTCEPSS rescore
  7. 2026-08-15 03:48 UTCEG score recompute
  8. 2026-08-15 01:30 UTCEPSS rescore
  9. 2026-08-13 22:47 UTCEG score recompute
  10. 2026-08-13 22:00 UTCEPSS rescore
  11. 2026-08-12 14:04 UTCEG score recompute
  12. 2026-08-12 13:51 UTCEPSS rescore
  13. 2026-08-11 16:14 UTCEG score recompute
  14. 2026-08-11 01:44 UTCEG score recompute
  15. 2026-08-11 00:00 UTCEPSS rescore
  16. 2026-08-09 17:02 UTCEG score recompute
  17. 2026-08-09 13:46 UTCEPSS rescore
  18. 2026-08-08 19:16 UTCEG score recompute
  19. 2026-08-08 16:37 UTCEPSS rescore
  20. 2026-08-07 17:52 UTCEG score recompute
  21. 2026-08-06 16:24 UTCEG score recompute
  22. 2026-08-06 13:47 UTCEPSS rescore
  23. 2026-08-05 22:16 UTCEG score recompute
  24. 2026-08-05 19:17 UTCEPSS rescore
  25. 2026-08-04 16:38 UTCEG score recompute
  26. 2026-08-04 15:10 UTCEPSS rescore
  27. 2026-08-04 13:01 UTCEG score recompute
  28. 2026-08-04 10:39 UTCEPSS rescore
  29. 2026-08-03 13:48 UTCEG score recompute
  30. 2026-08-03 10:36 UTCEPSS rescore
  31. 2026-08-02 05:01 UTCEG score recompute
  32. 2026-08-02 02:27 UTCEPSS rescore
  33. 2026-08-01 07:14 UTCEG score recompute
  34. 2026-08-01 04:16 UTCEPSS rescore
  35. 2026-07-30 21:40 UTCEG score recompute
  36. 2026-07-30 16:28 UTCEPSS rescore
  37. 2026-07-30 12:00 UTCEG score recompute
  38. 2026-07-30 03:01 UTCEG score recompute
  39. 2026-07-30 01:30 UTCEPSS rescore
  40. 2026-07-30 01:30 UTCEPSS rescore
  41. 2026-07-29 19:38 UTCEG score recompute
  42. 2026-07-29 18:34 UTCEG score recompute
  43. 2026-07-28 18:55 UTCEG score recompute
  44. 2026-07-28 15:37 UTCEPSS rescore
  45. 2026-07-27 16:44 UTCEG score recompute
  46. 2026-07-27 14:14 UTCEPSS rescore
  47. 2026-07-26 15:06 UTCEG score recompute
  48. 2026-07-26 14:54 UTCEPSS rescore
  49. 2026-07-26 14:54 UTCEPSS rescore
  50. 2026-07-26 11:25 UTCEG score recompute
  51. 2026-07-25 14:18 UTCEPSS rescore
  52. 2026-07-25 14:18 UTCEPSS rescore
  53. 2026-07-24 14:18 UTCEPSS rescore
  54. 2026-07-24 14:18 UTCEPSS rescore
  55. 2026-07-23 14:18 UTCEPSS rescore
  56. 2026-07-23 14:18 UTCEPSS rescore
  57. 2026-07-23 03:21 UTCEG score recompute
  58. 2026-07-22 14:08 UTCEPSS rescore
  59. 2026-07-22 14:08 UTCEPSS rescore
  60. 2026-07-21 15:25 UTCEPSS rescore
  61. 2026-07-21 15:25 UTCEPSS rescore
  62. 2026-07-20 17:08 UTCEPSS rescore
  63. 2026-07-19 14:31 UTCEPSS rescore
  64. 2026-07-19 02:29 UTCEPSS rescore
  65. 2026-07-18 10:04 UTCEPSS rescore
  66. 2026-07-16 15:24 UTCEG score recompute
  67. 2026-07-16 15:23 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-59866?
CVE-2026-59866 is a critical vulnerability published on July 16, 2026. Kiota is an OpenAPI based HTTP Client code generator. Prior to 1.29.1 and 1.32.5, Kiota emitted x-ms-kiota-info clientClassName and clientNamespaceName values without identifier or path sanitization as both generated client class or namespace names and generated output path components when kiota…
When was CVE-2026-59866 disclosed?
CVE-2026-59866 was first published in the National Vulnerability Database on July 16, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59866 actively exploited?
CVE-2026-59866 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 30.3% of all scored CVEs.
What is the CVSS score of CVE-2026-59866?
CVE-2026-59866 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2026-59866?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59866, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-59866

Explore →

Is Your Infrastructure Affected by CVE-2026-59866?

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

Start Free Scan →Browse All CVEs