External risk intelligence

OpenFunction Privilege Escalation via Unrestricted PodSpec Templates

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-130587

OpenFunction is a serverless platform running within a Kubernetes cluster. While it provides functionality that may be accessed via a network, the specific vulnerability requires a user to already possess permissions to create Function or Serving resources. This indicates an internal-facing administrative or developer-controlled interface rather than a public-facing service directly exposed to the internet.

Privilege Escalation

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory addresses a privilege escalation vulnerability in OpenFunction, a serverless computing platform. The issue allows authenticated users with specific creation permissions to potentially gain elevated access to the underlying host system by creating specially crafted resources. At a high level, this could allow an attacker to compromise the integrity and confidentiality of the worker node.

  • Unrestricted templates allow privilege escalation.
  • Confirms access to host system resources.
  • Assess relevance and exposure to internal users.

Attack Path

How an attacker could exploit the issue

An attacker with existing permissions to create Function or Serving resources can exploit this vulnerability by providing specially crafted PodSpec templates. This allows them to define Pods with elevated privileges, potentially granting them access to the worker node's root filesystem.

  • Entry: Tenant with create permissions.
  • Trigger: Unrestricted PodSpec templates.
  • Risk: Escalate to node access.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow a tenant with existing permissions to create Function or Serving resources to escalate their privileges. By supplying unrestricted PodSpec templates, an attacker could potentially mount the worker node's root filesystem and gain elevated access to the node.

  • Worker node filesystem could be exposed.
  • Malicious PodSpec templates could be supplied.
  • Node-level access could be achieved.

Operational Fix

Recommended remediation, mitigation, and detection steps

In a typical Kubernetes or cloud-native environment, platform teams and application owners are likely responsible for addressing this privilege escalation vulnerability. The first practical step is to inventory where OpenFunction is deployed, confirm its business criticality and network reachability, and identify the specific team accountable for the affected resources. This allows for a risk-based remediation plan that considers maintenance windows and potential vendor coordination.

  • Platform and application teams own the fix.
  • Verify OpenFunction deployment scope.
  • Plan remediation based on risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is OpenFunction?

OpenFunction is a serverless computing platform designed to run on Kubernetes. It enables developers to build and deploy event-driven functions or serving resources without managing the underlying infrastructure. By automating the creation of Kubernetes workloads, it helps teams streamline cloud-native application development, but it relies on strict configuration boundaries to keep these workloads isolated from the host environment.

What does CVE-2026-130587 mean for security?

This CVE describes a flaw categorized as CWE-862, which is a Missing Authorization vulnerability. It occurs because OpenFunction does not properly restrict how PodSpec templates are defined in Function or Serving resources. A user can exploit this by requesting configurations that grant the container excessive power, such as mounting the host's root filesystem or gaining control over host-level processes, essentially breaking the sandbox.

How can an attacker trigger this vulnerability?

To trigger this, an attacker must already have permissions to create or submit Function or Serving resources within the OpenFunction environment. The vulnerability is activated when they provide a malicious PodSpec template containing elevated fields like hostNetwork, hostPID, or hostPath. Users who lack the authority to create these specific resources cannot trigger the bug, even if they have other limited access to the platform.

Is this vulnerability a risk for my internet-facing systems?

According to Halo Surface Signal, this vulnerability is labeled as Unlikely to be directly reachable from the internet. Because exploiting it requires an attacker to already hold authorized credentials to create Function or Serving resources, the risk is concentrated among internal developers or administrative users. The threat is primarily an internal privilege escalation issue rather than an external gateway vulnerability.

What should I do if I run OpenFunction?

Start by identifying all clusters where OpenFunction is deployed and determining which teams have permissions to create Function or Serving resources. Review your internal access controls to limit who can define these resources. Coordinate with your platform and security teams to assess the business impact and prepare for necessary patches or configuration changes provided by the software maintainers.

References