Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2023-31209: Improper neutralization of active check command arguments in Checkmk < 2.1.0p32, < 2.0.0p38, < 2.2.0p4 leads t

47
This month
HIGH 8.8DOWNGRADEUPGRADE

CVE-2023-31209 is a high-severity flaw (CVSS 8.8) affecting checkmk, checkmk. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Improper neutralization of active check command arguments in Checkmk < 2.1.0p32, < 2.0.0p38, < 2.2.0p4 leads to arbitrary command execution for authenticated users.

Why this priority

  • High severity

A fixed release or distro patch exists.

Risk facts

CVSS score8.8 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance1.1% (top 34%)
CISA exploited listNo
WeaknessCWE-78, CWE-74
Published2023-08-10
Last modified2026-10-24
Publisher (CNA): Checkmk GmbH · Vendor: checkmk · tribe29

Last updated 2026-10-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

checkmk checkmk DOWNGRADE
Affected: 2.0.0 · 2.0.0 b1 · 2.0.0 b2 · 2.0.0 b3 · 2.0.0 b4 · 2.0.0 b5 · 2.0.0 b6 · 2.0.0 b7
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.0.0
1. Check installed version
apt-cache policy checkmk || rpm -q checkmk || checkmk --version
2. No fixed release: DOWNGRADE to a release before 2.0.0 (Debian / Ubuntu)
apt-cache madison checkmk sudo apt install checkmk=<VERSION_BEFORE_2.0.0> sudo apt-mark hold checkmk
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list checkmk sudo dnf downgrade checkmk-<VERSION_BEFORE_2.0.0> sudo dnf versionlock add checkmk
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
tribe29 checkmk UPGRADE
Affected: < 2.0.0
Fixed in: 2.0.0
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy checkmk || rpm -q checkmk || checkmk --version
2. UPGRADE to 2.0.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade checkmk
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade checkmk
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Exact fixes by distribution

A distro patch exists: prefer upgrading over downgrading.
Fedora 46 · gnome-shell-extension-tiling-assistant · FIXED · 56-1.fc46 · FEDORA-2026-ebf66a5321 · source
sudo dnf upgrade --advisory=FEDORA-2026-ebf66a5321
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2023-31209?

checkmk: downgrade or apply the listed mitigation; checkmk: upgrade to 2.0.0. Exact commands for each OS are on this page.

Is CVE-2023-31209 being exploited?

CVE-2023-31209 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2023-31209 affect?

CVE-2023-31209 affects checkmk, checkmk. Severity is high (CVSS 8.8). Improper neutralization of active check command arguments in Checkmk < 2.1.0p32, < 2.0.0p38, < 2.2.0p4 leads to arbitrary command execution for authenticated users.

How urgent is CVE-2023-31209?

Priority 47/100. High severity

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.