LiveActive security incident?Get immediate response
CVE Record

CVE-2021-36779: Host operations allowed in privileged Longhorn managed pods

A Missing Authentication for Critical Function vulnerability in SUSE Longhorn allows any workload in the cluster to execute any binary present in the image on the host without authentication. This issue affects: SUSE Longhorn longhorn versions prior to 1.1.3; longhorn versions prior to 1.2.3.

CriticalCVSS 9.6Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2021-36779 is a critical Longhorn flaw where any workload already inside a Kubernetes cluster could trigger privileged Longhorn-managed pods to run host binaries without authentication. In practical terms, a compromised or untrusted workload could threaten the underlying node, not just its own container.

Executive priority

Treat this as urgent for any affected Longhorn cluster. The business risk is potential host-level compromise from inside the cluster, which can expand a container incident into node, data, or service compromise.

Technical view

The issue is CWE-306, missing authentication for a critical function. SUSE states Longhorn versions before 1.1.3 and before 1.2.3 are affected. The CVSS 3.1 score is 9.6 with adjacent attack vector, no privileges required, no user interaction, changed scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to Kubernetes environments running affected SUSE Longhorn versions prior to 1.1.3 or 1.2.3. Risk is highest where clusters run untrusted, multi-tenant, internet-facing, or compromised workloads that can interact with Longhorn-managed components.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation evidence. The vulnerability is still severe because the described access path starts from any workload in the cluster and can affect the host through privileged Longhorn-managed pods.

Researcher notes

The bundle supports critical severity, affected version ranges, CWE-306, and the core impact. It does not provide exploit telemetry, detailed attack mechanics, or independent proof of exploitation, so validation should focus on version inventory and Longhorn deployment context.

Mitigation direction

  • Upgrade Longhorn to version 1.1.3, 1.2.3, or later as appropriate.
  • Check SUSE and Longhorn advisory guidance before selecting the target version.
  • Restrict untrusted workloads from affected clusters until remediation is complete.
  • Review cluster segmentation and policies around access to Longhorn-managed components.
  • Prioritize remediation on multi-tenant or externally exposed Kubernetes clusters.

Validation and detection

  • Inventory Kubernetes clusters using SUSE Longhorn.
  • Confirm each Longhorn deployment version is 1.1.3, 1.2.3, or later.
  • Identify clusters running untrusted or externally reachable workloads.
  • Review whether Longhorn-managed pods run privileged on affected nodes.
  • Check vendor advisories for any branch-specific remediation notes.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-306: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-36779 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.6CVSS 3.1CriticalCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H2.86Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.6Critical
CVSS 3.1 vector shape for CVE-2021-36779Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SUSELonghornlonghornListed
SUSELonghornlonghornListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-306 · source CWE mapping

Missing Authentication for Critical Function

Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.