CVE-2025-32918: Livestatus injection in autocomplete endpoint

Published Jul 4, 2025
·
Updated

Improper neutralization of Livestatus command delimiters in autocomplete endpoint within the RestAPI of Checkmk versions <2.4.0p6, <2.3.0p35, <2.2.0p44, and 2.1.0 (EOL) allows an authenticated user to inject arbitrary Livestatus commands.

Affected Software

108 affected components
Checkmk Checkmk<2.4.0p6, <2.3.0p35, <2.2.0p44
Checkmk Checkmk=2.1.0
Checkmk Checkmk=2.2.0
Checkmk Checkmk=2.2.0-b1
Checkmk Checkmk=2.2.0-b2
Checkmk Checkmk=2.2.0-b3
Checkmk Checkmk=2.2.0-b4
Checkmk Checkmk=2.2.0-b5
Checkmk Checkmk=2.2.0-b6
Checkmk Checkmk=2.2.0-b7
Checkmk Checkmk=2.2.0-b8
Checkmk Checkmk=2.2.0-i1
Checkmk Checkmk=2.2.0-p1
Checkmk Checkmk=2.2.0-p10
Checkmk Checkmk=2.2.0-p11
Checkmk Checkmk=2.2.0-p12
Checkmk Checkmk=2.2.0-p13
Checkmk Checkmk=2.2.0-p14
Checkmk Checkmk=2.2.0-p15
Checkmk Checkmk=2.2.0-p16
Checkmk Checkmk=2.2.0-p17
Checkmk Checkmk=2.2.0-p18
Checkmk Checkmk=2.2.0-p19
Checkmk Checkmk=2.2.0-p2
Checkmk Checkmk=2.2.0-p20
Checkmk Checkmk=2.2.0-p21
Checkmk Checkmk=2.2.0-p22
Checkmk Checkmk=2.2.0-p23
Checkmk Checkmk=2.2.0-p24
Checkmk Checkmk=2.2.0-p25
Checkmk Checkmk=2.2.0-p26
Checkmk Checkmk=2.2.0-p27
Checkmk Checkmk=2.2.0-p28
Checkmk Checkmk=2.2.0-p29
Checkmk Checkmk=2.2.0-p3
Checkmk Checkmk=2.2.0-p30
Checkmk Checkmk=2.2.0-p31
Checkmk Checkmk=2.2.0-p32
Checkmk Checkmk=2.2.0-p33
Checkmk Checkmk=2.2.0-p34
Checkmk Checkmk=2.2.0-p35
Checkmk Checkmk=2.2.0-p36
Checkmk Checkmk=2.2.0-p37
Checkmk Checkmk=2.2.0-p38
Checkmk Checkmk=2.2.0-p39
Checkmk Checkmk=2.2.0-p4
Checkmk Checkmk=2.2.0-p40
Checkmk Checkmk=2.2.0-p41
Checkmk Checkmk=2.2.0-p42
Checkmk Checkmk=2.2.0-p43
Checkmk Checkmk=2.2.0-p5
Checkmk Checkmk=2.2.0-p6
Checkmk Checkmk=2.2.0-p7
Checkmk Checkmk=2.2.0-p8
Checkmk Checkmk=2.2.0-p9
Checkmk Checkmk=2.3.0
Checkmk Checkmk=2.3.0-b1
Checkmk Checkmk=2.3.0-b2
Checkmk Checkmk=2.3.0-b3
Checkmk Checkmk=2.3.0-b4
Checkmk Checkmk=2.3.0-b5
Checkmk Checkmk=2.3.0-b6
Checkmk Checkmk=2.3.0-p1
Checkmk Checkmk=2.3.0-p10
Checkmk Checkmk=2.3.0-p11
Checkmk Checkmk=2.3.0-p12
Checkmk Checkmk=2.3.0-p13
Checkmk Checkmk=2.3.0-p14
Checkmk Checkmk=2.3.0-p15
Checkmk Checkmk=2.3.0-p16
Checkmk Checkmk=2.3.0-p17
Checkmk Checkmk=2.3.0-p18
Checkmk Checkmk=2.3.0-p19
Checkmk Checkmk=2.3.0-p2
Checkmk Checkmk=2.3.0-p20
Checkmk Checkmk=2.3.0-p21
Checkmk Checkmk=2.3.0-p22
Checkmk Checkmk=2.3.0-p23
Checkmk Checkmk=2.3.0-p24
Checkmk Checkmk=2.3.0-p25
Checkmk Checkmk=2.3.0-p26
Checkmk Checkmk=2.3.0-p27
Checkmk Checkmk=2.3.0-p28
Checkmk Checkmk=2.3.0-p29
Checkmk Checkmk=2.3.0-p3
Checkmk Checkmk=2.3.0-p30
Checkmk Checkmk=2.3.0-p31
Checkmk Checkmk=2.3.0-p32
Checkmk Checkmk=2.3.0-p33
Checkmk Checkmk=2.3.0-p34
Checkmk Checkmk=2.3.0-p4
Checkmk Checkmk=2.3.0-p5
Checkmk Checkmk=2.3.0-p6
Checkmk Checkmk=2.3.0-p7
Checkmk Checkmk=2.3.0-p8
Checkmk Checkmk=2.3.0-p9
Checkmk Checkmk=2.4.0
Checkmk Checkmk=2.4.0-b1
Checkmk Checkmk=2.4.0-b2
Checkmk Checkmk=2.4.0-b3
Checkmk Checkmk=2.4.0-b4
Checkmk Checkmk=2.4.0-b5
Checkmk Checkmk=2.4.0-b6
Checkmk Checkmk=2.4.0-p1
Checkmk Checkmk=2.4.0-p2
Checkmk Checkmk=2.4.0-p3
Checkmk Checkmk=2.4.0-p4
Checkmk Checkmk=2.4.0-p5

Event History

Jul 4, 2025
CVE Published
via MITRE·08:12 AM
Data Sourced
via MITRE·08:12 AM
DescriptionWeakness
Data Sourced
via NVD·08:15 AM
DescriptionSeverityWeaknessAffected Software
Apr 23, 57611
Event
via NVD·01:09 PM

Frequently Asked Questions

1

What is the severity of CVE-2025-32918?

CVE-2025-32918 has been assessed as a high severity vulnerability due to its potential for command injection.

2

How do I fix CVE-2025-32918?

To fix CVE-2025-32918, upgrade Checkmk to version 2.4.0p6 or later, or patch the affected versions as advised by the vendor.

3

Who is affected by CVE-2025-32918?

CVE-2025-32918 affects users of Checkmk versions prior to 2.4.0p6, 2.3.0p35, and 2.2.0p44.

4

What type of vulnerability is CVE-2025-32918?

CVE-2025-32918 is classified as an improper neutralization of Livestatus command delimiters, allowing for command injection.

5

Can CVE-2025-32918 be exploited remotely?

CVE-2025-32918 requires authentication, so it cannot be exploited remotely without valid credentials.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203