{"answers":{"affected":"2 open source packages ship an affected version, including semantic-release. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-26226 in the wild and no public exploit code.","fix":"Upgrade semantic-release to 17.2.3 or later.","what":"CVE-2020-26226 is a high-severity vulnerability in semantic-release, published on 18 Nov 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-26226 and fix it if it is affected.\n\nWhat it is: CVE-2020-26226 is a high-severity vulnerability in semantic-release, published on 18 Nov 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-26226 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- semantic-release (npm): affected all versions; fixed in 17.2.3\n- semantic-release (npm): affected all versions; fixed in 17.2.3\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-2020-26226/ (Markdown: https://insights.sbomify.com/CVE-2020-26226/index.md)","id":"CVE-2020-26226","markdown":"https://insights.sbomify.com/CVE-2020-26226/index.md","name":"CVE-2020-26226","record":{"aliases":["GHSA-r2j6-p67h-q639"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"npm semantic-release library","requires_auth":"none","summary":"Attackers can view sensitive secrets in logs if they contain URL-encoded characters, affecting users of the semantic-release npm package.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"semantic-release","vendor":"semantic-release_project"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"}],"description":"In the npm package semantic-release before version 17.2.3, secrets that would normally be masked by `semantic-release` can be accidentally disclosed if they contain characters that become encoded when included in a URL. Secrets that do not contain characters that become encoded when included in a URL are already masked properly. The issue is fixed in version 17.2.3.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Secret disclosure in semantic-release","id":"CVE-2020-26226","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":2,"n_references":2,"next":{"headline":"Cross-Site Scripting in Fluid view helpers","id":"CVE-2020-26227"},"packages":[{"ecosystem":"npm","fixed":["17.2.3"],"introduced":["0"],"last_affected":[],"package":"semantic-release","purl":null,"source":"GHSA-r2j6-p67h-q639"},{"ecosystem":"npm","fixed":["17.2.3"],"introduced":["0"],"last_affected":[],"package":"semantic-release","purl":"pkg:npm/semantic-release","source":"GHSA-r2j6-p67h-q639"}],"prev":{"headline":"Reflected XSS in PrestaShop Product Comments","id":"CVE-2020-26225"},"products":["semantic-release"],"published":"2020-11-18","related":[{"cvss_score":4.4,"headline":"Exposure of Sensitive Information to an Unauthorized Actor in semantic-release","id":"CVE-2022-31051","kev_date_added":null,"published":"2022-06-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["semantic-release"]},"summary":"Attackers can view sensitive secrets in logs if they contain URL-encoded characters, affecting users of the semantic-release npm package.","url":"https://insights.sbomify.com/CVE-2020-26226/"}