Skip to content
Fencer Intel
high 7.5

CVE-2026-93450 json

go-openapi/swag jsonutils before 0.27.1 Uncontrolled Recursion in Ordered JSON Marshal and Unmarshal

published 3mo ago modified last mo. also EUVD-2026-82602 , GHSA-xh24-9qpg-8w28

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository go-openapi/swag. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 66%
public exploits
0
none known

Summary

go-openapi/swag jsonutils before 0.27.1 contains a stack overflow vulnerability in ordered JSON parsing and serialization due to unbounded recursion with no depth limit. Remote unauthenticated attackers can submit deeply nested JSON documents to services accepting OpenAPI specifications, causing fatal stack overflow that terminates the process and all in-flight requests.

Patch / fix

  • go-openapi swag 0.27.1
  • grafana13.2 hummingbird 1 13.2.3-0.3.hum1
  • cosign hummingbird 1 3.1.3-0.2.hum1
  • spire1.14 hummingbird 1 1.14.7-0.5.hum1
  • spire1.14-agent hummingbird 1 1.14.7-0.5.hum1
  • spire1.14-server hummingbird 1 1.14.7-0.5.hum1
  • spire1.14-oidc-discovery-provider hummingbird 1 1.14.7-0.5.hum1
  • prometheus3.13 hummingbird 1 3.13.3-0.2.hum1
  • grafana12.4 hummingbird 1 12.4.12-0.3.hum1

red hat advisories RHSA-2026:85266RHSA-2026:72488RHSA-2026:72489RHSA-2026:72750RHSA-2026:74871RHSA-2026:72570

  • kubevirt Azure Linux 3.0 1.8.4-4

azure linux advisories AZL-103377

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2026-93450 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-93450 updated cvss 7.5

github.com/go-openapi/swag: go-openapi/swag: Denial of Service via uncontrolled JSON recursion

  • Red Hat Hardened Images prometheus3.5 3.5.5-0.8.hum1, opentofu1.11 1.11.14-0.1.hum1
    affected: no fix planned “Will not fix”
  • Red Hat Hardened Images helm4 4.3.0-0.2.hum1, cosign 3.1.3-0.2.hum1, helm3 3.22.0-0.2.hum1, trivy 0.74.0-0.4.hum1, loki3.7 3.7.8-0.3.hum1, loki3.6 3.6.17-0.3.hum1, +24 more
    fixed: vendor fix RHSA-2026:72488
  • Red Hat Hardened Images go-fdo-server 1.0.1-0.5.hum1, kubernetes1.35 1.35.8-3.hum1, kubernetes1.36 1.36.4-2.hum1, opentofu1.12 1.12.6-0.3.hum1, kube-state-metrics 2.20.0-0.2.hum1
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
partial
Assessed
last mo.

Exploit prediction

1.10% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • github.com https://github.com/go-openapi/swag/security/advisories/GHSA-xh24-9qpg-8w28 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 8.7 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA 4.0 8.7 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected products

  • go-openapi swag

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of go-openapi/swag published their own advisory on GitHub. Reviewed sources take precedence over it.