On this page (7 sections)

A critical privilege escalation flaw, tracked as CVE-2026-130587, affects OpenFunction through version 1.2.0. According to the GitHub Advisory and the NVD record, a tenant who can only create Function or Serving resources in their namespace can ask for privileged, host-level pods and use them to reach the underlying worker node.

If you run OpenFunction on a shared or multi-tenant Kubernetes cluster, this matters to you. At the time of writing the advisory lists no patched version, so cluster administrators should plan compensating controls rather than wait for an upgrade.

What happened

The advisory was published on November 17, 2026. It describes a flaw in how OpenFunction handles pod definitions embedded in its custom resources. Function and Serving resources accept a PodSpec template, and the project does not restrict what that template may contain.

As a result, a user who has nothing more than permission to create a Function or Serving object can set fields such as privileged, hostNetwork, hostPID or hostPath. Setting hostPath can mount the worker node's root filesystem into the pod, which is a direct route to node access.

Only one independent publisher covers this so far. The NVD entry repeats the same description as the GitHub Advisory, so treat them as one source, not two confirmations. The GitHub entry is also marked unreviewed.

Technical details: why this is serious

The weakness class is missing authorization (CWE-862). Kubernetes normally protects nodes by controlling who may create privileged pods, through RBAC and admission controls such as Pod Security Admission. OpenFunction's controller creates pods on the tenant's behalf from the template the tenant supplies. If the controller passes that template through unchecked, the tenant effectively borrows the controller's power to create pods, and the usual guardrails on pod contents are bypassed.

The advisory's CVSS v4 metrics show a network attack vector, low attack complexity, no attack requirements, low privileges required and no user interaction. Impact is rated high for confidentiality, integrity and availability on both the vulnerable system and subsequent systems. The low privilege requirement is the key detail: a tenant account that was never meant to touch nodes is enough.

The advisory references code in the v1.2.0 tree, in the Serving types definition and the async serving run logic, as well as issue 532 in the project repository. A VulnCheck advisory is also linked. We have not verified exploitation in practice, and we do not describe exploit steps here.

Who is affected

  • Clusters running OpenFunction 1.2.0 or earlier.
  • Platforms where several teams, customers or CI users share a cluster and are granted create rights on Function or Serving resources in their own namespaces.
  • Internal developer platforms that treat namespace-level access as safe because tenants cannot create privileged pods directly.

A single-tenant cluster where only fully trusted administrators can create these resources has lower practical exposure, though a stolen low-privilege credential would still carry the same risk.

How to check your exposure

These are read-only checks. Run them with a kubeconfig that can list resources cluster-wide. First, list the OpenFunction custom resource definitions to confirm the project is installed:

List OpenFunction CRDs on the cluster (look for functions and servings)Shell
kubectl get crd | grep -i openfunction

Next, find the controller image to learn which version you run. Look for a tag of 1.2.0 or lower:

Show images of workloads in the openfunction namespace (adjust the namespace if yours differs)Shell
kubectl get deployments -n openfunction -o wide

Then see who is allowed to create these resources. This lists the roles and cluster roles that mention them so you can review which subjects are bound to them:

Find RBAC roles that reference OpenFunction resourcesShell
kubectl get clusterroles,roles -A -o yaml | grep -n -i -E 'functions|servings'

Finally, look for pods in tenant namespaces that already use host-level settings. The output lists pod names with a hostNetwork or hostPID value; anything set to true in a tenant namespace deserves investigation:

List pods with hostNetwork and hostPID values across all namespacesShell
kubectl get pods -A -o custom-columns=NS:.metadata.namespace,NAME:.metadata.name,HOSTNET:.spec.hostNetwork,HOSTPID:.spec.hostPID

What to do now

Because no fixed version is named in the sources, focus on limiting who can trigger the flaw and on blocking dangerous pod settings at the cluster level, independent of OpenFunction.

  1. Inventory every cluster running OpenFunction and record the version in use.
  2. Review RBAC and remove create rights on Function and Serving resources from anyone who does not strictly need them.
  3. Enforce Pod Security Admission at the baseline or restricted level on tenant namespaces so privileged, host namespace and hostPath pods are rejected at admission.
  4. Consider a policy engine (for example Kyverno or OPA Gatekeeper) to deny privileged, hostNetwork, hostPID and hostPath in pods created by the OpenFunction controller.
  5. Audit existing pods and Function or Serving objects for host-level settings and investigate anything unexpected.
  6. Rotate credentials and review audit logs for any tenant account that created such resources before you applied controls.
  7. Watch the OpenFunction repository, issue 532 and the GitHub advisory for a patched release, and upgrade when one is published.
Caution. Enabling restrictive Pod Security Admission on a namespace can block existing workloads that rely on elevated settings. Test with the warn or audit mode first, then move to enforce.
Tip. If you cannot patch soon, treat tenant namespaces as untrusted for node-level access: apply network policies, restrict who can reach the Kubernetes API, and make sure worker nodes hold no secrets that would be valuable if one were reached.

Detection and monitoring

Kubernetes audit logs are your best source. Look for create events on Function and Serving resources by non-administrator users, and for pods created in tenant namespaces whose specs include privileged containers, host namespaces or hostPath volumes. Alert on any such pod appearing outside of namespaces that are expected to run system workloads.

On the node side, watch for unexpected processes or file access touching the host root filesystem from container runtimes. If you suspect a tenant abused this flaw, assume the node and anything it could reach, including mounted secrets and service account tokens, may be exposed and respond accordingly. Our guide on what to do when a website is hacked covers general incident steps.

If the workloads on your cluster serve public websites, outside-in monitoring helps you notice downstream effects such as unexpected certificate or DNS changes. Webforta Monitor covers uptime, certificates and DNS, though it cannot see inside your cluster.

What is still unknown

  • No patched version is listed in the advisory.
  • No exploitation in the wild is reported in the sources, and the CVE is not in CISA KEV.
  • The GitHub advisory is unreviewed and lists no package, so version scoping beyond 'through 1.2.0' is unconfirmed.
  • Coverage so far comes from a single independent publisher; details may change as maintainers respond.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-130587 - GitHub Advisory Databasegithub.com
  2. CVE-2026-130587: OpenFunction through 1.2.0 contains a privilege escalation vulnerability that allows namespace tenants to create privileged host-access pods by supplying…nvd.nist.gov ·
  • OpenFunction
  • Kubernetes
  • privilege escalation
  • CVE-2026-130587
  • container security