dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-59860

HIGH · 8.7 CVSS v4.0 Published 2026-07-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable No privileges 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Kiota is an OpenAPI based HTTP Client code generator. Prior to 1.29.1 and 1.32.3, Kiota is affected by a code-generation injection vulnerability in the C# XML documentation-comment sink (the description, externalDocs label, and externalDocs link fields emitted as /// … comments). When text from an OpenAPI description is written into single-line XML doc comments without stripping newline and Unicode line-terminator characters, an attacker can break out of the /// comment line and inject additional code into generated C# clients. This issue is fixed in version 1.29.1 and 1.32.3.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Kiota is an OpenAPI-based HTTP client code generator. The vulnerability exists in the C# XML documentation-comment generation where OpenAPI description fields (description, externalDocs label, and externalDocs link) are emitted as XML doc comments (/// ...) without properly sanitizing newline and Unicode line-terminator characters. This allows an attacker who controls the OpenAPI specification to break out of the single-line comment and inject arbitrary C# code into generated client files.

MitigationUpgrade Kiota to version 1.29.1 or 1.32.3 or later to receive the fix that properly sanitizes newline characters before emitting them into XML doc comments.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Kiota version
    Run 'kiota --version' or inspect the kiota binary metadata
    Affected if version is below 1.32.3 (any version prior to 1.32.3)
  2. Identify target language for code generation
    Review your kiota command or build pipeline to confirm C# (csharp) is the target language
    Affected if C# code generation is in use
  3. Locate OpenAPI source file
    Find the OpenAPI specification file (JSON/YAML) used as input for code generation
    Affected if the OpenAPI spec is accessible for inspection
  4. Inspect OpenAPI description fields for line breaks
    Search the OpenAPI spec for 'description:' fields and check if any contain newline characters (\n, \r\n) or Unicode line terminators within their values
    Affected if any description field (including in info, paths, operations, components, or externalDocs) contains embedded newline or line-terminator characters

You are affected if Kiota version is prior to 1.32.3 AND you are generating C# client code from an OpenAPI specification that contains description fields with embedded newline or line-terminator characters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Kiota to version 1.29.1 or 1.32.3 or later to receive the fix that properly sanitizes newline characters before emitting them into XML doc comments.

Recommended fix High confidence

1.32.3

  1. Identify the current Kiota version by running `kiota --version`
  2. Review the release notes for version 1.32.3 to check for any breaking changes relevant to your generated clients
  3. Upgrade Kiota to version 1.32.3 using the package manager or installation method originally used (e.g., dotnet tool update --global Microsoft.Kiota.Cli, or download the new release)
  4. Verify the upgrade was successful by running `kiota --version` and confirming it shows 1.32.3 or later
  5. Regenerate any existing C# client codebases using the upgraded Kiota to ensure the XML documentation comments are properly sanitized
  6. Test the regenerated clients to confirm functionality is intact
Caveat Review version 1.32.3 release notes; minor version upgrades in Kiota typically don't introduce breaking changes in generated code, but verify regenerated client compiles successfully

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-59860 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-59860 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data