CVE-2025-11366
Executive Summary
CVE-2025-11366 is a critical authentication bypass vulnerability in N-able N-central, a remote monitoring and management (RMM) platform. The flaw allows an unauthenticated attacker to bypass authentication mechanisms via a path traversal attack, potentially gaining administrative access to the N-central server. This could lead to full compromise of the RMM infrastructure, enabling lateral movement into managed endpoints, data exfiltration, and deployment of ransomware or other malicious payloads. The vulnerability affects all versions prior to N-central 2025.4. No public proof-of-concept (PoC) or exploit code is currently available, but the risk is severe due to the privileged position of RMM software in enterprise networks.
This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.
No signup required
CVSS Breakdown & Threat Level
- CVSS Score: 10.0 (Critical)
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
Threat Level: Critical. The vulnerability requires no authentication, no user interaction, and can be exploited remotely over the network. Successful exploitation grants full administrative control over the N-central server, which is a high-value target in any organization.
Deep Dive & Mechanics
The vulnerability resides in the authentication mechanism of N-central. The software fails to properly sanitize user-supplied input when processing authentication requests. By crafting a malicious path traversal sequence (e.g., ../), an attacker can manipulate the authentication logic to bypass credential checks and gain unauthorized access.
Root Cause: The application uses user-controlled input to construct file paths or resource identifiers without adequate validation. When the authentication module attempts to verify credentials or session tokens, it follows the manipulated path, effectively skipping the authentication step.
Attack Vector: An attacker sends a specially crafted HTTP request to the N-central web interface. The request includes path traversal sequences in the URL or POST parameters that target authentication-related resources. The server processes the request and, due to the path traversal, returns a valid session or administrative token without requiring valid credentials.
Impact: Once authenticated, the attacker can:
- Access the N-central management console.
- Deploy agents or scripts to managed endpoints.
- Exfiltrate sensitive data (e.g., credentials, configuration files).
- Disable or modify monitoring and security controls.
- Use the RMM as a pivot point for further attacks.
Vulnerable vs. Patched Code
Vulnerable Code (Conceptual):
# Vulnerable authentication handler
def authenticate(request):
token_path = request.GET.get('token', 'default_token')
# Path traversal not sanitized
with open('/auth/tokens/' + token_path, 'r') as f:
token_data = f.read()
if validate_token(token_data):
return create_session()
else:
return "Authentication failed"
Patched Code (Conceptual):
# Patched authentication handler
import os
def authenticate(request):
token_path = request.GET.get('token', 'default_token')
# Sanitize input to prevent path traversal
safe_path = os.path.normpath('/auth/tokens/' + token_path)
if not safe_path.startswith('/auth/tokens/'):
return "Invalid token path"
with open(safe_path, 'r') as f:
token_data = f.read()
if validate_token(token_data):
return create_session()
else:
return "Authentication failed"
The patched version uses os.path.normpath() to resolve the path and then checks that the resolved path still starts with the expected base directory, preventing traversal outside the allowed directory.
Exploitation & Lab Setup
Red Team (Exploitation):
- Setup: Deploy a vulnerable instance of N-central (version < 2025.4) in an isolated lab environment.
- Reconnaissance: Identify the N-central web interface (typically on port 443 or 8443).
- Craft Payload: Use a path traversal sequence to bypass authentication. Example request:
Note: The exact parameter and path may vary; this is a conceptual example.POST /login HTTP/1.1 Host: target-ncentral.com Content-Type: application/x-www-form-urlencoded token=../../../../etc/passwd&username=admin&password=anything - Execute: Send the crafted request using tools like
curlor Burp Suite.curl -X POST https://target-ncentral.com/login -d "token=../../../../etc/passwd&username=admin&password=test" - Verify: If successful, the response will contain a session cookie or token granting administrative access.
Blue Team (Detection & Defense):
- Monitor Logs: Look for unusual HTTP requests containing
../or%2e%2e%2f(URL-encoded path traversal) in the N-central access logs. - Network Detection: Deploy network-based IDS/IPS rules to detect path traversal patterns.
- Honeypot: Set up a decoy N-central instance to capture exploitation attempts.
- Immediate Actions:
- Block IPs exhibiting path traversal behavior.
- Review authentication logs for unauthorized access.
- Isolate the N-central server if compromise is suspected.
Indicators of Compromise (IOCs)
Network IOCs:
- HTTP requests containing
../or%2e%2e%2fin thetokenparameter or similar fields. - Unusual POST requests to
/loginor/authenticateendpoints. - Responses containing session tokens without prior valid authentication.
- HTTP requests containing
File System IOCs:
- Unexpected files in
/auth/tokens/directory (if accessible). - Modified authentication logs showing successful logins from unknown IPs.
- Unexpected files in
Log IOCs:
- N-central access logs showing
200 OKresponses to requests with path traversal patterns. - Application logs with errors like
FileNotFoundErrororPermissionErrorrelated to token paths.
- N-central access logs showing
Detection Engineering
YARA Rule:
rule CVE_2025_11366_PathTraversal {
meta:
description = "Detects path traversal attempts targeting N-able N-central authentication bypass"
author = "Valters IT"
date = "2025-04-10"
reference = "CVE-2025-11366"
strings:
$traversal1 = "../"
$traversal2 = "..\\"
$traversal3 = "%2e%2e%2f"
$traversal4 = "%2e%2e%5c"
$auth_param = "token="
condition:
any of ($traversal*) and $auth_param
}
Sigma Rule:
title: N-able N-central Authentication Bypass via Path Traversal
id: 7a8b9c0d-1e2f-3a4b-5c6d-7e8f9a0b1c2d
status: experimental
description: Detects HTTP requests with path traversal patterns targeting N-central authentication
author: Valters IT
date: 2025-04-10
logsource:
category: webserver
product: ncentral
detection:
selection:
cs-method: 'POST'
cs-uri-query|contains:
- '../'
- '..\\'
- '%2e%2e%2f'
- '%2e%2e%5c'
cs-uri-query|contains: 'token='
condition: selection
falsepositives:
- Legitimate use of path traversal in other contexts (rare)
level: critical
Suricata Rule:
alert http any any -> any any (msg:"CVE-2025-11366 N-able N-central Authentication Bypass Attempt"; flow:to_server; content:"POST"; http_method; content:"/login"; http_uri; content:"token="; http_client_body; pcre:"/(\.\.\/|\.\.\\|%2e%2e%2f|%2e%2e%5c)/Ri"; classtype:attempted-admin; sid:1000001; rev:1;)
Remediation & Mitigation
Immediate Actions:
- Upgrade: Update N-central to version 2025.4 or later immediately. This is the only complete fix.
- Workaround: If immediate patching is not possible, restrict network access to the N-central web interface using firewall rules or VPNs. Only allow trusted IPs.
- Web Application Firewall (WAF): Deploy a WAF rule to block path traversal patterns in HTTP requests.
Long-Term Measures:
- Implement strict input validation and sanitization for all user-supplied data.
- Conduct regular security audits and penetration testing of RMM infrastructure.
- Monitor for unusual authentication patterns and implement anomaly detection.
- Ensure all RMM components are kept up-to-date with the latest security patches.
Valters IT