API token disclosure via inherited subprocess environment
Published Aug 24, 2026 · Updated Aug 24, 2026
Information disclosure in Black Duck C/C++ Tool 1.0.17 through 3.0.6 allows local users to obtain its API token during scans. Build capture and signature scanning launch project-controlled subprocesses with the scanner's ambient environment, including BLACKDUCK_API_TOKEN or BD_HUB_TOKEN. The issue is reachable only when a token is supplied through either environment variable and untrusted build code executes; exposure grants that code the token's Black Duck permissions.
Summary
What happened
Information disclosure in Black Duck C/C++ Tool 1.0.17 through 3.0.6 allows local users to obtain its API token during scans. Build capture and signature scanning launch project-controlled subprocesses with the scanner's ambient environment, including BLACKDUCK_API_TOKEN or BD_HUB_TOKEN. The issue is reachable only when a token is supplied through either environment variable and untrusted build code executes; exposure grants that code the token's Black Duck permissions.
The record
- CVE
- CVE-2026-76054
- Published
- Aug 24, 2026
- Updated
- Aug 24, 2026
- Vendor
- Black Duck Software
- Product
- Black Duck C/C++ Tool
- Classifications
- CWE-214, T1552
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 24, 2026CVE publishedPublication date reported by the CVE source.
- Aug 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.17 <3.0.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo