Skip to content
Web

CVE-2026-77354

8.7
High
EPSS 0.30%Patch availableAug 22, 2026

Unauthenticated DoS via deepObject query index causing multi-GB allocation.

common questions

Is CVE-2026-77354 being exploited?

Not confirmed. CVE-2026-77354 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.30% probability of exploitation in the next 30 days.

How severe is CVE-2026-77354?

CVE-2026-77354 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-77354?

Yes. A fix has been recorded for CVE-2026-77354. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-77354 affect?

CVE-2026-77354 affects kin-openapi 0.124.0–0.141.0, Go services using openapi3filter/req_resp_decoder.go, APIs accepting deepObject-style query arrays. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-77354?

Upgrade kin-openapi to >=0.142.0; add input validation and enforce rate/size limits.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
kin-openapi 0.124.0–0.141.0Go services using openapi3filter/req_resp_decoder.goAPIs accepting deepObject-style query arrays
impact

Unauthenticated attacker can craft deepObject query indexes to force multi-GB heap allocations, causing OOM kills or service restarts (denial of service).

action required

Immediate action required

affected versions
getkin kin-openapi
  • affected>= 0.124.0 and < 0.142.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free