CVE-2026-76054
Received Received - Intake

Invocation of Process Using Visible Sensitive Information in Black Duck blackduck-c-cpp

Publication date: 2026-08-24

Last updated on: 2026-08-24

Assigner: Synopsys

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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-24
Last Modified
2026-08-24
Generated
2026-08-24
AI Q&A
2026-08-24
EPSS Evaluated
N/A
NVD
CVE-2026-76054
EUVD
EUVD-2026-64894

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
synopsys blackduck-c-cpp From 1.0.17 (inc) to 3.0.6 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-214 A process is invoked with sensitive command-line arguments, environment variables, or other elements that can be seen by other processes on the operating system.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves Black Duck blackduck-c-cpp versions 1.0.17 through 3.0.6 exposing the Black Duck API token via the ambient process environment. When the token is set through BLACKDUCK_API_TOKEN or BD_HUB_TOKEN environment variables, subprocesses launched during build capture and signature scanning can access it.

Detection Guidance

This vulnerability involves exposure of the Black Duck API token via environment variables during build processes. To detect it, inspect environment variables during build capture or signature scanning for BLACKDUCK_API_TOKEN or BD_HUB_TOKEN. Check process listings for subprocesses launched during builds to see if these tokens are visible.

Impact Analysis

An attacker with code execution in the build environment could obtain the Black Duck API token, potentially leading to unauthorized access to Black Duck services or data. This could result in data breaches or service misuse.

Compliance Impact

This vulnerability could potentially expose sensitive API tokens used by Black Duck during build processes. If exploited, it may lead to unauthorized access to project data, which could violate confidentiality requirements under GDPR and HIPAA. Organizations using affected versions must rotate tokens to mitigate risks.

Mitigation Strategies

Rotate any Black Duck API tokens supplied via BLACKDUCK_API_TOKEN or BD_HUB_TOKEN environment variables. Upgrade to a patched version of blackduck-c-cpp beyond 3.0.6. Ensure tokens are not passed through environment variables during build processes.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-76054. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart