WhatBrokeToday
GTA 6FAQ
Kubernetes

Checkmk Kubernetes Special Agent Argument Injection Vulnerability (CVE-2026-121374)

critical

Is it fixed? Not yet.

Ongoing since Nov 11, 11:17 UTC. First reported Nov 11, 11:17 UTC.

What happened

An argument injection vulnerability in the Kubernetes special agent in Checkmk allows authenticated users with rule-editing permissions to write files to arbitrary locations and achieve code execution. Affected versions include releases prior to 2.5.0p19, prior to 2.4.0p40, and version 2.3.0 (EOL).

What caused it?

Argument injection via crafted node roles in the 'Exclude nodes based on their role' rule option in the Kubernetes special agent allows arbitrary file writes.

No verified workaround yet

None of the linked reports describe a mitigation. This page updates when one appears.

Official fix

Timeline

  1. Investigating(current)
  2. Workaround available(upcoming)
  3. Resolved(upcoming)
  1. First report on security advisory

    Kubernetes special agent in Checkmk <2.5.0p19, <2.4.0p40, and: CVE-2026-121374 (Critical)

    Source

Evidence

1 report · 1 CVEShow
  1. [1]
    CVE First report
    Kubernetes special agent in Checkmk <2.5.0p19, <2.4.0p40, and: CVE-2026-121374 (Critical)(opens security advisory in a new tab)

    Critical severity. Argument injection in the Kubernetes special agent in Checkmk <2.5.0p19, <2.4.0p40, and 2.3.0 (EOL) allows a user with permission to edit rules in at least one folder to write files to arbitrary locations writable by the site user via crafted node roles in the "Exclude nodes based on their role" rule option, leading to code execution as the site user.

    by Tenable 0upvotes 0comments

FAQ

What happened in the Kubernetes issue?

An argument injection vulnerability in the Kubernetes special agent in Checkmk allows authenticated users with rule-editing permissions to write files to arbitrary locations and achieve code execution. Affected versions include releases prior to 2.5.0p19, prior to 2.4.0p40, and version 2.3.0 (EOL).

What is affected by the Kubernetes issue?

Kubernetes (versions: <2.5.0p19, <2.4.0p40, and 2.3.0). Also affected at the same time: Bun.

When did the Kubernetes issue start and end?

It started Nov 11, 11:17 UTC and is still ongoing (7 d 17 h so far). This page updates as it develops.

How do I get alerts for Kubernetes?

Subscribe to the Kubernetes RSS feed for every new Kubernetes incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Kubernetes is down. Kubernetes feed

Where does this information come from?

WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.