# CVE-2026-32999: Code injection in Comet Backup

> Authenticated tenant administrators can execute arbitrary code on Comet Backup servers and connected devices due to insufficient character filtering in the signing module.

- **Severity:** Critical 9.1 (`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:** 28 May 2026
- **Updated:** 28 May 2026
- **Also known as:** GHSA-x8w2-9wjv-3hv6

## What is CVE-2026-32999?

CVE-2026-32999 is a critical code injection vulnerability in WebPros Comet Backup, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insufficient character filtering in backup agent signing module on Comet Backup server allows authenticated tenant administrator to execute an arbitrary code on behalf of a privileged user on the affected server and connected devices.

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

## Which versions are affected by CVE-2026-32999?


## How do I fix CVE-2026-32999?

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

## Is CVE-2026-32999 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32999 and fix it if it is affected.

What it is: CVE-2026-32999 is a critical code injection vulnerability in WebPros Comet Backup, published on 28 May 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-2026-32999 in the wild and no public exploit code.

Affected product: WebPros Comet 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-2026-32999/ (Markdown: https://insights.sbomify.com/CVE-2026-32999/index.md)
```

## Sources

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

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