CVE-2026-130587 in OpenFunction
Summary
by MITRE • 11/17/2026
OpenFunction through 1.2.0 contains a privilege escalation vulnerability that allows namespace tenants to create privileged host-access pods by supplying unrestricted PodSpec templates in Function and Serving resources. Attackers with only Function or Serving create permissions can set privileged, hostNetwork, hostPID, or hostPath fields to mount the worker node's root filesystem and escalate to node access.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 11/17/2026
OpenFunction versions up through 1.2.0 contain a critical privilege escalation vulnerability rooted in insufficient input validation within its Function and Serving resource definitions. This flaw allows users with permissions to create or modify these specific resources to bypass standard namespace-level isolation controls. The core technical issue lies in the lack of enforcement on PodSpec fields when generating underlying Kubernetes pods for serverless functions. Specifically, the system fails to restrict access to sensitive host-related configuration parameters such as privileged mode, host network sharing, host process ID visibility, and host path volume mounts. This architectural oversight means that any tenant with write access to Function or Serving objects can effectively dictate how their workloads interact with the underlying node infrastructure, disregarding typical security boundaries designed to contain containerized applications within isolated environments.
The operational impact of this vulnerability is severe, as it enables a direct escalation from namespace-level user privileges to full control over the worker nodes hosting the OpenFunction cluster. By supplying unrestricted PodSpec templates in their Function or Serving resources, an attacker can configure pods with privileged flags that grant access to all host devices and capabilities equivalent to root on the node. Furthermore, enabling hostNetwork allows the pod to share the node's network stack, facilitating network-based attacks such as sniffing traffic from other workloads running on the same node. The ability to set hostPID permits inspection of processes across the entire node, while hostPath mounts allow direct read-write access to arbitrary directories on the worker filesystem, including sensitive configuration files and credentials stored outside container boundaries. This effectively breaks the multi-tenant security model, allowing a compromised or malicious tenant to pivot laterally across the cluster by accessing other tenants' data or disrupting shared infrastructure services.
From a classification perspective, this vulnerability aligns with CWE-269 Improper Privilege Management, as it involves an actor obtaining elevated privileges without proper authorization checks on specific resource attributes. It also maps closely to CWE-732 Incorrect Permission Assignment for Critical Resource, reflecting the failure to restrict access to sensitive host resources via container configuration fields. In terms of adversary tactics, this exploit leverages techniques associated with MITRE ATT&CK T1608 Privileged Account Creation and T1496 Host-Based Credential Access if used to harvest secrets from mounted paths, or more broadly falls under lateral movement strategies that rely on compromising node-level access rather than just pod-level isolation. The vulnerability highlights a common risk in serverless Kubernetes platforms where abstraction layers may inadvertently expose low-level container runtime configurations to higher-level application developers who should not have such authority.
Mitigation for this issue requires immediate remediation by upgrading OpenFunction to version 1.2.1 or later, where the underlying admission controllers and validation logic have been hardened to reject unauthorized PodSpec fields in Function and Serving resources. In environments where an upgrade is not immediately feasible, administrators should implement strict NetworkPolicies and LimitRanges at the namespace level to restrict pod creation capabilities further. Additionally, deploying a Kubernetes Admission Controller such as OPA Gatekeeper or Kyverno can enforce policies that explicitly block the setting of privileged, hostNetwork, hostPID, and hostPath fields in any PodSpec generated by OpenFunction resources. It is also critical to review RBAC permissions within the cluster, ensuring that only trusted service accounts with explicit need for node-level access are granted rights to create or modify Function and Serving objects. Regular auditing of pod specifications deployed through these interfaces can help detect attempts to exploit this vulnerability before they result in full node compromise.