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

> An unauthenticated remote attacker can cause a denial of service via a nil-pointer panic in kin-openapi by sending crafted array parameters or bodies.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** CLEANSTART-2026-KH25643, ECHO-3b34-ae40-bbcf, GHSA-vrcc-3ch7-hppw, MINI-2wqf-8h3q-m5cx, MINI-5mjx-m6cp-g8v4, MINI-73h7-74q6-pxwv, MINI-f47j-8674-4qv7, MINI-f9h2-qv92-f5jq, MINI-h43h-g8p9-pq2w, MINI-hcfw-pwqg-2722, MINI-hhx3-3732-3fcx, MINI-p72g-chf3-x83v, MINI-qccf-779v-v42f, MINI-qwr9-v4fq-m245, MINI-rg8m-7wf7-wwr2, MINI-xc9f-5cfv-4h55, MINI-xqr6-f699-4hr7, UBUNTU-CVE-2026-100353

## What is CVE-2026-100353?

CVE-2026-100353 is a high-severity vulnerability in getkin kin-openapi, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 property, or an application/x-www-form-urlencoded request body whose array property appears inside an allOf, anyOf, or oneOf subschema. The query and composed-body paths reach urlValuesDecoder.parseArray, while the deepObject path reaches buildResObj, and all pass a nil items schema into code that dereferences it. This issue is fixed in version 0.149.0.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2026-100353?

2 open source packages ship an affected version, including github.com/getkin/kin-openapi.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/getkin/kin-openapi` | Go | From 0.136.0 | 0.149.0 |
| `github.com/getkin/kin-openapi` | Go | From 0.136.0 | 0.149.0 |

## How do I fix CVE-2026-100353?

Upgrade github.com/getkin/kin-openapi to 0.149.0 or later.

## Is CVE-2026-100353 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100353 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-100353 and fix it if it is affected.

What it is: CVE-2026-100353 is a high-severity vulnerability in getkin kin-openapi, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100353 exists.

Affected packages and fixed versions:
- github.com/getkin/kin-openapi (Go): affected from 0.136.0; fixed in 0.149.0
- github.com/getkin/kin-openapi (Go): affected from 0.136.0; fixed in 0.149.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-100353/ (Markdown: https://insights.sbomify.com/CVE-2026-100353/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-100353
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-100353
- OSV: https://osv.dev/vulnerability/CVE-2026-100353

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-100353/
Summaries are generated and may contain mistakes; the official description above is the record.