EUVD-2026-64894
GHSA-95m4-f2x3-273j
Severity by source
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Local attack vector (code execution in build); no system-level privileges required; scope changes to Black Duck Hub; only confidentiality impact via token disclosure.
Primary rating from Vendor (BlackDuck).
CVSS VectorVendor: BlackDuck
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Lifecycle Timeline
3DescriptionCVE.org
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.
AnalysisAI
Token exfiltration in Black Duck blackduck-c-cpp 1.0.17 through 3.0.6 allows any actor with code execution inside a scanned project's build to read the Black Duck API token from the process environment inherited by scanning subprocesses. The token - when supplied via BLACKDUCK_API_TOKEN or BD_HUB_TOKEN - is passed in plaintext to child processes spawned during build capture and signature scanning, where it is observable by co-located code. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | The attacker must have the ability to execute arbitrary code within the scanned project's build environment - achieved, for example, through a malicious build script (Makefile target, CMake custom command), a compromised or malicious C/C++ dependency that runs code at build time, or a supply chain injection into the project's source tree. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 4.0 vector (AV:L/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:L) correctly identifies local access with low complexity, but AT:P (attack requirements present) is the critical gating condition: exploitation requires code execution inside the build environment, which is a non-trivial prerequisite in hardened CI/CD pipelines. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | A threat actor embeds a malicious rule in a project's Makefile or a compromised C/C++ dependency that, when executed during blackduck-c-cpp's build capture phase, reads /proc/self/environ (or calls getenv()) to extract the BLACKDUCK_API_TOKEN value and exfiltrates it to an attacker-controlled endpoint. With the stolen token, the attacker authenticates to the Black Duck Hub API, enumerates all scanned projects and their vulnerability reports, and potentially modifies scan results to suppress findings - undermining the integrity of the organization's SCA program. … |
| Remediation | Upgrade blackduck-c-cpp to a version beyond 3.0.6 per the vendor advisory at https://community.blackduck.com/s/article/Black-Duck-Product-Security-Advisory-CVE-2026-76054-CVE-2026-76055; the exact patched release number was not specified in the available data and should be verified against PyPI or the advisory. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Identify all deployed instances of Black Duck blackduck-c-cpp and determine which versions are in use; consult vendor advisory for patched version availability and begin credential rotation procedures. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
More in Blackduck C Cpp
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today