Code Injection in openapi-python-client (CVE-2026-105801)
Summary
Code injection in openapi-python-client (CVE-2026-105801). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.29.1 or later.
Original description
The description as published by the source.
Impact
A malicious OpenAPI document processed by any openapi-python-client prior to 0.29.1 can generate arbitrary Python code. When anyone imports the malicious client, that arbitrary Python code will execute.
Patches
Versions starting with 0.29.1 have updated with guardrails to prevent arbitrary code generation. Upgrade to this version immediately and audit any code previously generated from untrusted documents.
Workarounds
Do not generate clients for documents you don't completely trust. Carefully verify any existing generated code from untrusted documents.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-105801 has been found in openapi-python-client.
Risk of unauthorized operations or information disclosure.
What to do: upgrade openapi-python-client to 0.29.1 or later.
If unsure, ask your IT team or search "openapi-python-client CVE-2026-105801" on the vendor's site.
CVE-2026-105801 (openapi-python-client) — CWE-94
Patched: 0.29.1 — apply immediately
Workaround: Do not generate clients for documents you don't completely trust.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Arbitrary code execution (CWE-94) exists in openapi-python-client.
Check the vendor advisory for the affected versions of openapi-python-client.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.29.1.
Workaround: Do not generate clients for documents you don't completely trust.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'openapi-python-client' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'openapi-python-client' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
openapi-python-clientを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Do not generate clients for documents you don't completely trust.パッチが適用されるまでの応急処置として、Do not generate clients for documents you don't completely trust. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade openapi-python-client to 0.29.1ステージング環境で 0.29.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- package pypi.org
- web github.com
- web github.com
- web github.com
- web github.com