getkin kin-openapi Flaw (CVE-2026-100349) Rated CVSS 8.2
A newly published high vulnerability in getkin kin-openapi carries a CVSS score of 8.2. Here is what is affected and how to respond.
Key points
- CVE-2026-100349 affects getkin kin-openapi.
- CVSS 8.2 (High).
- No exploitation confirmed yet.
getkin kin-openapi is affected by CVE-2026-100349, a security flaw that the National Vulnerability Database rates 8.2 out of 10.
At a glance
- CVE
- CVE-2026-100349
- Product
- getkin kin-openapi
- CVSS
- 8.2 High
- Weakness
- CWE-476
- Exploited
- No known exploitation
What is the vulnerability?
The NVD entry states: kin-openapi is a Go project for handling OpenAPI files. Prior to 0.146.0, openapi3filter.ValidateResponse passes a nil response header schema to decodeValue when an OpenAPI document declares the header with content instead of schema. The document passes validation, but every response validation for the affected operation dereferences the nil schema and panics even when the response does not contain the declared header. Applications that ingest an untrusted specification can expose this as remote availability impact, while applications using only trusted local specifications still crash when the affected operation is exercised. This issue is fixed in version 0.146.0.
Affected versions
| Vendor | Product | Versions |
|---|---|---|
| Getkin | kin-openapi | < 0.146.0 |
Is it being exploited?
There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.
What should you do?
- Identify whether the affected product and versions run in your environment.
- Apply the vendor update listed in the advisory as soon as it is available.
- Limit network exposure of the affected service until it is patched.
- Monitor the vendor advisory for updated guidance or exploitation reports.
What to do and how to stay safe: CVE-2026-100349
- Vulnerability severity scores ignore your specific architecture and context.
- Exploitability depends on network exposure and user behavior, not just code flaws.
- Prioritization requires continuous asset inventory and threat intelligence alignment.
Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.
Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-100349?
CVE-2026-100349 is a CWE-476 vulnerability in getkin kin-openapi.
How severe is CVE-2026-100349?
It has a CVSS score of 8.2 High.
Is CVE-2026-100349 being exploited?
There is no public confirmation of exploitation at the time of publication.
