Arbitrary file write via unvalidated workspace output paths
Published Jul 16, 2026 · Updated Jul 16, 2026
Path traversal in Microsoft Kiota before 1.29.1 and 1.30.0 through 1.32.4 allows remote attackers to write files outside the workspace. WorkspaceConfigurationStorageService deserializes .kiota/workspace.json and uses each client or plugin outputPath without rejecting rooted paths or traversal segments. Exploitation requires a developer or CI job to run a client or plugin generate command in a malicious repository, enabling writes with that process's filesystem permissions.
Summary
What happened
Path traversal in Microsoft Kiota before 1.29.1 and 1.30.0 through 1.32.4 allows remote attackers to write files outside the workspace. WorkspaceConfigurationStorageService deserializes .kiota/workspace.json and uses each client or plugin outputPath without rejecting rooted paths or traversal segments. Exploitation requires a developer or CI job to run a client or plugin generate command in a malicious repository, enabling writes with that process's filesystem permissions.
The record
- CVE
- CVE-2026-59863
- Published
- Jul 16, 2026
- Updated
- Jul 16, 2026
- Vendor
- Microsoft
- Product
- Kiota
- Classifications
- CWE-22, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 16, 2026CVE publishedPublication date reported by the CVE source.
- Jul 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.32.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Workspace outputPath advisory reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo