CVE
OpenFunction privilege escalation via unrestricted PodSpec templates
Affects OpenFunction through 1.2.0, where Function or Serving resources accept an unrestricted PodSpec template. The checked facts name no fixed version or vendor patch.
Written by a model from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affects OpenFunction through version 1.2.0 Function or Serving resources accept an unrestricted PodSpec template that the operator copies into workloads
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 33/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
OpenFunction has a privilege escalation flaw that a remote attacker with low-privilege login can exploit over the network. By supplying unrestricted PodSpec templates in Function or Serving resources, an attacker with only create permissions for those resources can set privileged, hostNetwork, hostPID, or hostPath fields, mount the worker node's root filesystem, and gain node access.
Original description
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.
Who should check
Teams running OpenFunction 1.2.0 or earlier where namespace tenants hold Function or Serving create rights
“OpenFunction through 1.2.0 contains a privilege escalation vulnerability”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects Go packages
- Severity10/10CVSS 9.4, total technical impact per CISA
- No patch5/5No patch listed yet
What would change the score
- Would score about 83 if added to CISA KEV
- Would score about 78 if CISA's SSVC rates exploitation active
- Would score about 40 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affects OpenFunction through version 1.2.0 Function or Serving resources accept an unrestricted PodSpec template that the operator copies into workloadsWorkaround: The checked facts give no vendor workaround. Limiting who can create Function or Serving resources would restrict the path the vulnerability describes.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130587 (OpenFunction through 1.2.0 Privilege Escalation via Unrestricted PodSpec Templates), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130587 (entry last updated 2026-11-17):
Affected:
- Go package github.com/openfunction: through 1.2.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Affects OpenFunction through version 1.2.0 (source: https://www.vulncheck.com/advisories/openfunction-through-1.2.0-privilege-escalation-via-unrestricted-podspec-templates)
- Function or Serving resources accept an unrestricted PodSpec template that the operator copies into workloads (source: https://github.com/OpenFunction/OpenFunction/issues/532)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130587 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130587 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/OpenFunction/OpenFunction/issues/532
- https://github.com/OpenFunction/OpenFunction/blob/v1.2.0/pkg/core/serving/openfuncasync/servingrun.go#L320
- https://github.com/OpenFunction/OpenFunction/blob/v1.2.0/apis/core/v1beta2/serving_types.go#L225
- https://www.vulncheck.com/advisories/openfunction-through-1.2.0-privilege-escalation-via-unrestricted-podspec-templates
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130587
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130587"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
- Posted on X by cve.now
Affected versions
through 1.2.0
Evidence 6
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 4
- Report
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130587
Is CVE-2026-130587 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Function and Serving resources accept a complete, unrestricted PodSpec template that the operator copies into workloads. This lets an attacker create privileged host-access pods that mount the worker node's root filesystem and gain node access.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-130587?
github.com/openfunction (Go): through 1.2.0.Source: cve.now feed data
Am I affected, and how do I check?
OpenFunction through version 1.2.0 is affected in the setup where Function or Serving resources are used. To check a deployment, look at the installed OpenFunction version and whether Function or Serving CRDs are in use.Source: vulncheck.com, github.com
How do I fix CVE-2026-130587?
The checked facts name no fixed version and no vendor patch IDs, so no upgrade target can be stated from them. Check the OpenFunction vendor for a fix that is newer than 1.2.0.Source: vulncheck.com, github.com
What if there's no patch?
The checked facts give no vendor workaround. Limiting who can create Function or Serving resources would restrict the path the vulnerability describes.Source: vulncheck.com, github.com