{"answers":{"affected":"2 open source packages ship an affected version, including unleash-server.","exploited":"There is no known exploitation of CVE-2026-76909 in the wild and no public exploit code.","fix":"Upgrade unleash-server to 8.0.3 or later.","what":"CVE-2026-76909 is a low-severity cross-site scripting vulnerability in unleash, published on 22 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-76909 and fix it if it is affected.\n\nWhat it is: CVE-2026-76909 is a low-severity cross-site scripting vulnerability in unleash, published on 22 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-76909 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- unleash-server (npm): affected all versions; fixed in 8.0.3\n- unleash-server (npm): affected all versions; fixed in 8.0.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-2026-76909/ (Markdown: https://insights.sbomify.com/CVE-2026-76909/index.md)","id":"CVE-2026-76909","markdown":"https://insights.sbomify.com/CVE-2026-76909/index.md","name":"CVE-2026-76909","record":{"aliases":["GHSA-7hvx-28gp-mf6j","MINI-37xr-34vh-v5cg"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Feature management platform","requires_auth":"low_privilege","summary":"Attackers can inject HTML into approval emails, enabling phishing or tracking, affecting Unleash users with email notifications enabled.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.1,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Unleash is an open-source feature management platform. Prior to 8.0.3, the change-request approval email template at src/mailtemplates/requested-cr-approval/requested-cr-approval.html.mustache renders the user-controlled changeRequestTitle, requesterName, and requesterEmail values without HTML escaping, and sendRequestedCRApprovalEmail passes those values to Mustache rendering. A project member who can create a change request when approval emails are enabled can inject HTML into an approver's notification, allowing forged links, tracking content, or visually altered email content. This issue is fixed in version 8.0.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":"Unleash: CR-approval email renders user-controlled raw HTML","id":"CVE-2026-76909","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Unleash: Clone-feature lets a user copy a feature from a project they cannot read","id":"CVE-2026-76910"},"packages":[{"ecosystem":"npm","fixed":["8.0.3"],"introduced":["0"],"last_affected":[],"package":"unleash-server","purl":null,"source":"GHSA-7hvx-28gp-mf6j"},{"ecosystem":"npm","fixed":["8.0.3"],"introduced":["0"],"last_affected":[],"package":"unleash-server","purl":"pkg:npm/unleash-server","source":"GHSA-7hvx-28gp-mf6j"}],"prev":{"headline":"LaSuite Doc: Public Documents Enumeration","id":"CVE-2026-76907"},"products":["unleash"],"published":"2026-09-22","related":[],"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":"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-09-23","vendors":["Unleash"]},"summary":"Attackers can inject HTML into approval emails, enabling phishing or tracking, affecting Unleash users with email notifications enabled.","url":"https://insights.sbomify.com/CVE-2026-76909/"}