CVE-2026-97394 getkin CVE debrief

Who should care

Defenders and developers using `github.com/getkin/kin-openapi` should assess exposure and apply patches or workarounds to mitigate the vulnerability. They should verify OpenAPI 3.1 operations for `type: array` without `items` and implement per-request recover handlers to prevent process exit. Prioritization is crucial for systems using OpenAPI 3.1, and compensating controls should be reviewed for exposed systems while remediation is scheduled and verified.

Why it matters

The vulnerability allows an unauthenticated client to crash a request handler, potentially leading to denial-of-service (DoS) attacks. Defenders and developers should assess exposure and apply patches or workarounds to mitigate the vulnerability.

• Crash of request handlers with a single HTTP request
• Potential for denial-of-service (DoS) attacks
• Need for verification of OpenAPI 3.1 operations for `type: array` without `items`
• Priority for applying patches or workarounds to prevent exploitation

Technical summary

The `openapi3filter` package in `github.com/getkin/kin-openapi` is vulnerable to a nil-pointer dereference when handling OpenAPI 3.1 array schemas without `items`. This allows an unauthenticated client to crash a request handler with a single HTTP request. The vulnerability arises from the package's handling of OpenAPI 3.1 array schemas, which permits omitting `items`, leading to a deterministic panic on every request to the affected operation. Defenders and developers should assess exposure and apply patches or workarounds to mitigate the vulnerability, particularly for systems using OpenAPI 3.1.

Defensive priority

Defenders should prioritize assessing exposure and applying patches or workarounds to mitigate the vulnerability, particularly for systems using OpenAPI 3.1.

Recommended defensive actions

• Assess exposure and apply patches or workarounds to mitigate the vulnerability
• Verify OpenAPI 3.1 operations for `type: array` without `items`
• Implement per-request recover handlers to prevent process exit
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is caused by a nil-pointer dereference in `openapi3filter` for OpenAPI 3.1 array schemas missing `items`. The issue is deterministic and can cause a panic on every request to the affected operation.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.