Security readout for executives and security teams
Plain-English summary
Kiota can turn malicious text in an OpenAPI description into executable code inside a generated client. The main risk arises when teams generate clients from untrusted or tampered API descriptions. Successful abuse could compromise the confidentiality, integrity, and availability of the system where the generated code is built or run.
Executive priority
Prioritize remediation for teams that ingest third-party specifications or automate client generation. Upgrade and regenerate promptly in those environments. Trusted, integrity-protected specifications substantially reduce practical risk, but existing generated clients still warrant review because vulnerable output may persist.
Technical view
Affected Kiota releases fail to apply context-appropriate escaping across multiple code-writer sinks, including serialization keys, parameter mappings, URL metadata, enums, properties, and default values. Crafted OpenAPI values can escape generated string literals and inject source code. The issue is classified as CWE-94 and scored CVSS 4.0 7.3.
Likely exposure
Exposure is highest in development, CI, or supply-chain workflows that generate clients from external, user-supplied, or insufficiently integrity-protected OpenAPI descriptions. Previously generated clients may retain unsafe injected output even after Kiota itself is upgraded, making regeneration and review important.
Exploitation context
Practical exploitation requires an attacker-controlled or compromised OpenAPI description and a user or automated workflow to generate code from it. The supplied record marks this CVE as absent from KEV and provides no evidence of active exploitation. The CVSS vector describes local access, low complexity, a prerequisite condition, and user interaction.
Researcher notes
The vulnerability spans several language-writer output contexts rather than one isolated sink. Assessment should consider both generator versions and the provenance of every input description. The supplied affected ranges are versions below 1.29.1 and versions 1.30.0 through 1.31.0. No exploit activity or additional affected products are established by the bundle.
Mitigation direction
- Upgrade Kiota to version 1.29.1, 1.31.1, or later.
- Regenerate existing clients with the upgraded Kiota release.
- Accept OpenAPI descriptions only from trusted, integrity-protected sources.
- Review vendor guidance for any later branch-specific remediation advice.
Validation and detection
- Inventory Kiota versions used locally and in CI pipelines.
- Identify clients generated from untrusted or potentially modified OpenAPI descriptions.
- Confirm OpenAPI provenance and integrity controls across generation workflows.
- Regenerate clients and review resulting changes for unexpected executable code.
- Verify refreshed clients build and pass established security and regression tests.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-41134 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
7.3HighVector: CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/microsoft/kiota/security/advisories/GHSA-2hx3-vp6r-mg3fCVE reference, GitHub_M · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.