CVE Intelligence
High File handling exploit reference

CVE-2025-32919 — Privilege Escalation in Windows License plugin for Checkmk Windows Agent

Use of an insecure temporary directory in the Windows License plugin for the Checkmk Windows Agent allows Privilege Escalation. This issue affects Checkmk: from 2.4.0 before 2.4.0p13, from 2.3.0 before 2.3.0p38, from 2.2.0 before 2.2.0p46, and all versions of 2.1.0 (EOL).

Published Oct 9, 2025 · Updated Oct 19, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: Checkmk

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.3% (30-day exploitation probability)+3
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.27%
ahead of 18% of scored CVEs · Oct 20, 2026
Affects
Checkmk
Checkmk
CVSS base
7.8
High · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Checkmk Checkmk).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (file handling), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Checkmk Checkmk version 2.3.0-p24version 2.3.0-p35version 2.3.0-p34version 2.3.0-p33version 2.3.0-p32version 2.3.0-p31version 2.3.0-p30version 2.3.0-p3
and 87 more version 2.3.0-p29version 2.3.0-p28version 2.3.0-p27version 2.3.0-p26version 2.3.0-p25version 2.3.0-p36version 2.3.0-p23version 2.3.0-p22version 2.3.0-p21version 2.3.0-p20version 2.3.0-p2version 2.3.0-p19version 2.3.0-p18version 2.3.0-p17version 2.3.0-p16version 2.3.0-p15version 2.3.0-p14version 2.4.0-p12version 2.4.0-p9version 2.4.0-p8version 2.4.0-p7version 2.4.0-p6version 2.4.0-p5version 2.4.0-p4version 2.4.0-p3version 2.4.0-p2version 2.3.0-p13version 2.4.0-p11version 2.4.0-p10version 2.4.0-p1version 2.4.0version 2.3.0-p9version 2.3.0-p8version 2.3.0-p7version 2.3.0-p6version 2.3.0-p5version 2.3.0-p4version 2.3.0-p37version 2.2.0-p21version 2.2.0-p32version 2.2.0-p31version 2.2.0-p30version 2.2.0-p3version 2.2.0-p29version 2.2.0-p28version 2.2.0-p27version 2.2.0-p26version 2.2.0-p25version 2.2.0-p24version 2.2.0-p23version 2.2.0-p22version 2.2.0-p33version 2.2.0-p19version 2.2.0-p18version 2.2.0-p17version 2.2.0-p16version 2.2.0-p14version 2.2.0-p13version 2.2.0-p12version 2.2.0-p11version 2.2.0-p10version 2.2.0-p1version 2.2.0version 2.2.0-p44version 2.3.0-p12version 2.3.0-p11version 2.3.0-p10version 2.3.0-p1version 2.3.0version 2.2.0-p9version 2.2.0-p8version 2.2.0-p7version 2.2.0-p6version 2.2.0-p5version 2.2.0-p45≥ 2.1.0 and < 2.2.0version 2.2.0-p43version 2.2.0-p42version 2.2.0-p41version 2.2.0-p40version 2.2.0-p4version 2.2.0-p39version 2.2.0-p38version 2.2.0-p37version 2.2.0-p36version 2.2.0-p35version 2.2.0-p34
Vulnerable NIST National Vulnerability Database
Checkmk Checkmk version 2.1.0≥ 2.2.0 and < 2.2.0p46≥ 2.3.0 and < 2.3.0p38≥ 2.4.0 and < 2.4.0p13 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.8 CVSS 4.0 High — — security@checkmk.com via NIST National Vulnerability Database
8.8 CVSS 4.0 High — — Checkmk via CVE Program (cve.org) e CISA ADP
7.8 CVSS 3.1 High 1.8 5.9 nvd@nist.gov via NIST National Vulnerability Database
7.8 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-427 · Uncontrolled Search Path Element

Other CVEs with this weakness →

EPSS over time FIRST

Oct 19, 2026 → Oct 20, 2026 · 2 reading(s) · max 0.27%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Monitor file creation in web directories and paths with traversal sequences (../).
endpoint telemetry (EDR)file integrity (FIM)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · checkmk gmbh/checkmk
    Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 19, 2026
  • CVSS changed · 7.8
    Oct 19, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 19, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 19, 2026 · NIST National Vulnerability Database
  • 2025
  • CVE published
    Oct 9, 2025 · Checkmk

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 19, 2026 – Oct 19, 2026
  • 1× Official description updated · Oct 19, 2026 – Oct 19, 2026

References

5 on the record

Elsewhere on this site

Checkmk
every CVE for this vendor
File handling
same class
CWE-427
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-14452 Open redirect and XSS via reset_url parameter 5d
  • CVE-2026-105331 mk-oracle: Local privilege escalation via malicious Oracle Instant Client 13d
  • CVE-2026-92882 Redact SNMP community, SNMPv3 pass phrases, and IPMI password in host config REST API GET responses 29d
  • CVE-2026-90990 Livestatus injection via monitoring filter values 29d
  • CVE-2026-77021 Missing decompression size limit in agent receiver allows memory exhaustion via push agent data Sep 21, 2026
  • CVE-2026-15937 Agent receiver certificate confusion allows authentication with a certificate issued for another endpoint Sep 4, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-32919 is "Privilege Escalation in Windows License plugin for Checkmk Windows Agent", rated High. It affects Checkmk (Checkmk); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 0.27% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.