CVE-2026-76054
Black Duck C/C++ Sensitive Information Disclosure via Process Environment
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.
INFO
Published Date :
Aug. 24, 2026, 2:16 p.m.
Last Modified :
Aug. 24, 2026, 2:16 p.m.
Remotely Exploit :
No
Source :
BlackDuck
Affected Products
The following products are affected by CVE-2026-76054
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 4.0 | HIGH | 8cad7728-009c-4a3d-a95e-ca62e6ff8a0b |
Solution
- Rotate any exposed Black Duck API tokens.
- Upgrade Black Duck to a version that mitigates this vulnerability.
- Avoid supplying tokens via environment variables.
- Implement least privilege for build processes.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-76054 vulnerability anywhere in the article.