{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2026-56457 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-56457 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-56457 is a medium-severity vulnerability in HCLSoftware HCL DevOps Deploy / HCL Launch, published on 29 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-56457 and fix it if it is affected.\n\nWhat it is: CVE-2026-56457 is a medium-severity vulnerability in HCLSoftware HCL DevOps Deploy / HCL Launch, published on 29 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-56457 in the wild and no public exploit code.\n\nAffected product: HCLSoftware HCL DevOps Deploy / HCL Launch. 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-56457/ (Markdown: https://insights.sbomify.com/CVE-2026-56457/index.md)","id":"CVE-2026-56457","markdown":"https://insights.sbomify.com/CVE-2026-56457/index.md","name":"CVE-2026-56457","record":{"aliases":["GHSA-q6fr-25ph-fpvf"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"DevOps deployment tool","requires_auth":"low_privilege","summary":"Attackers with log access can obtain sensitive values from HCL DevOps Deploy output logs, requiring a patch to prevent data leakage.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"HCL","cpe":[{"product":"hcl_devops_deploy","vendor":"hcltechsw"},{"product":"hcl_launch","vendor":"hcltechsw"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"HCL DevOps Deploy / HCL Launch is susceptible to an exposure of sensitive information vulnerability in output logs. This exposure could allow an attacker with access to the logs to potentially obtain sensitive values related to that step.","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":"HCL DevOps Deploy / HCL Launch is susceptible to an exposure of sensitive information","id":"CVE-2026-56457","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"HCL DevOps Deploy is susceptible to a Permissive Cross-domain Security Policy with Untrusted Domains","id":"CVE-2026-56458"},"packages":[],"prev":{"headline":"HCL DFXAnalytics is affected by an Internal File Path Disclosure vulnerability.","id":"CVE-2026-56456"},"products":["HCL DevOps Deploy / HCL Launch"],"published":"2026-06-29","related":[{"cvss_score":7.2,"headline":"HCL DevOps Deploy / HCL Launch is susceptible to command injection vulnerability","id":"CVE-2025-0255","kev_date_added":null,"published":"2025-03-24"},{"cvss_score":6.5,"headline":"HCL DevOps Deploy / HCL Launch is susceptible to an Insertion of Sensitive Information Into Sent Data vulnerability","id":"CVE-2026-56460","kev_date_added":null,"published":"2026-07-09"},{"cvss_score":6.3,"headline":"HCL DevOps Deploy / HCL Launch is susceptible to unauthorized access to other services","id":"CVE-2025-0257","kev_date_added":null,"published":"2025-04-02"},{"cvss_score":6.3,"headline":"HCL DevOps Deploy / HCL Launch does not invalidate all session authentication cookies after logout","id":"CVE-2024-23558","kev_date_added":null,"published":"2024-04-15"},{"cvss_score":6.2,"headline":"HCL DevOps Deploy / HCL Launch is susceptible to sensitive information disclosure","id":"CVE-2026-56459","kev_date_added":null,"published":"2026-07-09"},{"cvss_score":6.2,"headline":"HCL DevOps Deploy / HCL Launch (UCD) may be vulnerable to sensitive information disclosure","id":"CVE-2024-23550","kev_date_added":null,"published":"2024-02-03"},{"cvss_score":6.1,"headline":"HCL DevOps Deploy / Launch is generating an obsolete HTTP header","id":"CVE-2024-23559","kev_date_added":null,"published":"2024-04-15"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-06-29","vendors":["HCLSoftware"]},"summary":"Attackers with log access can obtain sensitive values from HCL DevOps Deploy output logs, requiring a patch to prevent data leakage.","url":"https://insights.sbomify.com/CVE-2026-56457/"}