# CVE-2026-100352: kin-openapi: YAML NaN/Inf Values Bypass Built-in Guards and Panic via OAS 3.1 Validation Path

> Remote attackers can cause a denial of service by sending YAML NaN or infinity values that bypass validation guards and trigger a panic in the kin-openapi library.

- **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:** 20 Oct 2026
- **Also known as:** CLEANSTART-2026-MH48139, DEBIAN-CVE-2026-100352, ECHO-46ca-0724-4961, GHSA-rj39-cv6w-8wv7, MINI-2w9m-2h26-9rq8, MINI-2wgq-c2mw-54v8, MINI-3459-4c7m-522r, MINI-3fpg-gfvw-gjp2, MINI-4766-6m68-46jw, MINI-63cx-mgc5-4959, MINI-6j9c-r28x-q85h, MINI-6m3w-6wwh-5vw3, MINI-769p-2hc6-7rjf, MINI-83wf-5c55-hgqr, MINI-8gcw-gxvj-hwxc, MINI-8hj2-gh38-jpjq, MINI-9hxm-77rg-6873, MINI-9w63-337p-mjf7, MINI-f3gv-5q9j-x7fp, MINI-f972-26qw-mwpg, MINI-g89v-pr72-28wh, MINI-m64j-gh37-gv5m, MINI-p5pf-56q7-q8h9, MINI-qf73-55mj-9373, MINI-rw4r-h534-92qv, MINI-vg9j-mpc7-4chh, MINI-vvxq-g34j-wfh3, MINI-ww87-w2w5-cc33, MINI-x23j-jp7q-w3hf, MINI-x5mm-f5qh-gm98, UBUNTU-CVE-2026-100352

## What is CVE-2026-100352?

CVE-2026-100352 is a high-severity denial of service 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. Prior to 0.148.0, the OpenAPI 3.1 validation path passes YAML NaN and infinity numeric values to santhosh-tekuri/jsonschema v6.0.2 without applying kin-openapi's existing finite-number guards. A remote unauthenticated client can send an application/yaml or application/x-yaml request body containing .nan, .inf, or -.inf to an operation with a numeric constraint, causing the dependency to create and dereference a nil big.Rat during ValidateRequest. Standard net/http servers recover the panic per connection, while other hosts or application goroutines may terminate the process. This issue is fixed in version 0.148.0.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

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

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 | All versions | 0.148.0 |
| `github.com/getkin/kin-openapi` | Go | All versions | 0.148.0 |

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

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

## Is CVE-2026-100352 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100352 is a high-severity denial of service 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-100352 exists.

Affected packages and fixed versions:
- github.com/getkin/kin-openapi (Go): affected all versions; fixed in 0.148.0
- github.com/getkin/kin-openapi (Go): affected all versions; fixed in 0.148.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-100352/ (Markdown: https://insights.sbomify.com/CVE-2026-100352/index.md)
```

## Sources

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

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