# CVE-2026-76055: Command injection in blackduck-c-cpp

> An attacker can execute arbitrary OS commands by placing files with malicious names in the scanned directory, affecting Black Duck C/C++ users.

- **Severity:** High 7.5 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/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 Aug 2026
- **Updated:** 24 Aug 2026
- **Also known as:** GHSA-xgr7-5g33-wgpv

## What is CVE-2026-76055?

CVE-2026-76055 is a high-severity command injection vulnerability in blackduck-c-cpp, published on 24 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper Neutralization of Special Elements used in an OS Command in the package manager component of Black Duck blackduck-c-cpp before 3.0.7 allows an actor able to create a file within the scanned build directory to execute operating system commands as the account running the scan.

Filesystem paths encountered while traversing the scanned directory are interpolated into command strings that are executed through a shell without quoting or escaping, so shell metacharacters within those paths are interpreted rather than treated as literal text. No control over the build command or the tool's configuration is required.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-76055 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76055 is a high-severity command injection vulnerability in blackduck-c-cpp, published on 24 Aug 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-2026-76055 in the wild and no public exploit code.

Affected product: blackduck-c-cpp. 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-76055/ (Markdown: https://insights.sbomify.com/CVE-2026-76055/index.md)
```

## Sources

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

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