# CVE-2025-32991: Race condition in n/a

> A race condition in the RESTful API allows remote attackers to execute arbitrary code on N2WS Backup & Recovery systems.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Mar 2026
- **Updated:** 25 Mar 2026
- **Also known as:** GHSA-7p72-hg7m-3627

## What is CVE-2025-32991?

CVE-2025-32991 is a critical vulnerability in n/a, published on 25 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2025-32991?

It affects 1 product.


Products: N2w Backup\& Recovery.

## How do I fix CVE-2025-32991?

No fix has been published for CVE-2025-32991 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-32991 being exploited?

There is no known exploitation of CVE-2025-32991 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-32991 and fix it if it is affected.

What it is: CVE-2025-32991 is a critical vulnerability in n/a, published on 25 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-32991 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-32991/ (Markdown: https://insights.sbomify.com/CVE-2025-32991/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-32991
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-32991
- OSV: https://osv.dev/vulnerability/CVE-2025-32991

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-32991/
Summaries are generated and may contain mistakes; the official description above is the record.