CVE-2026-76905: CWE-476: NULL Pointer Dereference in getkin kin-openapi
Description
A NULL pointer dereference vulnerability exists in kin-openapi versions from 0.10.0 up to but not including 0.141.0. The issue occurs in the openapi3filter.convertParseError function, which dereferences a nil Parameter field without checking. This can cause applications that render validation errors using specific helpers to panic when processing malformed multipart/form-data requests. The vulnerability allows unauthenticated clients to cause a denial of service by repeatedly sending such requests. The issue is fixed in version 0.141.0.
CVSS v3.1
Score 7.5high
Affected software
getkin
kin-openapi
pkg:golang/github.com/getkin/kin-openapiRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
kin-openapi, a Go library for handling OpenAPI files, contains a NULL pointer dereference vulnerability (CWE-476) in the openapi3filter.convertParseError function located in openapi3filter/validation_error_encoder.go. Between versions 0.10.0 and 0.141.0, the code dereferences e.Parameter.In without verifying if e.Parameter is nil. When a malformed non-string scalar field is sent in a multipart/form-data request body, a nested ParseError is generated with a nil RequestError.Parameter. Applications that use openapi3filter.ConvertErrors or ValidationErrorEncoder to render validation errors will panic, potentially causing a denial of service. JSON request bodies and applications not using these error-rendering helpers are not affected. The vulnerability is resolved in version 0.141.0.
Potential Impact
An unauthenticated attacker can cause a denial of service by sending specially crafted multipart/form-data requests that trigger a NULL pointer dereference in affected kin-openapi versions. This leads to application panics if the application uses the vulnerable error rendering helpers and lacks recovery boundaries. There is no impact on confidentiality or integrity, only availability.
Mitigation Recommendations
Upgrade kin-openapi to version 0.141.0 or later, where this issue is fixed. Until then, applications should avoid using openapi3filter.ConvertErrors or ValidationErrorEncoder with untrusted multipart/form-data inputs or implement recovery boundaries to handle panics gracefully. Patch status is confirmed fixed in 0.141.0.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-08-19T22:43:14.891Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a88be1eacd9273b49bcc759
Added to database: 08/21/2026, 21:07:42 UTC
Last enriched: 09/10/2026, 15:49:13 UTC
Last updated: 10/05/2026, 18:48:22 UTC
Views: 79
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.