{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-76054 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-76054 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-76054 is a high-severity vulnerability in blackduck-c-cpp, published on 24 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-76054 and fix it if it is affected.\n\nWhat it is: CVE-2026-76054 is a high-severity vulnerability in blackduck-c-cpp, published on 24 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-76054 in the wild and no public exploit code.\n\nAffected product: blackduck-c-cpp. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-76054/ (Markdown: https://insights.sbomify.com/CVE-2026-76054/index.md)","id":"CVE-2026-76054","markdown":"https://insights.sbomify.com/CVE-2026-76054/index.md","name":"CVE-2026-76054","record":{"aliases":["GHSA-95m4-f2x3-273j"],"analysis":{"component_type":"developer_tool","fix_type":"configuration_change","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Black Duck C/C++ scanner","requires_auth":"none","summary":"Attackers with build execution access can steal Black Duck API tokens from environment variables, requiring token rotation and secure token handling.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"BlackDuck","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-214","name":"Invocation of Process Using Visible Sensitive Information"}],"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.\n\nUpgrading does not remediate prior disclosure; any token supplied to an affected version through an environment variable should be rotated.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in blackduck-c-cpp","id":"CVE-2026-76054","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Command injection in blackduck-c-cpp","id":"CVE-2026-76055"},"packages":[],"prev":{"headline":"TranslatePress \u003c= 3.3.3 - Unauthenticated Stored Cross-Site Scripting via Comment Noise-Key Injection into HTML Parser","id":"CVE-2026-76053"},"products":["blackduck-c-cpp"],"published":"2026-08-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-24","vendors":["Black Duck"]},"summary":"Attackers with build execution access can steal Black Duck API tokens from environment variables, requiring token rotation and secure token handling.","url":"https://insights.sbomify.com/CVE-2026-76054/"}