# CVE-2025-9120: RCE vulnerability has been discovered in OpenText™ Carbonite Safe Server Backup.

> An attacker can execute arbitrary code via code injection in OpenText Carbonite Safe Server Backup through an open port.

- **Severity:** High 8.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Feb 2026
- **Updated:** 24 Feb 2026
- **Also known as:** GHSA-7w2h-4285-9pwr

## What is CVE-2025-9120?

CVE-2025-9120 is a high-severity code injection vulnerability in OpenText™ Carbonite Safe Server Backup, published on 24 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper Control of Generation of Code ('Code Injection') vulnerability in OpenText™ Carbonite Safe Server Backup allows Code Injection. 

The vulnerability could be exploited through an open port, potentially allowing unauthorized access.

This issue affects Carbonite Safe Server Backup: through 6.8.3.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2025-9120 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9120 is a high-severity code injection vulnerability in OpenText™ Carbonite Safe Server Backup, published on 24 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-9120 in the wild and no public exploit code.

Affected product: OpenText™ Carbonite Safe Server Backup. 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-9120/ (Markdown: https://insights.sbomify.com/CVE-2025-9120/index.md)
```

## Sources

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

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