Skip to main content
Menu
CVEs

CVE

N-able N-central root command execution in audit export syslog config

CVE-2026-129273EUVD-2026-126958GHSA-3PX6-WQQR-XFQ5

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

8.6HighCNA
Exploited
No known exploitation
Fix
Fixed in 2026.4.1 HF3
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 2026.4.1 HF3.

Published
Last modified
Reference
Last checked
13/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

N-able's N-central has a flaw in its Audit Export setting: the setting is written to the system logging configuration without filtering out control characters. An attacker who can reach it over the network and log in with product administrator privileges can inject configuration and run commands as root on the N-central server.

Written by a model from the sources below. Verify against them.

Original description

N-able N-central before 2026.4.1 HF3 does not neutralise control characters in an Audit Export setting before writing it to the system logging configuration. An authenticated attacker with product administrator privileges can inject configuration and execute commands as root on the N-central server.

cve.now Index

13Pcve.now Index 13 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.6/10CVSS 8.6, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 32 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 2026.4.1 HF3.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129273 (N-central Audit Export syslog configuration injection allows root command execution), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129273 (entry last updated 2026-11-17):
Affected:
- N-able N-central: fixed in 2026.4.1 HF3
Fixed versions: 2026.4.1 HF3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129273 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129273 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://me.n-able.com/s/security-advisory/aArVy0000002jkDKAQ
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129273
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129273"}.

Timeline

  1. cve.now early warning

    N-able investigates new N-central exploits claimed to give root RCE

    5 days
  2. CVE published
  3. First seen by cve.now
  4. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  5. Record last updated

Affected versions

  • N-able N-central

    fixed in 2026.4.1 HF3

Evidence 3

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129273

Is CVE-2026-129273 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-129273?

N-central: before 2026.4.1 HF3.Source: cve.now feed data

How do I fix CVE-2026-129273?

Upgrade to a fixed version: 2026.4.1 HF3.Source: cve.now feed data

More CVEs