ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-100349

kin-openapi is a Go project for handling OpenAPI files.

Published Oct 15, 2026 · catalog updated Oct 16, 2026 · kin-openapi is a Go

Check if you run it

No confirmed exploitation is on record for CVE-2026-100349. EPSS is 0.37%. Act only if a listed version of kin-openapi is a Go is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (kin-openapi is a Go).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High8.2
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.37%
Remediation
Version ranges on file
Affected products
Debian:12 golang-github-getkin-kin-openapi · Debian:13 golang-github-getkin-kin-openapi · Debian:14 golang-github-getkin-kin-openapi · Go github.com/getkin/kin-openapi · go github.com/getkin/kin-openapi · golang github.com

## Summary panics on a nil pointer when a spec declares a response header with instead of . accepts that document, so the crash comes from a spec the library just called valid. Same class as GHSA-jpcw-4wr7-c3vq, which covered the request-parameter case in v0.144.0; this is the response-header path. Affects . Reproduced on master , Go 1.26. ## Details A -typed response header has . passes it straight through: and is where it lands: Two things I checked rather than assumed. The response does not need to carry the header; declaring it is enough, and then every call for that operation panics. And the body path is fine, returns early on a nil schema, so this is headers only. The PoC keeps the body case as a control. ## PoC Drop into and run: Output: The is the point: control passes, the header case takes the binary down. Ran in a container against a fresh clone of master. I have not tried it against a live proxy. ## Impact A process crash instead of an error return. Declaring the header is enough, so it is every call on that operation rather than an occasional one. If the spec comes from somewhere else -- gateways, linters, anything ingesting specs it did not write -- that is a trust boundary, and it becomes remote availability. If it is your own spec, nothing attacker-controlled starts it, but any client reaching that route then crashes the process. It fires on every call, so normally you would see it the first time that route runs. A spec edited without exercising the route is the case where you would not. That is the difference from GHSA-jpcw, where the attacker supplied the trigger. I have left severity unset; the two cases do not score the same. On how common it is, I checked rather than guessed. Of roughly 1,500 OpenAPI 3.x specs on apis.guru, one declares content-typed response headers -- VTEX Catalog API -- and not in one corner of it: the shape repeats across its operations, so for that consumer this is not an edge case. The header names in it ( , , a few malfor

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Debian:12 golang-github-getkin-kin-openapi0.110.0-1, 0.117.0-1, 0.118.0-1
  • Debian:13 golang-github-getkin-kin-openapi0.124.0-1, 0.135.0-1
  • Debian:14 golang-github-getkin-kin-openapi0.124.0-1, 0.135.0-1
  • Go github.com/getkin/kin-openapi0 → 0.146.0
  • go github.com/getkin/kin-openapi<= 0.145.0
  • golang github.comversion unspecified

How to fix CVE-2026-100349

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-100349. EPSS is 0.37%. Act only if a listed version of kin-openapi is a Go is installed.

Which versions are affected?

Compare what you have installed with 0.110.0-1, 0.117.0-1, 0.118.0-1, 0.124.0-1, 0.135.0-1, 0 → 0.146.0, <= 0.145.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-476: NULL Pointer Dereference. EPSS 0.37%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Debian security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 15, 2026 · NIST NVD

    Detected

    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 contai

  2. Oct 15, 2026 · NIST NVD

    Updated

    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 contai

  3. Oct 16, 2026 · OpenSSF OSV / OSV Scanner

    Updated

    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 contai

  4. Oct 16, 2026 · GitHub Advisory Database

    Fix available

    github.com/getkin/kin-openapi fixed in 0.146.0

  5. Oct 16, 2026 · GitHub Advisory Database

    Fix available

    github.com/getkin/kin-openapi fixed in 0.146.0

  6. Oct 16, 2026 · GitHub Advisory Database

    Updated

    ## Summary panics on a nil pointer when a spec declares a response header with instead of . accepts that document, so the crash comes from a spec the library just called valid. Same class as GHSA-jpcw-4wr7-c3vq, which covered the request-parameter case in v0.144.0; this is the response-header path. Affects . Reproduced on master , Go 1.26. ## Details A -typed response header has . passes it straig

Sources

  • CVE.orgVulnerability recordCVE-2026-100349

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-100349

    30-day exploitation probability 0.4%

    first.org
  • GitHub Advisory DatabasePackage advisoryGHSA-74vm-87hj-r66f

    GitHub Advisory Database record mirrored by OSV.

    github.com
  • GitLab Advisory DatabasePackage advisoryCVE-2026-100349

    ValidateResponse panics on a nil pointer when a spec declares a response header with content instead of schema. doc.Validate() accepts that document, so the crash comes from a spec the library just called valid. Same class as GHSA-jpcw-4wr7-c3vq, which covered the request-parameter case in v0.144.0; this is the response-header path. Affects github.com/getkin/kin-openapi <= v0.145.0. Reproduced on

    advisories.gitlab.com
  • Go Vulnerability DatabasePackage advisoryGHSA-74vm-87hj-r66f

    kin-openapi openapi3filter: nil-pointer panic in ValidateResponse on a response header declared with content

    osv.dev
  • NIST NVDVulnerability recordCVE-2026-100349

    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 resp

    nvd.nist.gov
  • OpenSSF OSV / OSV ScannerPackage advisoryDEBIAN-CVE-2026-100349
    osv.dev
  • OpenSSF OSV / OSV ScannerPackage advisoryGHSA-74vm-87hj-r66f

    kin-openapi openapi3filter: nil-pointer panic in ValidateResponse on a response header declared with content

    osv.dev

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.