CVE-2025-3506
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFiles to be deployed with agents are accessible without authentication in Checkmk 2.1.0, Checkmk 2.2.0, Checkmk 2.3.0 and <Checkmk 2.4.0b6 allows attacker to access files that could contain secrets.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn Checkmk versions 2.1.0 through 2.3.0 and prior to 2.4.0b6, the agent deployment functionality allows unauthenticated access to files intended for agent distribution. Attackers can directly request these files without any authentication, potentially exposing configuration files, credentials, or other secrets embedded in agent deployment packages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2.1.0, <= 2.3.0= 2.4.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Checkmk versionRun the command to display the Checkmk version (such as 'omd version' or 'checkmk --version' depending on installation method)Affected if The installed version is 2.1.0, 2.2.0, 2.3.0, or 2.4.0 (any release prior to 2.4.0b6)
-
Determine if agent deployment or agent receiver is configuredInspect the Checkmk configuration to see if the agent deployment feature is enabled, typically through the web interface under 'Setup > Agents > Agent deployment' or by checking for related configuration filesAffected if Agent deployment is actively configured and the Checkmk version falls within the affected range
-
Verify network accessibility of agent deployment endpointsTest whether the agent deployment URLs (paths typically under /check_mk/ or /omd/ related to agent distribution) are reachable from untrusted network segments without any authentication credentialsAffected if The agent deployment endpoints respond without requiring authentication and the version is affected
-
Inspect agent deployment package contentsIf accessible, examine the files in the agent deployment directory to identify if configuration files, credentials, or other sensitive data are included in the agent packagesAffected if Sensitive files such as configuration files or credentials are present in the deployed agent packages and the version is affected
You are affected if your Checkmk version is 2.1.0 through 2.3.0 or 2.4.0 (prior to 2.4.0b6) AND the agent deployment functionality is enabled and accessible over the network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to Checkmk 2.4.0b6 or later. Until then, implement network-level access controls to restrict exposure of agent deployment endpoints to untrusted networks.
Checkmk 2.4.0b6 or later
- Upgrade Checkmk to version 2.4.0b6 or later (or the latest stable 2.4.x release)
- After upgrading, verify that agent deployment files now require authentication
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3506 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-3506 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data