CVE-2026-3103 — Deletion of passwords via RestApi
A logic error in the remove_password() function in Checkmk GmbH's Checkmk versions <2.4.0p23, <2.3.0p43, and 2.2.0 (EOL) allows a low-privileged user to cause data loss.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.3% (30-day exploitation probability)+3
- Technical severity (medium)+3
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.
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.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented mitigation — checkmk.com (NIST National Vulnerability Database)
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.
- Identify exposed assets running the affected vendor/product/version combinations (Checkmk Checkmk).
- Apply the documented mitigations until a definitive fix is available.
- Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Checkmk | Checkmk |
version 2.4.0-b1version 2.4.0-p13version 2.4.0-p12version 2.4.0-p11version 2.4.0-p10version 2.4.0-p1version 2.4.0-b6version 2.4.0-b5 and 71 moreversion 2.4.0-b4version 2.4.0-b3version 2.4.0-b2version 2.4.0-p14version 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-p42version 2.3.0-p41version 2.3.0-p40version 2.4.0-p3version 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.3.0-p4version 2.4.0-p22version 2.4.0-p21version 2.4.0-p20version 2.4.0-p2version 2.4.0-p19version 2.4.0-p18version 2.4.0-p17version 2.4.0-p16version 2.4.0-p15version 2.3.0-p11version 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.3.0-p13version 2.3.0-p12version 2.3.0-p21version 2.3.0-p10version 2.3.0-p1version 2.3.0-b6version 2.3.0-b5version 2.3.0-b4version 2.3.0-b3version 2.3.0-b2version 2.3.0-b1version 2.3.0version 2.3.0-p30version 2.3.0-p39version 2.3.0-p38version 2.3.0-p37version 2.3.0-p36version 2.3.0-p35version 2.3.0-p34version 2.3.0-p33version 2.3.0-p32version 2.3.0-p31version 2.2.0version 2.3.0-p3version 2.3.0-p29version 2.3.0-p28version 2.3.0-p27version 2.3.0-p26version 2.3.0-p25version 2.3.0-p24version 2.3.0-p23version 2.3.0-p22 |
Vulnerable | NIST National Vulnerability Database |
| Checkmk | Checkmk | version 2.2.0≥ 2.3.0 and < 2.3.0p43≥ 2.4.0 and < 2.4.0p23 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 5.3 | CVSS 4.0 | Medium | — | — | security@checkmk.com via NIST National Vulnerability Database |
| 5.3 | CVSS 4.0 | Medium | — | — | Checkmk via CVE Program (cve.org) e CISA ADP |
| 5.4 | CVSS 3.1 | Medium | 2.8 | 2.5 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.30%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Audit administrative actions and access to resources outside each user’s normal pattern.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · checkmk gmbh/checkmk
- SSVC assessment updated
- Record published
- Fix documented
- CVSS changed · 5.4
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
1 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-105331 mk-oracle: Local privilege escalation via malicious Oracle Instant Client 7d
- Medium CVE-2026-9549 Fix XSS in service discovery active check output Jun 8, 2026
- Medium CVE-2026-7765 User Messages widget leaked issuer messages on shared dashboards Jun 8, 2026
- Medium CVE-2026-8833 XSS in urls Jun 8, 2026
- Medium CVE-2026-8078 Fix stored XSS in global settings change log Jun 8, 2026
- Medium CVE-2026-7186 Fix stored XSS in URL dashboard widget via dangerous URI schemes Jun 8, 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 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-2026-3103 is "Deletion of passwords via RestApi", rated Medium. It affects Checkmk (Checkmk); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.4 describes technical severity. EPSS 0.30% 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.