nday
CVE-2026-130587

OpenFunction through 1.2.0 Privilege Escalation via Unrestricted PodSpec Templates

OpenFunction / OpenFunction

A public PoC appeared 1 day after disclosure. nday has no fix record for it yet; that does not mean no patch exists. Listed by 1 of 4 PoC sources: github. Not in CISA KEV.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

broken access control
CWE-862, stated by the CNA VulnCheck and NVD, republishing [email protected]
network
AV:N in 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 (CVSS 4.0) from the CNA VulnCheck
no user interaction
UI:N in 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 (CVSS 4.0) from the CNA VulnCheck
stage
POC
disclosed
disclosure → PoC
T+1d POC is date-only
cvss
9.4 CRITICAL v4.0

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
11-17T13:52Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
11-18, date only
ITWexploited
no record yet
KEVKEV
no record yet

Summary

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.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:L
Low: no target-specific security measures to get around
Attack requirements AT:N
None: success does not depend on how the target is deployed or running
Privileges required PR:L
Low: ordinary user privileges
User interaction UI:N
None: no action by anyone other than the attacker

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

CVSS 4.0 vector from the CVE record, scored by the CNA VulnCheck.

Event log

+DISdisclosed

CVE record published by VulnCheck. CVSS 9.4, critical.

src cvelist · nday , observed live · raw
{
  "id": 476188,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-130587",
  "occurred_at": "2026-11-17T13:52:16.263Z",
  "observed_at": "2026-11-17T14:02:30.435931Z",
  "is_backfill": false,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "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",
      "version": "4.0",
      "base_score": 9.4,
      "base_severity": "CRITICAL"
    },
    "ssvc": {
      "timestamp": "2026-11-17T16:06:40.650867Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2026-11-17T13:52:16.263Z",
    "assigner_short_name": "VulnCheck"
  }
}
2026-11-18date only, from source
+POCpublic PoC

PoC repository on GitHub: googlesky/CVE-2026-130587. The date is the repository's creation day.

src github 1462623621 · nday , observed live · raw
{
  "id": 487406,
  "type": "poc_published",
  "source": "github",
  "url": "https://github.com/googlesky/CVE-2026-130587",
  "occurred_at": "2026-11-18T10:07:39Z",
  "observed_at": "2026-11-19T00:00:00Z",
  "is_backfill": false,
  "dedupe_key": "1462623621",
  "detail": {
    "url": "https://github.com/googlesky/CVE-2026-130587",
    "title": "googlesky/CVE-2026-130587",
    "precision": "day"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.