Secuno
ENNL
Book demo

CVE-2025-32991

N2w Backup& Recovery remote code execution

9.0 CRITICALEPSS 0.34%
  1. Published25 Mar 2026

Description

In N2WS Backup & Recovery before 4.4.0, a two-step attack against the RESTful API results in remote code execution.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityHigh
Privileges requiredNone
User interactionNone
ScopeChanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected products

N2w Backup& Recovery< 4.3.2

Remediation

Fixed in
N2w Backup& Recovery≥ 4.3.2

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-1065008.5
Backstage is an open framework for building developer portals. Prior to 3.3.1, 3.4.1,…
CVE-2026-1064268.3
Race condition in Fonts in Google Chrome prior to 155.0.8059.39 allowed a remote…
CVE-2026-1063778.3
Race condition in Fonts in Google Chrome prior to 155.0.8059.39 allowed a remote…
CVE-2026-1062558.8
Race condition in V8 in Google Chrome prior to 155.0.8059.39 allowed a remote attacker…
CVE-2026-1062388.3
Race condition in Fonts in Google Chrome prior to 155.0.8059.39 allowed a remote…
CVE-2026-1062018.8
Race condition in V8 in Google Chrome prior to 155.0.8059.39 allowed a remote attacker…

Frequently asked

Is CVE-2025-32991 being actively exploited?

CVE-2025-32991 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.34%.

How severe is CVE-2025-32991?

CVE-2025-32991 has a CVSS 3.1 base score of 9.0, rated critical. EPSS estimates a 0.34% probability of exploitation.

Which products are affected by CVE-2025-32991?

Affected products include N2w Backup& Recovery.

How do I fix CVE-2025-32991?

Upgrade affected software to a fixed version, for example N2w Backup& Recovery 4.3.2 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-32991 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.