CVE-2026-76905
kin-openapi openai3filter: nil-pointer panic in ConvertErrors on malformed multipart/form-data body enables unauthenticated DoS
kin-openapi is a Go project for handling OpenAPI files. From 0.10.0 until 0.141.0, openapi3filter.convertParseError in openapi3filter/validation_error_encoder.go dereferences e.Parameter.In without checking whether e.Parameter is nil. A malformed non-string scalar field in a multipart/form-data request body produces a nested ParseError with a nil RequestError.Parameter, and applications that render the validation error through openapi3filter.ConvertErrors or ValidationErrorEncoder panic. An unauthenticated client can repeatedly send such requests to deny service when the application lacks a recovery boundary. JSON request bodies and applications that do not use these error-rendering helpers are not affected. This issue is fixed in version 0.141.0.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Exploit likelihood
What each source reports
CVE List Score used
7.5
kin-openapi openai3filter: nil-pointer panic in ConvertErrors on malformed multipart/form-data body enables unauthenticated DoS
kin-openapi is a Go project for handling OpenAPI files. From 0.10.0 until 0.141.0, openapi3filter.convertParseError in openapi3filter/validation_error_encoder.go dereferences e.Parameter.In without checking whether e.Parameter is nil. A malformed non-string scalar field in a multipart/form-data request body produces a nested ParseError with a nil RequestError.Parameter, and applications that render the validation error through openapi3filter.ConvertErrors or ValidationErrorEncoder panic. An unauthenticated client can repeatedly send such requests to deny service when the application lacks a recovery boundary. JSON request bodies and applications that do not use these error-rendering helpers are not affected. This issue is fixed in version 0.141.0.
- Record
CVE-2026-76905- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-476
- Updated
- 2026-11-02
EUVDEUVD-2026-64150
7.5
kin-openapi is a Go project for handling OpenAPI files. From 0.10.0 until 0.141.0, openapi3filter.convertParseError in openapi3filter/validation_error_encoder.go dereferences e.Parameter.In without checking whether e.Parameter is nil. A malformed non-string scalar field in a multipart/form-data request body produces a nested ParseError with a nil RequestError.Parameter, and applications that render the validation error through openapi3filter.ConvertErrors or ValidationErrorEncoder panic. An unauthenticated client can repeatedly send such requests to deny service when the application lacks a recovery boundary. JSON request bodies and applications that do not use these error-rendering helpers are not affected. This issue is fixed in version 0.141.0.
- Record
EUVD-2026-64150- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-mmfr-pmjx-hw9w
7.5
kin-openapi openai3filter: nil-pointer panic in ConvertErrors on malformed multipart/form-data body enables unauthenticated DoS
Summary
A nil-pointer dereference in openapi3filter.ConvertErrors lets any unauthenticated client crash a server with a single HTTP request. When an application validates a multipart/form-data request body and renders the resulting validation error through the library-provided ValidationErrorEncoder / ConvertErrors helpers, a malformed scalar form field (e.g. a non-numeric value for an integer property) produces an error shape that convertParseError dereferences without a nil check. The handler goroutine panics, causing a denial of service. application/json request bodies are not affected — the bug is specific to multipart/form-data.
Details
The panic is in convertParseError, at openapi3filter/validation_error_encoder.go:119-120 (still present on master at the time of writing):
} else if innerErr.RootCause() != nil {
if rootErr, ok := innerErr.Cause.(*ParseError); ok &&
rootErr.Kind == KindInvalidFormat && e.Parameter.In == "query" { // ❌ e.Parameter may be nil → panic
The comparison e.Parameter.In == "query" assumes e.Parameter is non-nil. It is reached whenever both of the following hold:
e.Parameter == nil. A*RequestErrorcarries eitherParameter(parameter errors) orRequestBody(body errors), never both.ValidateRequestBodybuilds body errors with onlyRequestBodyset, leavingParameternil — seevalidate_request.go:326-332.innerErr.Causeis itself a*ParseError(aParseErrornested inside aParseError), so the type assertion on line 119 succeeds and execution reaches thee.Parameter.Indereference on line 120.
The only default code path that satisfies both conditions is the multipart body decoder, which wraps a failed part's *ParseError inside another *ParseError at req_resp_decoder.go:1549 and :1558:
if v, ok := err.(*ParseError); ok {
return nil, &ParseError{path: []any{name}, Cause: v} // v is a *ParseError → nested
}
Why other paths do not reach the dereference:
| Body content type | Failure mode | RequestError.Err shape | .Cause is *ParseError? | e.Parameter | Panics? |
|---|---|---|---|---|---|
| multipart/form-data | scalar part fails primitive parse (age=notanumber) | *ParseError wrapping a *ParseError | yes | nil | YES |
| application/json | malformed JSON syntax | *ParseError whose .Cause is an encoding/json error | no (assertion fails → safe fallback branch) | nil | no |
| application/json | wrong type / schema violation | *openapi3.SchemaError (routed to convertSchemaError, never reaches convertParseError) | n/a | nil | no |
| styled query / path params | invalid format | *ParseError wrapping a *ParseError | yes | set (non-nil) | no (guard/assignment succeeds) |
Note that the sibling "path" branch two lines above (line 108) already guards correctly with e.Parameter != nil; the "query" branch simply omits the same guard.
Recommended fix. Add the missing nil guard to the condition:
if rootErr, ok := innerErr.Cause.(*ParseError); ok &&
- rootErr.Kind == KindInvalidFormat && e.Parameter.In == "query" {
+ rootErr.Kind == KindInvalidFormat && e.Parameter != nil && e.Parameter.In == "query" {
When e.Parameter == nil the inner if is skipped and control falls through to the existing return &ValidationError{Status: http.StatusBadRequest, Title: innerErr.Reason} at [line…
- Record
GHSA-mmfr-pmjx-hw9w- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-476
- Updated
- 2026-11-02
NVD
7.5
kin-openapi is a Go project for handling OpenAPI files. From 0.10.0 until 0.141.0, openapi3filter.convertParseError in openapi3filter/validation_error_encoder.go dereferences e.Parameter.In without checking whether e.Parameter is nil. A malformed non-string scalar field in a multipart/form-data request body produces a nested ParseError with a nil RequestError.Parameter, and applications that render the validation error through openapi3filter.ConvertErrors or ValidationErrorEncoder panic. An unauthenticated client can repeatedly send such requests to deny service when the application lacks a recovery boundary. JSON request bodies and applications that do not use these error-rendering helpers are not affected. This issue is fixed in version 0.141.0.
- Record
CVE-2026-76905- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-476
- Updated
- 2026-11-02
OSV
7.5
kin-openapi openai3filter: nil-pointer panic in ConvertErrors on malformed multipart/form-data body enables unauthenticated DoS
kin-openapi is a Go project for handling OpenAPI files. From 0.10.0 until 0.141.0, openapi3filter.convertParseError in openapi3filter/validation_error_encoder.go dereferences e.Parameter.In without checking whether e.Parameter is nil. A malformed non-string scalar field in a multipart/form-data request body produces a nested ParseError with a nil RequestError.Parameter, and applications that render the validation error through openapi3filter.ConvertErrors or ValidationErrorEncoder panic. An unauthenticated client can repeatedly send such requests to deny service when the application lacks a recovery boundary. JSON request bodies and applications that do not use these error-rendering helpers are not affected. This issue is fixed in version 0.141.0.
- Record
CVE-2026-76905- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-476
- Updated
- 2026-11-02
OSVDEBIAN-CVE-2026-76905
7.5
kin-openapi is a Go project for handling OpenAPI files. From 0.10.0 until 0.141.0, openapi3filter.convertParseError in openapi3filter/validation_error_encoder.go dereferences e.Parameter.In without checking whether e.Parameter is nil. A malformed non-string scalar field in a multipart/form-data request body produces a nested ParseError with a nil RequestError.Parameter, and applications that render the validation error through openapi3filter.ConvertErrors or ValidationErrorEncoder panic. An unauthenticated client can repeatedly send such requests to deny service when the application lacks a recovery boundary. JSON request bodies and applications that do not use these error-rendering helpers are not affected. This issue is fixed in version 0.141.0.
- Record
DEBIAN-CVE-2026-76905- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
Show 6 moreShow less
OSVGHSA-mmfr-pmjx-hw9w
7.5
kin-openapi openai3filter: nil-pointer panic in ConvertErrors on malformed multipart/form-data body enables unauthenticated DoS
Summary
A nil-pointer dereference in openapi3filter.ConvertErrors lets any unauthenticated client crash a server with a single HTTP request. When an application validates a multipart/form-data request body and renders the resulting validation error through the library-provided ValidationErrorEncoder / ConvertErrors helpers, a malformed scalar form field (e.g. a non-numeric value for an integer property) produces an error shape that convertParseError dereferences without a nil check. The handler goroutine panics, causing a denial of service. application/json request bodies are not affected — the bug is specific to multipart/form-data.
Details
The panic is in convertParseError, at openapi3filter/validation_error_encoder.go:119-120 (still present on master at the time of writing):
} else if innerErr.RootCause() != nil {
if rootErr, ok := innerErr.Cause.(*ParseError); ok &&
rootErr.Kind == KindInvalidFormat && e.Parameter.In == "query" { // ❌ e.Parameter may be nil → panic
The comparison e.Parameter.In == "query" assumes e.Parameter is non-nil. It is reached whenever both of the following hold:
e.Parameter == nil. A*RequestErrorcarries eitherParameter(parameter errors) orRequestBody(body errors), never both.ValidateRequestBodybuilds body errors with onlyRequestBodyset, leavingParameternil — seevalidate_request.go:326-332.innerErr.Causeis itself a*ParseError(aParseErrornested inside aParseError), so the type assertion on line 119 succeeds and execution reaches thee.Parameter.Indereference on line 120.
The only default code path that satisfies both conditions is the multipart body decoder, which wraps a failed part's *ParseError inside another *ParseError at req_resp_decoder.go:1549 and :1558:
if v, ok := err.(*ParseError); ok {
return nil, &ParseError{path: []any{name}, Cause: v} // v is a *ParseError → nested
}
Why other paths do not reach the dereference:
| Body content type | Failure mode | RequestError.Err shape | .Cause is *ParseError? | e.Parameter | Panics? |
|---|---|---|---|---|---|
| multipart/form-data | scalar part fails primitive parse (age=notanumber) | *ParseError wrapping a *ParseError | yes | nil | YES |
| application/json | malformed JSON syntax | *ParseError whose .Cause is an encoding/json error | no (assertion fails → safe fallback branch) | nil | no |
| application/json | wrong type / schema violation | *openapi3.SchemaError (routed to convertSchemaError, never reaches convertParseError) | n/a | nil | no |
| styled query / path params | invalid format | *ParseError wrapping a *ParseError | yes | set (non-nil) | no (guard/assignment succeeds) |
Note that the sibling "path" branch two lines above (line 108) already guards correctly with e.Parameter != nil; the "query" branch simply omits the same guard.
Recommended fix. Add the missing nil guard to the condition:
if rootErr, ok := innerErr.Cause.(*ParseError); ok &&
- rootErr.Kind == KindInvalidFormat && e.Parameter.In == "query" {
+ rootErr.Kind == KindInvalidFormat && e.Parameter != nil && e.Parameter.In == "query" {
When e.Parameter == nil the inner if is skipped and control falls through to the existing return &ValidationError{Status: http.StatusBadRequest, Title: innerErr.Reason} at [line…
- Record
GHSA-mmfr-pmjx-hw9w- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-476
- Updated
- 2026-11-02
OSVUBUNTU-CVE-2026-76905
7.5
kin-openapi is a Go project for handling OpenAPI files. From 0.10.0 until 0.141.0, openapi3filter.convertParseError in openapi3filter/validation_error_encoder.go dereferences e.Parameter.In without checking whether e.Parameter is nil. A malformed non-string scalar field in a multipart/form-data request body produces a nested ParseError with a nil RequestError.Parameter, and applications that render the validation error through openapi3filter.ConvertErrors or ValidationErrorEncoder panic. An unauthenticated client can repeatedly send such requests to deny service when the application lacks a recovery boundary. JSON request bodies and applications that do not use these error-rendering helpers are not affected. This issue is fixed in version 0.141.0.
- Record
UBUNTU-CVE-2026-76905- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVGO-2026-6274 No score
kin-openapi openai3filter: nil-pointer panic in ConvertErrors on malformed multipart/form-data body enables unauthenticated DoS in github.com/getkin/kin-openapi
kin-openapi openai3filter: nil-pointer panic in ConvertErrors on malformed multipart/form-data body enables unauthenticated DoS in github.com/getkin/kin-openapi
- Record
GO-2026-6274- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:21761-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
-
Update to version 0.0.20260827T195228 2026-08-27T19:52:28Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-5026 CVE-2026-39821
- GO-2026-6225
- GO-2026-6250 CVE-2026-63328 GHSA-8rc5-4fr6-64pw
- GO-2026-6253 CVE-2026-17106 GHSA-hfg8-hc9c-6c3h
- GO-2026-6254 CVE-2026-53941 GHSA-vjhx-2cqw-3q6q
- GO-2026-6255 CVE-2026-61711 GHSA-7236-3392-c5c6
- GO-2026-6256 CVE-2026-61712 GHSA-72x6-4j93-7w86
- GO-2026-6258 CVE-2026-45404 GHSA-42cj-99w8-cp2p
- GO-2026-6259 CVE-2026-32637 GHSA-j2g6-362q-6qc6
- GO-2026-6260 CVE-2026-55149 GHSA-qqff-5854-px68
- GO-2026-6261 CVE-2026-54061 GHSA-rrwh-6jrq-wp5v
- GO-2026-6262 GHSA-22w5-2fxg-vrwx
- GO-2026-6263 CVE-2026-54168 GHSA-6f2p-296r-cc28
- GO-2026-6264 CVE-2026-54245 GHSA-7q96-f8xw-jv5j
- GO-2026-6265 GHSA-8fxq-53rx-ph5f
- GO-2026-6266 CVE-2026-54167 GHSA-f5f4-3hh4-f54m
- GO-2026-6267 GHSA-h58c-xccx-75m3
- GO-2026-6268 GHSA-q9c5-pp7m-fm2g
- GO-2026-6269 GHSA-rxhg-vcww-2mpw
- GO-2026-6270 CVE-2026-54162 GHSA-x3g7-qrwc-f6c5
- GO-2026-6271 CVE-2026-67448 GHSA-8r62-w5wh-fc5m
- GO-2026-6272 CVE-2026-67447 GHSA-r553-m4fv-5v97
- GO-2026-6273 CVE-2026-64679 GHSA-26w5-6g95-gj28
- GO-2026-6274 CVE-2026-76905 GHSA-mmfr-pmjx-hw9w
- GO-2026-6275 CVE-2026-77354 GHSA-xhj3-7xw9-vr34
- GO-2026-6277 GHSA-4ph6-mjv7-3fq6
- GO-2026-6278 GHSA-w67g-5rqw-f597
- GO-2026-6279 CVE-2026-6046 GHSA-3vmp-whvv-5v9v
- GO-2026-6280 CVE-2026-7387 GHSA-6hxm-w4hv-vgvw
- GO-2026-6281 CVE-2026-6961 GHSA-8qq9-cqj8-82w4
- GO-2026-6282 CVE-2026-7184 GHSA-9p44-r552-4wp9
- GO-2026-6283 CVE-2026-6689 GHSA-c28q-m4gf-vg4q
- GO-2026-6284 CVE-2026-55477 GHSA-jm48-m3rr-9hgg
- GO-2026-6285 CVE-2026-6739 GHSA-m2w9-h2mm-79qr
- GO-2026-6286 CVE-2026-3433 GHSA-rp4v-qc77-phm4
- GO-2026-6287 GHSA-vx2m-jpxr-xv7w
- GO-2026-6288 CVE-2026-11624 GHSA-76g7-m3xw-x9gr
- GO-2026-6289 GHSA-w8j7-39hp-8x59
- GO-2026-6290 CVE-2026-55581 GHSA-3x77-wg38-92r3
- GO-2026-6291 CVE-2026-55582 GHSA-74hp-mggr-hv58
- GO-2026-6292 CVE-2026-55580 GHSA-f5pj-2738-996m
- GO-2026-6293 CVE-2026-55677 GHSA-vfp3-v2gw-7wfq
- GO-2026-6294 CVE-2026-55092 GHSA-mcj4-mphf-j9ff
- GO-2026-6295 CVE-2026-55637 GHSA-cmwv-wf9p-p8wx
- GO-2026-6296 CVE-2026-54523 GHSA-79gf-7frw-68m9
- GO-2026-6297 CVE-2026-50879 GHSA-g743-m6x3-v6wm
- GO-2026-6298 CVE-2026-54563 GHSA-w5fv-7x5q-g8qp
- GO-2026-6299 CVE-2026-50884 GHSA-5442-mh7f-72px
- GO-2026-6300 CVE-2026-50891 GHSA-rcqf-cpv9-g5jf
- GO-2026-6301 CVE-2026-42350 GHSA-g7gw-m874-7rmf
-
Update to version 0.0.20260819T170606 2026-08-19T17:06:06Z.
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-4720 GHSA-v3mg-9v85-fcm7
- GO-2026-4942 CVE-2026-35172 GHSA-f2g3-hh2r-cwgc
- GO-2026-4950
- GO-2026-6093 GHSA-464c-974j-9xm6
- GO-2026-6094 GHSA-gcjh-h69q-9w9g
- GO-2026-6095 GHSA-r277-6w6q-xmqw
- GO-2026-6097 CVE-2026-55495 GHSA-49h3-cwhj-4737
- GO-2026-6098 CVE-2026-55496 GHSA-8r7f-r8hj-r3rv
- GO-2026-6099 CVE-2026-57497 GHSA-g35j-m5xg-vh3q
- GO-2026-6100 CVE-2026-55497 GHSA-g9j2-8w95-3vwv
- GO-2026-6101 CVE-2026-55502 GHSA-hq88-5x99-x3gf
- GO-2026-6102 CVE-2026-55499 GHSA-w8x7-h2px-xmq8
- GO-2026-6103 CVE-2026-73564 GHSA-26gq-p25f-99cp
- GO-2026-6104 CVE-2026-62323 GHSA-c3jm-gv5r-9wcp
- GO-2026-6105 GHSA-c534-2w9c-x7fm
- GO-2026-6106 GHSA-v6w6-358x-2433
- GO-2026-6107 CVE-2026-73500 GHSA-6vch-q96h-7gc3
- GO-2026-6108 CVE-2026-73505 GHSA-6xj8-qv9j-xcjq
- GO-2026-6109 GHSA-86cx-wwf4-phq4
- GO-2026-6110 CVE-2026-73509 GHSA-95cv-r8x4-vh75
- GO-2026-6111 CVE-2026-73506 GHSA-fwjx-9p69-h25h
- GO-2026-6112 CVE-2026-73502 GHSA-jpcw-4wr7-c3vq
- GO-2026-6113 GHSA-p6ph-3jx2-3337
- GO-2026-6114 CVE-2026-73499 GHSA-xg4h-6gfc-h4m8
- GO-2026-6115 CVE-2026-56867
- GO-2026-6117 GHSA-hp74-gm6m-2qm5
- GO-2026-6118 CVE-2026-47427 GHSA-w4q6-qw23-4rg7
- GO-2026-6119 CVE-2026-43983…
- Record
openSUSE-SU-2026:21761-1- Updated
- 2026-11-02
OSVROOT-APP-GOBINARY-CVE-2026-76905 No score
CVE-2026-76905 in github.com/getkin/kin-openapi - Patched by Root
Root has patched CVE-2026-76905 in the github.com/getkin/kin-openapi package for Root:Go. Multiple fixed versions available.
- Record
ROOT-APP-GOBINARY-CVE-2026-76905- Updated
- 2026-11-06
OSVSUSE-SU-2026:23625-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
-
Update to version 0.0.20260827T195228 2026-08-27T19:52:28Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-5026 CVE-2026-39821
- GO-2026-6225
- GO-2026-6250 CVE-2026-63328 GHSA-8rc5-4fr6-64pw
- GO-2026-6253 CVE-2026-17106 GHSA-hfg8-hc9c-6c3h
- GO-2026-6254 CVE-2026-53941 GHSA-vjhx-2cqw-3q6q
- GO-2026-6255 CVE-2026-61711 GHSA-7236-3392-c5c6
- GO-2026-6256 CVE-2026-61712 GHSA-72x6-4j93-7w86
- GO-2026-6258 CVE-2026-45404 GHSA-42cj-99w8-cp2p
- GO-2026-6259 CVE-2026-32637 GHSA-j2g6-362q-6qc6
- GO-2026-6260 CVE-2026-55149 GHSA-qqff-5854-px68
- GO-2026-6261 CVE-2026-54061 GHSA-rrwh-6jrq-wp5v
- GO-2026-6262 GHSA-22w5-2fxg-vrwx
- GO-2026-6263 CVE-2026-54168 GHSA-6f2p-296r-cc28
- GO-2026-6264 CVE-2026-54245 GHSA-7q96-f8xw-jv5j
- GO-2026-6265 GHSA-8fxq-53rx-ph5f
- GO-2026-6266 CVE-2026-54167 GHSA-f5f4-3hh4-f54m
- GO-2026-6267 GHSA-h58c-xccx-75m3
- GO-2026-6268 GHSA-q9c5-pp7m-fm2g
- GO-2026-6269 GHSA-rxhg-vcww-2mpw
- GO-2026-6270 CVE-2026-54162 GHSA-x3g7-qrwc-f6c5
- GO-2026-6271 CVE-2026-67448 GHSA-8r62-w5wh-fc5m
- GO-2026-6272 CVE-2026-67447 GHSA-r553-m4fv-5v97
- GO-2026-6273 CVE-2026-64679 GHSA-26w5-6g95-gj28
- GO-2026-6274 CVE-2026-76905 GHSA-mmfr-pmjx-hw9w
- GO-2026-6275 CVE-2026-77354 GHSA-xhj3-7xw9-vr34
- GO-2026-6277 GHSA-4ph6-mjv7-3fq6
- GO-2026-6278 GHSA-w67g-5rqw-f597
- GO-2026-6279 CVE-2026-6046 GHSA-3vmp-whvv-5v9v
- GO-2026-6280 CVE-2026-7387 GHSA-6hxm-w4hv-vgvw
- GO-2026-6281 CVE-2026-6961 GHSA-8qq9-cqj8-82w4
- GO-2026-6282 CVE-2026-7184 GHSA-9p44-r552-4wp9
- GO-2026-6283 CVE-2026-6689 GHSA-c28q-m4gf-vg4q
- GO-2026-6284 CVE-2026-55477 GHSA-jm48-m3rr-9hgg
- GO-2026-6285 CVE-2026-6739 GHSA-m2w9-h2mm-79qr
- GO-2026-6286 CVE-2026-3433 GHSA-rp4v-qc77-phm4
- GO-2026-6287 GHSA-vx2m-jpxr-xv7w
- GO-2026-6288 CVE-2026-11624 GHSA-76g7-m3xw-x9gr
- GO-2026-6289 GHSA-w8j7-39hp-8x59
- GO-2026-6290 CVE-2026-55581 GHSA-3x77-wg38-92r3
- GO-2026-6291 CVE-2026-55582 GHSA-74hp-mggr-hv58
- GO-2026-6292 CVE-2026-55580 GHSA-f5pj-2738-996m
- GO-2026-6293 CVE-2026-55677 GHSA-vfp3-v2gw-7wfq
- GO-2026-6294 CVE-2026-55092 GHSA-mcj4-mphf-j9ff
- GO-2026-6295 CVE-2026-55637 GHSA-cmwv-wf9p-p8wx
- GO-2026-6296 CVE-2026-54523 GHSA-79gf-7frw-68m9
- GO-2026-6297 CVE-2026-50879 GHSA-g743-m6x3-v6wm
- GO-2026-6298 CVE-2026-54563 GHSA-w5fv-7x5q-g8qp
- GO-2026-6299 CVE-2026-50884 GHSA-5442-mh7f-72px
- GO-2026-6300 CVE-2026-50891 GHSA-rcqf-cpv9-g5jf
- GO-2026-6301 CVE-2026-42350 GHSA-g7gw-m874-7rmf
-
Update to version 0.0.20260819T170606 2026-08-19T17:06:06Z.
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-4720 GHSA-v3mg-9v85-fcm7
- GO-2026-4942 CVE-2026-35172 GHSA-f2g3-hh2r-cwgc
- GO-2026-4950
- GO-2026-6093 GHSA-464c-974j-9xm6
- GO-2026-6094 GHSA-gcjh-h69q-9w9g
- GO-2026-6095 GHSA-r277-6w6q-xmqw
- GO-2026-6097 CVE-2026-55495 GHSA-49h3-cwhj-4737
- GO-2026-6098 CVE-2026-55496 GHSA-8r7f-r8hj-r3rv
- GO-2026-6099 CVE-2026-57497 GHSA-g35j-m5xg-vh3q
- GO-2026-6100 CVE-2026-55497 GHSA-g9j2-8w95-3vwv
- GO-2026-6101 CVE-2026-55502 GHSA-hq88-5x99-x3gf
- GO-2026-6102 CVE-2026-55499 GHSA-w8x7-h2px-xmq8
- GO-2026-6103 CVE-2026-73564 GHSA-26gq-p25f-99cp
- GO-2026-6104 CVE-2026-62323 GHSA-c3jm-gv5r-9wcp
- GO-2026-6105 GHSA-c534-2w9c-x7fm
- GO-2026-6106 GHSA-v6w6-358x-2433
- GO-2026-6107 CVE-2026-73500 GHSA-6vch-q96h-7gc3
- GO-2026-6108 CVE-2026-73505 GHSA-6xj8-qv9j-xcjq
- GO-2026-6109 GHSA-86cx-wwf4-phq4
- GO-2026-6110 CVE-2026-73509 GHSA-95cv-r8x4-vh75
- GO-2026-6111 CVE-2026-73506 GHSA-fwjx-9p69-h25h
- GO-2026-6112 CVE-2026-73502 GHSA-jpcw-4wr7-c3vq
- GO-2026-6113 GHSA-p6ph-3jx2-3337
- GO-2026-6114 CVE-2026-73499 GHSA-xg4h-6gfc-h4m8
- GO-2026-6115 CVE-2026-56867
- GO-2026-6117 GHSA-hp74-gm6m-2qm5
- GO-2026-6118 CVE-2026-47427 GHSA-w4q6-qw23-4rg7
- GO-2026-6119 CVE-2026-43983…
- Record
SUSE-SU-2026:23625-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/getkin/kin-openapiGo |
0.10.0 up to 0.141.0 | 0.141.0 |
golang-github-getkin-kin-openapiDebian:12 |
All versions, plus listed versions 0.110.0-10.117.0-10.118.0-10.120.0-10.122.0-1 Show 5 moreShow less0.122.0-20.122.0-30.123.0-10.124.0-10.135.0-1 |
None known |
golang-github-getkin-kin-openapiDebian:13 |
All versions, plus listed versions 0.124.0-10.135.0-1 |
None known |
golang-github-getkin-kin-openapiDebian:14 |
All versions, plus listed versions 0.124.0-10.135.0-1 |
None known |
github.com/getkin/kin-openapiRoot:Go |
before v0.140.0-aikido.2 | v0.140.0-aikido.2v0.140.0-aikido.3 |
rootio-github.com/getkin/kin-openapiRoot:Go |
before v0.140.0-root.io.2 | v0.140.0-root.io.2v0.140.0-root.io.3 |
govulncheck-vulndbSUSE:Linux Enterprise Server 16.0 From an advisory covering 181 CVEs |
before 0.0.20260827T195228-160000.1.1 | 0.0.20260827T195228-160000.1.1 |
govulncheck-vulndbSUSE:Linux Enterprise Server for SAP applications 16.0 From an advisory covering 181 CVEs |
before 0.0.20260827T195228-160000.1.1 | 0.0.20260827T195228-160000.1.1 |
golang-github-getkin-kin-openapiUbuntu:22.04:LTS |
All versions, plus listed versions 0.32.0-20.80.0-10.85.0-1 |
None known |
golang-github-getkin-kin-openapiUbuntu:24.04:LTS |
All versions, plus listed versions 0.117.0-10.120.0-10.122.0-30.123.0-1 |
None known |
golang-github-getkin-kin-openapiUbuntu:26.10 |
All versions, plus listed versions 0.124.0-10.135.0-1 |
None known |
golang-github-getkin-kin-openapiUbuntu:26.04:LTS |
All versions, plus listed versions 0.124.0-1 |
None known |
govulncheck-vulndbopenSUSE:Leap 16.0 From an advisory covering 181 CVEs |
before 0.0.20260827T195228-160000.1.1 | 0.0.20260827T195228-160000.1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected | OSV | |
| affected, aliases | OSV | |
| affected, facts | ||
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-76905 is a high vulnerability (CVSS 7.5) in Getkin Kin-openapi, published August 21, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.61%, the 49th percentile. Fixed in github.com/getkin/kin-openapi 0.141.0.
References
github.com/getkin/kin-openapi/security/advisories/GHSA-mmfr-pmjx-hw9w
github.com/getkin/kin-openapi/commit/1d0a337c9b1570fab283be8a04c8af6e43b9a22c
github.com/getkin/kin-openapi/releases/tag/v0.141.0
github.com/advisories/GHSA-mmfr-pmjx-hw9w
github.com/CVEProject/cvelistV5/tree/main/cves/2026/76xxx/CVE-2026-76905.json
nvd.nist.gov/vuln/detail/CVE-2026-76905
Show 186 moreShow less
security-tracker.debian.org/tracker/CVE-2026-76905
github.com/getkin/kin-openapi
suse.com/support/update/announcement/2026/suse-su-202623625-1
suse.com/security/cve/CVE-2026-10722
suse.com/security/cve/CVE-2026-11465
suse.com/security/cve/CVE-2026-11479
suse.com/security/cve/CVE-2026-11481
suse.com/security/cve/CVE-2026-11500
suse.com/security/cve/CVE-2026-11624
suse.com/security/cve/CVE-2026-17106
suse.com/security/cve/CVE-2026-25688
suse.com/security/cve/CVE-2026-25699
suse.com/security/cve/CVE-2026-25700
suse.com/security/cve/CVE-2026-32637
suse.com/security/cve/CVE-2026-33582
suse.com/security/cve/CVE-2026-33818
suse.com/security/cve/CVE-2026-34031
suse.com/security/cve/CVE-2026-34033
suse.com/security/cve/CVE-2026-34177
suse.com/security/cve/CVE-2026-34178
suse.com/security/cve/CVE-2026-34179
suse.com/security/cve/CVE-2026-3433
suse.com/security/cve/CVE-2026-34905
suse.com/security/cve/CVE-2026-34976
suse.com/security/cve/CVE-2026-35172
suse.com/security/cve/CVE-2026-35511
suse.com/security/cve/CVE-2026-39821
suse.com/security/cve/CVE-2026-39832
suse.com/security/cve/CVE-2026-39833
suse.com/security/cve/CVE-2026-39904
suse.com/security/cve/CVE-2026-40173
suse.com/security/cve/CVE-2026-41179
suse.com/security/cve/CVE-2026-41181
suse.com/security/cve/CVE-2026-41327
suse.com/security/cve/CVE-2026-41568
suse.com/security/cve/CVE-2026-42350
suse.com/security/cve/CVE-2026-42508
suse.com/security/cve/CVE-2026-43983
suse.com/security/cve/CVE-2026-45099
suse.com/security/cve/CVE-2026-45404
suse.com/security/cve/CVE-2026-46600
suse.com/security/cve/CVE-2026-46603
suse.com/security/cve/CVE-2026-47427
suse.com/security/cve/CVE-2026-48119
suse.com/security/cve/CVE-2026-48491
suse.com/security/cve/CVE-2026-48786
suse.com/security/cve/CVE-2026-49446
suse.com/security/cve/CVE-2026-49447
suse.com/security/cve/CVE-2026-49980
suse.com/security/cve/CVE-2026-50567
suse.com/security/cve/CVE-2026-50568
suse.com/security/cve/CVE-2026-50569
suse.com/security/cve/CVE-2026-50570
suse.com/security/cve/CVE-2026-50879
suse.com/security/cve/CVE-2026-50884
suse.com/security/cve/CVE-2026-50891
suse.com/security/cve/CVE-2026-52855
suse.com/security/cve/CVE-2026-52856
suse.com/security/cve/CVE-2026-52857
suse.com/security/cve/CVE-2026-53469
suse.com/security/cve/CVE-2026-53470
suse.com/security/cve/CVE-2026-53471
suse.com/security/cve/CVE-2026-53474
suse.com/security/cve/CVE-2026-53475
suse.com/security/cve/CVE-2026-53476
suse.com/security/cve/CVE-2026-53551
suse.com/security/cve/CVE-2026-53622
suse.com/security/cve/CVE-2026-53657
suse.com/security/cve/CVE-2026-53658
suse.com/security/cve/CVE-2026-53941
suse.com/security/cve/CVE-2026-54061
suse.com/security/cve/CVE-2026-54162
suse.com/security/cve/CVE-2026-54167
suse.com/security/cve/CVE-2026-54168
suse.com/security/cve/CVE-2026-54245
suse.com/security/cve/CVE-2026-54332
suse.com/security/cve/CVE-2026-54345
suse.com/security/cve/CVE-2026-54523
suse.com/security/cve/CVE-2026-54526
suse.com/security/cve/CVE-2026-54563
suse.com/security/cve/CVE-2026-54572
suse.com/security/cve/CVE-2026-54593
suse.com/security/cve/CVE-2026-54638
suse.com/security/cve/CVE-2026-54650
suse.com/security/cve/CVE-2026-54680
suse.com/security/cve/CVE-2026-54693
suse.com/security/cve/CVE-2026-54719
suse.com/security/cve/CVE-2026-54725
suse.com/security/cve/CVE-2026-54735
suse.com/security/cve/CVE-2026-54763
suse.com/security/cve/CVE-2026-54764
suse.com/security/cve/CVE-2026-54765
suse.com/security/cve/CVE-2026-54787
suse.com/security/cve/CVE-2026-54908
suse.com/security/cve/CVE-2026-54909
suse.com/security/cve/CVE-2026-54910
suse.com/security/cve/CVE-2026-54917
suse.com/security/cve/CVE-2026-55061
suse.com/security/cve/CVE-2026-55062
suse.com/security/cve/CVE-2026-55092
suse.com/security/cve/CVE-2026-55149
suse.com/security/cve/CVE-2026-55477
suse.com/security/cve/CVE-2026-55495
suse.com/security/cve/CVE-2026-55496
suse.com/security/cve/CVE-2026-55497
suse.com/security/cve/CVE-2026-55499
suse.com/security/cve/CVE-2026-55502
suse.com/security/cve/CVE-2026-55580
suse.com/security/cve/CVE-2026-55581
suse.com/security/cve/CVE-2026-55582
suse.com/security/cve/CVE-2026-55637
suse.com/security/cve/CVE-2026-55677
suse.com/security/cve/CVE-2026-56852
suse.com/security/cve/CVE-2026-56853
suse.com/security/cve/CVE-2026-56858
suse.com/security/cve/CVE-2026-56859
suse.com/security/cve/CVE-2026-56860
suse.com/security/cve/CVE-2026-56862
suse.com/security/cve/CVE-2026-56864
suse.com/security/cve/CVE-2026-56865
suse.com/security/cve/CVE-2026-56867
suse.com/security/cve/CVE-2026-56868
suse.com/security/cve/CVE-2026-56869
suse.com/security/cve/CVE-2026-56870
suse.com/security/cve/CVE-2026-56871
suse.com/security/cve/CVE-2026-56872
suse.com/security/cve/CVE-2026-56873
suse.com/security/cve/CVE-2026-56874
suse.com/security/cve/CVE-2026-57210
suse.com/security/cve/CVE-2026-57497
suse.com/security/cve/CVE-2026-59732
suse.com/security/cve/CVE-2026-59733
suse.com/security/cve/CVE-2026-6046
suse.com/security/cve/CVE-2026-61711
suse.com/security/cve/CVE-2026-61712
suse.com/security/cve/CVE-2026-62323
suse.com/security/cve/CVE-2026-62325
suse.com/security/cve/CVE-2026-63328
suse.com/security/cve/CVE-2026-64679
suse.com/security/cve/CVE-2026-64859
suse.com/security/cve/CVE-2026-64863
suse.com/security/cve/CVE-2026-64865
suse.com/security/cve/CVE-2026-64866
suse.com/security/cve/CVE-2026-64868
suse.com/security/cve/CVE-2026-65600
suse.com/security/cve/CVE-2026-65601
suse.com/security/cve/CVE-2026-65602
suse.com/security/cve/CVE-2026-65834
suse.com/security/cve/CVE-2026-65835
suse.com/security/cve/CVE-2026-66063
suse.com/security/cve/CVE-2026-66064
suse.com/security/cve/CVE-2026-6689
suse.com/security/cve/CVE-2026-67309
suse.com/security/cve/CVE-2026-6739
suse.com/security/cve/CVE-2026-67437
suse.com/security/cve/CVE-2026-67438
suse.com/security/cve/CVE-2026-67439
suse.com/security/cve/CVE-2026-67447
suse.com/security/cve/CVE-2026-67448
suse.com/security/cve/CVE-2026-6961
suse.com/security/cve/CVE-2026-71309
suse.com/security/cve/CVE-2026-71310
suse.com/security/cve/CVE-2026-71311
suse.com/security/cve/CVE-2026-71312
suse.com/security/cve/CVE-2026-71313
suse.com/security/cve/CVE-2026-71324
suse.com/security/cve/CVE-2026-71325
suse.com/security/cve/CVE-2026-71326
suse.com/security/cve/CVE-2026-71327
suse.com/security/cve/CVE-2026-71479
suse.com/security/cve/CVE-2026-71556
suse.com/security/cve/CVE-2026-71557
suse.com/security/cve/CVE-2026-7184
suse.com/security/cve/CVE-2026-73080
suse.com/security/cve/CVE-2026-73499
suse.com/security/cve/CVE-2026-73500
suse.com/security/cve/CVE-2026-73502
suse.com/security/cve/CVE-2026-73505
suse.com/security/cve/CVE-2026-73506
suse.com/security/cve/CVE-2026-73509
suse.com/security/cve/CVE-2026-73564
suse.com/security/cve/CVE-2026-7387
suse.com/security/cve/CVE-2026-76905
suse.com/security/cve/CVE-2026-77354
ubuntu.com/security/CVE-2026-76905
cve.org/CVERecord?id=CVE-2026-76905
Left out here: the rest of 4 source descriptions. The JSON record has them.