Vulnerability in github.com/getkin/kin-openapi (CVE-2026-73502)
Summary
Vulnerability in github.com/getkin/kin-openapi (CVE-2026-73502). Risk of unauthorized operations or information disclosure. Exploitable via HEAD. Mitigation: upgrade to 0.144.0 or later.
Original description
The description as published by the source.
Nil-pointer panic on content parameter without schema in github.com/getkin/kin-openapi
Source: GitHub Security Advisories (Global) 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-73502 has been found in github.com/getkin/kin-openapi.
Attackers can target a specific entry point like HEAD over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade github.com/getkin/kin-openapi to 0.144.0 or later.
If unsure, ask your IT team or search "github.com/getkin/kin-openapi CVE-2026-73502" on the vendor's site.
CVE-2026-73502 (github.com/getkin/kin-openapi) — CWE-476 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: HEAD / openapi3filter.ValidateRequest / content / schema
Patched: 0.144.0 — apply immediately
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.
A vulnerability (CWE-476) exists in github.com/getkin/kin-openapi. Attackers reach the vulnerable code path via HEAD without authentication.
Check the vendor advisory for the affected versions of github.com/getkin/kin-openapi. Attack surface: HEAD / openapi3filter.ValidateRequest / content / schema.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 0.144.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/getkin/kin-openapi' . 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 'github.com/getkin/kin-openapi' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/getkin/kin-openapiを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/getkin/kin-openapi to 0.144.0ステージング環境で 0.144.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-73502 golang-github-getkin-kin-openapi
- Ubuntu UBUNTU-CVE-2026-73502 golang-github-getkin-kin-openapi
References
- advisory github.com
- patch github.com
- web github.com
- web github.com