ZeroDay Findings
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-100353

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

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

Check if you run it

No confirmed exploitation is on record for CVE-2026-100353. EPSS is 0.34%. 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
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.34%
Remediation
Version ranges on file
Affected products
go github.com/getkin/kin-openapi · golang github.com

## Summary The fix for GHSA-p6wj-qrr4-pgh5 addressed a nil-pointer dereference that occurs when an OpenAPI 3.1 array schema omits the keyword (which is legal under JSON Schema 2020-12). That fix patched three decoder paths: the standalone function, the top-level array check in , and . Three additional crash paths were missed. All of them reach the unguarded method ( ) or the unguarded array branch in (line 1015): 1. **Query parameters** with and no . 2. **deepObject** query parameters containing an array property with no . 3. **URL-encoded request bodies** where the array lives inside an / / sub-schema. This path bypasses the guard added by the GHSA-p6wj-qrr4-pgh5 fix, because that guard only inspects top-level properties. Each path is triggerable by an unauthenticated client and produces a deterministic nil-pointer panic during request validation. ## Details ### Root Cause The three paths patched for GHSA-p6wj-qrr4-pgh5 each received a nil- guard: But (line 576), which handles query-parameter and urlencoded-body array decoding, has **no** such guard: immediately dereferences the schema it is handed: For the deepObject path, (line 1015) has the same gap. Its array branch recurses with (line 1028), which can be nil, and the recursive call dereferences it at line 1015: For the allOf body path, validates only top-level (line 1429-1449). But (line 1474) recursively walks / / sub-schemas and calls on their properties, which never pass through the top-level guard and reach . ## Proof of Concept ### Environment - kin-openapi v0.144.0 (cloned at tag , commit ) - Go 1.26.7 - Each PoC calls first to prove the spec is legal, then drives directly ### Path 1: Query parameter array without items Spec (query param is , no ), request : ### Path 2: deepObject nested array without items Spec (deepObject param with array property , no ), request : ### Path 3: URL-encoded body with array inside allOf (bypasses the existing fix) Spec (urlencoded body, sub-schema with array property , no

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.

  • go github.com/getkin/kin-openapi>= 0.136.0, < 0.149.0
  • go github.com/getkin/kin-openapi>=0.136.0 <0.149.0
  • golang github.comversion unspecified

How to fix CVE-2026-100353

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-100353. EPSS is 0.34%. 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.136.0, < 0.149.0, >=0.136.0 <0.149.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.34%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

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. From 0.136.0 until 0.149.0, three openapi3filter decoder paths that were missed by the fix for GHSA-p6wj-qrr4-pgh5 lack a nil-items guard for legal OpenAPI 3.1 array schemas. An unauthenticated remote client can trigger a deterministic nil-pointer panic through an array query parameter, a deepObject query parameter containing an array propert

  2. Oct 15, 2026 · NIST NVD

    Updated

    kin-openapi is a Go project for handling OpenAPI files. From 0.136.0 until 0.149.0, three openapi3filter decoder paths that were missed by the fix for GHSA-p6wj-qrr4-pgh5 lack a nil-items guard for legal OpenAPI 3.1 array schemas. An unauthenticated remote client can trigger a deterministic nil-pointer panic through an array query parameter, a deepObject query parameter containing an array propert

  3. Oct 15, 2026 · GitHub Advisory Database

    Updated

    ## Summary The fix for GHSA-p6wj-qrr4-pgh5 addressed a nil-pointer dereference that occurs when an OpenAPI 3.1 array schema omits the keyword (which is legal under JSON Schema 2020-12). That fix patched three decoder paths: the standalone function, the top-level array check in , and . Three additional crash paths were missed. All of them reach the unguarded method ( ) or the unguarded array branch

Sources

  • CVE.orgVulnerability recordCVE-2026-100353

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-100353

    30-day exploitation probability 0.3%

    first.org
  • GitHub Advisory DatabasePackage advisoryGHSA-vrcc-3ch7-hppw

    kin-openapi: Incomplete Fix for GHSA-p6wj-qrr4-pgh5: Three Unpatched nil-Items Panic Paths in openapi3filter

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

    The fix for GHSA-p6wj-qrr4-pgh5 addressed a nil-pointer dereference that occurs when an OpenAPI 3.1 array schema omits the items keyword (which is legal under JSON Schema 2020-12). That fix patched three decoder paths: the standalone parseArray function, the top-level array check in UrlencodedBodyDecoder, and MultipartBodyDecoder. Three additional crash paths were missed. All of them reach the ung

    advisories.gitlab.com
  • GitLab Advisory DatabasePackage advisorygo/github.com/getkin/kin-openapi/CVE-2026-100353.yml

    The fix for GHSA-p6wj-qrr4-pgh5 addressed a nil-pointer dereference + that occurs when an OpenAPI 3.1 array schema omits the keyword (which is + legal under JSON Schema 2020-12). That fix patched three decoder paths: the standalone + function, the top-level array check in , and + .\n\nThree additional crash paths were missed. All of them + reach the unguarded method (`openapi3filter/req_resp_deco

    gitlab.com
  • NIST NVDVulnerability recordCVE-2026-100353

    kin-openapi is a Go project for handling OpenAPI files. From 0.136.0 until 0.149.0, three openapi3filter decoder paths that were missed by the fix for GHSA-p6wj-qrr4-pgh5 lack a nil-items guard for legal OpenAPI 3.1 array schemas. An unauthenticated remote client can trigger a de

    nvd.nist.gov

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.