dbcve.org
N CentralApplication · N Able

CVE-2025-11367

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-12
Fix available
A fix is available. Upgrade to 2025.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The N-central Software Probe < 2025.4 is vulnerable to Remote Code Execution via deserialization

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 · moderate confidence

The N-central Software Probe versions prior to 2025.4 contain a deserialization vulnerability that allows unauthenticated attackers to execute arbitrary code remotely. This stems from unsafe deserialization of untrusted data, likely through a network protocol or API endpoint used by the probe to communicate with the N-central server.

MitigationUpgrade the N-central Software Probe to version 2025.4 or later to remediate this vulnerability. Given the critical severity and RCE capability, this upgrade should be treated as urgent and deployed across all affected probe instances.

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
N CentralApplication
Affected:< 2025.4

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate N-central Software Probe installation
    Check system for N-central Software Probe - look for installation directory (commonly in Program Files or Program Files (x86) under N-able or N-able Technologies), or query installed programs via system inventory tools
    Affected if The probe software is found on the system
  2. Identify installed probe version
    Access the probe's version information - check the software's About/Properties window, its main executable file properties, or any version file within the probe installation directory
    Affected if Version cannot be determined or shows a version number
  3. Compare version against affected range
    Compare the identified version to 2025.4 - any version below 2025.4 (such as 2025.3.x, 2025.2.x, earlier 2025.x releases, or any 2024.x/2023.x versions) falls within the affected range
    Affected if Installed version is less than 2025.4 (for example: 2025.3, 2025.0, 2024.1, etc.)
  4. Verify probe service is active
    Confirm the N-central Software Probe service or process is running - check Windows Services, task manager, or process list for a probe-related service or executable
    Affected if Probe service is running and accepting network communications from the N-central server

If the N-central Software Probe is installed with a version lower than 2025.4 and the probe service is active, the environment is vulnerable to unauthenticated remote code execution via unsafe deserialization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2025.4 or later
Fixed in 2025.4
Interim mitigation

Upgrade the N-central Software Probe to version 2025.4 or later to remediate this vulnerability. Given the critical severity and RCE capability, this upgrade should be treated as urgent and deployed across all affected probe instances.

Recommended fix Moderate confidence

2025.4

  1. Review the N-central 2025.4 release notes and upgrade documentation at me.n-able.com for prerequisites and procedures
  2. Ensure you have a complete backup of your current N-central configuration and data
  3. Download the N-central 2025.4 (or later) upgrade package from the N-able customer portal at me.n-able.com
  4. Follow the documented upgrade procedure to apply the 2025.4 update to your N-central server
  5. After upgrading, verify that the N-central services start successfully and the probe communication is restored
  6. Confirm the version number displays as 2025.4 or later to verify the patch was applied

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in N Central Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11367 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11367 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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