Unauthenticated service crash via nil schema dereference
Published Aug 18, 2026 · Updated Aug 18, 2026
NULL pointer dereference in getkin kin-openapi before 0.144.0 allows remote attackers to interrupt service via a crafted HTTP request. In openapi3filter/req_resp_decoder.go, defaultContentParameterDecoder reads mt.Schema.Value for an application/json content parameter without checking whether mt.Schema is nil, and the library's document validation accepts that schema-less media type under OpenAPI 3.0.x and 3.1.x. Exposure requires request validation with openapi3filter on at least one unauthenticated operation whose served specification includes a content parameter with no schema; common net/http use aborts the request and logs a panic, while integrations without recovery can crash the process.
Summary
What happened
NULL pointer dereference in getkin kin-openapi before 0.144.0 allows remote attackers to interrupt service via a crafted HTTP request. In openapi3filter/req_resp_decoder.go, defaultContentParameterDecoder reads mt.Schema.Value for an application/json content parameter without checking whether mt.Schema is nil, and the library's document validation accepts that schema-less media type under OpenAPI 3.0.x and 3.1.x. Exposure requires request validation with openapi3filter on at least one unauthenticated operation whose served specification includes a content parameter with no schema; common net/http use aborts the request and logs a panic, while integrations without recovery can crash the process.
The record
- CVE
- CVE-2026-73502
- Published
- Aug 18, 2026
- Updated
- Aug 18, 2026
- Vendor
- getkin
- Product
- kin-openapi
- Classifications
- CWE-476, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.2.0, < 0.144.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- GHSA-jpcw-4wr7-c3vq proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo