CVE-2025-64997: Insufficient permission validation when showing agent information
Noroxi assessment
Priority: Monitor (action score 25/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Checkmk GmbH Checkmk 2.3.0p42, 2.4.0p17.
Low priority for now. Upgrade to Checkmk GmbH Checkmk 2.3.0p42, 2.4.0p17 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Insufficient permission validation in Checkmk versions prior to 2.4.0p17 and 2.3.0p42 allow low-privileged users to view agent information via the REST API, which could lead to information disclosure.
- Published
- Dec 18, 2025
- Updated
- Oct 13, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-280
Report tools
Action score
25
Monitor
Low priority for now.
- CVSS
- 25 / 40 · 6.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Checkmk
- 6.3
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:H/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| checkmk | checkmk | cpe:2.3:a:checkmk:checkmk |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- checkmk checkmk2.2.0
- checkmk checkmk2.3.0
- checkmk checkmk2.4.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Checkmk). Independent of NVD's CPE analysis and usually ahead of it.
Checkmk GmbH Checkmk
- 2.4.0 and later · before 2.4.0p17affected · semver
- 2.3.0 and later · before 2.3.0p42affected · semver
Same product
checkmk: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-28825Brute-force protection ineffective for some login methods39Monitor
- CVE-2022-48317Insecure Termination of RestAPI Session Tokens39Monitor
- CVE-2025-39666omd: Local privilege escalation when executing omd commands as root37Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-58122Nov 18, 2025 · Insufficient permission validation when configuring notification parameters21Monitor
- ← EarlierCVE-2025-64996Nov 18, 2025 · Overly broad file permissions in the mk_inotify plugin allows reading and manipulating the plugin's output19Monitor
- Later →CVE-2025-65000Dec 18, 2025 · Exposure of SSH Private Keys in Remote Alert Handlers (Linux) Rule9Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Checkmk GmbH Checkmk | 2.3.0p42 | Vendor (CNA) |
| Checkmk GmbH Checkmk | 2.4.0p17 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- PS Positive Security GmbHreporter
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-5812130 days apartInsufficient permission validation on multiple REST API endpoints21Monitor
- CVE-2025-5812230 days apartInsufficient permission validation when configuring notification parameters21Monitor
- CVE-2026-24096104 days apartInsufficient permission validation on multiple REST API Quick Setup endpoints21Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-280 · Improper Handling of Insufficient Permissions or PrivilegesCVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.