Skip to main content
VulnerabilityPublished

CVE-2026-97054: Yunikorn k8shim · For HTTP/1 servers, when MaxBytesReader's limit is exceeded, "Connection: close"

Affects yunikorn-k8shimSource GCVE Database

0
Compare
Authoritative record:CVE-2026-97054· High

Not known to be exploited : upgrade to 1.8.0-r5 soon.

Data as of 14 Nov 2026, 03:50 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 1.8.0-r5, 1.9.0-r2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade yunikorn-k8shim to 1.8.0-r5; yunikorn-k8shim to 1.9.0-r2.

Affected software

ProductAffectedFixed in
CleanStartyunikorn-k8shimpkg:apk/cleanstart/yunikorn-k8shimOther threatsAffected
  • <1.8.0-r5
Fixed in
  • 1.8.0-r5
CleanStartyunikorn-k8shimpkg:apk/cleanstart/yunikorn-k8shimOther threatsAffected
  • <1.9.0-r2
Fixed in
  • 1.9.0-r2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in versions 1.8.0-r5 and 1.9.0-r2 of yunikorn-k8shim. Users should upgrade to these versions or later to remediate the vulnerability.

Description

A security vulnerability in the yunikorn-k8shim package affects HTTP/1 servers where exceeding MaxBytesReader's limit causes the "Connection: close" header to be set automatically without synchronization. This can race with another header set explicitly in the server handler, potentially leading to inconsistent header states.

References

Community reviews

Loading reviews…