Skip to main content
Mallory
HighVulnerability

CVE-2026-125878: OGNL Injection Leading to RCE in N-able N-central

Published Nov 10, 2026 · Updated 1 day ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days17 mentions · peak 8 in a dayToday
CVSS8.7High · v4
EPSS0.41%36th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-125878CWE-79 · Improper Neutralization of Input…

CVE-2026-125878 affects N-able N-central versions before 26.4.1 and encompasses multiple OGNL injection vulnerabilities associated with remote code execution. The CVE classification describes improper neutralization of input during web page generation, categorized as CWE-79, allowing resource injection; this differs from the OGNL injection terminology used in the vulnerability title. The vulnerability is network-accessible and requires low privileges but no user interaction. Specific vulnerable functions and injection parameters are not established.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can enable remote code execution and compromise the confidentiality and integrity of the N-central system. The CVSS v4.0 assessment assigns high confidentiality and integrity impacts and low availability impact, with a base score of 8.7. Root-level execution and compromise of downstream managed endpoints are not established consequences of this vulnerability alone.

Mitigation

If you can’t patch tonight, do this now.

Keep unpatched on-premises N-central servers offline until the security update is installed. Restrict administrative interfaces to trusted networks using VPN access or IP allowlisting rather than exposing them directly to the internet. Review authentication activity, administrator account creation, and deployed scripts or tasks for unauthorized changes. No vulnerability-specific configuration workaround is established.

Remediation

Patch, then assume compromise.

Upgrade N-central to 2026.4 Hotfix 2, build 2026.4.1.26, or a later supported release containing the fix. The CVE record identifies the fixed version boundary as 26.4.1. Update Agents and Probes to build 2026.4.1.26 or later as required by the security release, upgrading Agents before Probes to preserve communication compatibility. This hotfix resolves this CVE but does not address every separately disclosed N-central vulnerability.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-125878 exploited in the wild?
As of Nov 16, 2026, Mallory has no reports of CVE-2026-125878 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-125878?
As of Nov 16, 2026, Mallory has found no public exploit for CVE-2026-125878.
Is there a patch for CVE-2026-125878?
Upgrade N-central to 2026.4 Hotfix 2, build 2026.4.1.26, or a later supported release containing the fix. The CVE record identifies the fixed version boundary as 26.4.1.
How severe is CVE-2026-125878?
CVE-2026-125878 has a CVSS v4 score of 8.7 (High) and an EPSS score of 0.41% (36th percentile) as of Nov 16, 2026.
Activity feed

Recent activity

17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+11 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.