Skip to main content
CVE-2026-130588VulnerabilityPublished

OpenFunction through 1.2.0 contains a NULL pointer dereference vulnerability in getServingRun that allows users

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-130588· High 7.1

Not known to be exploited · CVSS 7.1 High.

Data as of 17 Nov 2026, 17:04 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.07.1
CNA (VulnCheck)CVSS 3.16.5
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
OpenFunctionOpenFunctionAffected
  • <=1.2.0
Fixed in–
GoOpenFunctionpkg:golang/OpenFunctionOther threatsAffected
  • <=1.2.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should restrict permissions to create Serving resources to trusted users only. If a crash-loop occurs, the affected Serving resource with nil Spec.Triggers must be deleted to restore controller-manager functionality. Monitor vendor advisories for any forthcoming patches or official remediation guidance.

Description

OpenFunction versions through 1.2.0 have a NULL pointer dereference vulnerability in the getServingRun function. This flaw allows users with permission to create Serving resources to crash the operator by submitting a Serving resource with a nil Spec.Triggers section. The crash causes the controller-manager to enter a crash loop, halting Function and Serving reconciliation across the cluster until the problematic object is removed.

References

Community reviews

Loading reviews…