Skip to main content
Menu
CVEs

CVE

OpenFunction denial of service in serving controller

OpenFunction through 1.2.0 is affected when a Serving resource is created without a triggers section. The checked facts name no fixed version or patch ids.

CVE-2026-130588EUVD-2026-127016

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:N/VI:N/VA:H/SC:N/SI:N/SA:N

7.1HighCNA
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. A Serving resource is created without a triggers section (Spec.Triggers is nil). OpenFunction version 1.2.0 and earlier.

Published
Last modified
Reference
Last checked
30/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

OpenFunction is affected by a NULL pointer dereference in its Serving controller. An attacker who has permission to create Serving resources can reach it over the network by submitting one with the triggers section left out, which crashes the controller-manager and halts Function and Serving reconciliation cluster-wide until that object is deleted.

Original description

OpenFunction through 1.2.0 contains a NULL pointer dereference vulnerability in getServingRun that allows users permitted to create Serving resources to crash the operator by omitting the triggers section. Attackers can submit a Serving with nil Spec.Triggers to crash-loop the controller-manager, halting Function and Serving reconciliation cluster-wide until the object is deleted.

Who should check

Teams running the OpenFunction operator 1.2.0 or earlier, especially where users can create Serving resources.

“OpenFunction through 1.2.0 contains a NULL pointer dereference vulnerability”

vulncheck.com

cve.now Index

30Pcve.now Index 30 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects Go packages
  • Severity7.1/10CVSS 7.1
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 80 if added to CISA KEV
  • Would score about 75 if CISA's SSVC rates exploitation active
  • Would score about 37 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    A Serving resource is created without a triggers section (Spec.Triggers is nil). OpenFunction version 1.2.0 and earlier.
  • Workaround: The checked facts give no vendor workaround. Limiting the affected feature means creating Serving resources only with a triggers section, and deleting any existing Serving object that lacks one.

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-130588 (OpenFunction through 1.2.0 NULL Pointer Dereference DoS via Serving Controller), 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-130588 (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):
- A Serving resource is created without a triggers section (Spec.Triggers is nil). (source: https://www.vulncheck.com/advisories/openfunction-through-1.2.0-null-pointer-dereference-dos-via-serving-controller)
- OpenFunction version 1.2.0 and earlier. (source: https://www.vulncheck.com/advisories/openfunction-through-1.2.0-null-pointer-dereference-dos-via-serving-controller)
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-130588 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130588 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/533
- https://github.com/OpenFunction/OpenFunction/blob/v1.2.0/controllers/core/serving_controller.go#L217
- https://www.vulncheck.com/advisories/openfunction-through-1.2.0-null-pointer-dereference-dos-via-serving-controller
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-130588
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-130588"}.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  3. Record last updated
  4. First seen by cve.now

Affected versions

Evidence 5

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 3

  1. Report
  2. Repository
  3. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130588

Is CVE-2026-130588 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?

A NULL pointer dereference in getServingRun crashes the controller-manager when a Serving resource is created without a triggers section. The repeated crash halts Function and Serving reconciliation cluster-wide until that object is deleted.Source: vulncheck.com

Which versions are affected by CVE-2026-130588?

github.com/openfunction (Go): through 1.2.0.Source: cve.now feed data

Am I affected, and how do I check?

OpenFunction 1.2.0 and earlier are in the affected range. The affected setup is a Serving resource whose spec omits the triggers section (Spec.Triggers is nil), so check Serving manifests in a cluster for a missing triggers section.Source: vulncheck.com

How do I fix CVE-2026-130588?

The checked facts name no fixed version or vendor patch identifier, so no upgrade target can be given. Check the OpenFunction advisory for a fix.Source: vulncheck.com

What if there's no patch?

The checked facts give no vendor workaround. Limiting the affected feature means creating Serving resources only with a triggers section, and deleting any existing Serving object that lacks one.Source: vulncheck.com

More CVEs