CVE-2026-76054: CWE-214 Invocation of Process Using Visible Sensitive Information in Black Duck blackduck-c-cpp
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.
AI Analysis
Technical Summary
This vulnerability (CWE-214) involves the invocation of processes using visible sensitive information in Black Duck blackduck-c-cpp versions 1.0.17 through 3.0.6. Specifically, if the Black Duck API token is provided through the environment variables BLACKDUCK_API_TOKEN or BD_HUB_TOKEN, it can be accessed by any subprocesses spawned during the build capture and signature scanning phases. An attacker able to execute code within the build environment can leverage this to obtain the API token. The vulnerability is fixed starting with version 3.0.7. However, upgrading does not mitigate any prior token disclosure, so token rotation is necessary if tokens were exposed.
Potential Impact
An attacker with the ability to execute code within the scanned project's build environment can obtain the Black Duck API token if it was supplied via environment variables. This token exposure could allow unauthorized access to Black Duck services or data associated with the token. The vulnerability does not escalate privileges but leaks sensitive credentials. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrade to blackduck-c-cpp version 3.0.7 or later to remediate the vulnerability. Since upgrading does not mitigate any prior token exposure, any API tokens supplied through environment variables to affected versions should be rotated immediately to prevent unauthorized access.
CVE-2026-76054: CWE-214 Invocation of Process Using Visible Sensitive Information in Black Duck blackduck-c-cpp
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.
CVSS v4.0
Score 7.1high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability (CWE-214) involves the invocation of processes using visible sensitive information in Black Duck blackduck-c-cpp versions 1.0.17 through 3.0.6. Specifically, if the Black Duck API token is provided through the environment variables BLACKDUCK_API_TOKEN or BD_HUB_TOKEN, it can be accessed by any subprocesses spawned during the build capture and signature scanning phases. An attacker able to execute code within the build environment can leverage this to obtain the API token. The vulnerability is fixed starting with version 3.0.7. However, upgrading does not mitigate any prior token disclosure, so token rotation is necessary if tokens were exposed.
Potential Impact
An attacker with the ability to execute code within the scanned project's build environment can obtain the Black Duck API token if it was supplied via environment variables. This token exposure could allow unauthorized access to Black Duck services or data associated with the token. The vulnerability does not escalate privileges but leaks sensitive credentials. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrade to blackduck-c-cpp version 3.0.7 or later to remediate the vulnerability. Since upgrading does not mitigate any prior token exposure, any API tokens supplied through environment variables to affected versions should be rotated immediately to prevent unauthorized access.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- BlackDuck
- Date Reserved
- 2026-08-18T20:17:15.954Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a8c53b1acd9273b49a6bf07
Added to database: 08/24/2026, 14:22:41 UTC
Last enriched: 08/24/2026, 14:37:14 UTC
Last updated: 08/24/2026, 15:32:47 UTC
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.