# CVE-2026-76054: Information disclosure in blackduck-c-cpp

> Attackers with build execution access can steal Black Duck API tokens from environment variables, requiring token rotation and secure token handling.

- **Severity:** High 7.1 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:L`)
- **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-95m4-f2x3-273j

## What is CVE-2026-76054?

CVE-2026-76054 is a high-severity 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

Invocation of Process Using Visible Sensitive Information in Black Duck blackduck-c-cpp 1.0.17 through 3.0.6 allows an actor able to execute code within the scanned project's build to obtain the Black Duck API token via the ambient process environment, which is inherited by subprocesses launched during build capture and signature scanning. This applies only where the token is supplied through the BLACKDUCK_API_TOKEN or BD_HUB_TOKEN environment variable.

Upgrading does not remediate prior disclosure; any token supplied to an affected version through an environment variable should be rotated.

Weakness: CWE-214 (Invocation of Process Using Visible Sensitive Information)

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


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

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

## Is CVE-2026-76054 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76054 is a high-severity 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-76054 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-76054/ (Markdown: https://insights.sbomify.com/CVE-2026-76054/index.md)
```

## Sources

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

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