{"answers":{"affected":"2 open source packages ship an affected version, including lettermint. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-27492 in the wild and no public exploit code.","fix":"Upgrade lettermint to 1.5.1 or later.","what":"CVE-2026-27492 is a medium-severity vulnerability in lettermint-node, published on 21 Feb 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-27492 and fix it if it is affected.\n\nWhat it is: CVE-2026-27492 is a medium-severity vulnerability in lettermint-node, published on 21 Feb 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-27492 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- lettermint (npm): affected all versions; fixed in 1.5.1\n- lettermint (npm): affected all versions; fixed in 1.5.1\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-27492/ (Markdown: https://insights.sbomify.com/CVE-2026-27492/index.md)","id":"CVE-2026-27492","markdown":"https://insights.sbomify.com/CVE-2026-27492/index.md","name":"CVE-2026-27492","record":{"aliases":["GHSA-49pc-8936-wvfp"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","other"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Node.js email SDK","requires_auth":"low_privilege","summary":"Reusing a client instance leaks previous email properties to unintended recipients, exposing sensitive data in transactional flows.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"lettermint","vendor":"lettermint"}],"cvss":{"score":4.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-488","name":"Exposure of Data Element to Wrong Session"}],"description":"Lettermint Node.js SDK is the official Node.js SDK for Lettermint. In versions 1.5.0 and below, email properties (such as to, subject, html, text, and attachments) are not reset between sends when a single client instance is reused across multiple .send() calls. This can cause properties from a previous send to leak into a subsequent one, potentially delivering content or recipient addresses to unintended parties. Applications sending emails to different recipients in sequence — such as transactional flows like password resets or notifications — are affected. This issue has been fixed in version 1.5.1.","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":"Lettermint Node.js SDK leaks email properties to unintended recipients when client instance is reused","id":"CVE-2026-27492","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"n8n has Unauthenticated Expression Evaluation via Form Node","id":"CVE-2026-27493"},"packages":[{"ecosystem":"npm","fixed":["1.5.1"],"introduced":["0"],"last_affected":[],"package":"lettermint","purl":null,"source":"GHSA-49pc-8936-wvfp"},{"ecosystem":"npm","fixed":["1.5.1"],"introduced":["0"],"last_affected":[],"package":"lettermint","purl":"pkg:npm/lettermint","source":"GHSA-49pc-8936-wvfp"}],"prev":{"headline":"Discourse has a bypass of official warnings messages by non-staff users","id":"CVE-2026-27491"},"products":["lettermint-node"],"published":"2026-02-21","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":"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-02-24","vendors":["lettermint"]},"summary":"Reusing a client instance leaks previous email properties to unintended recipients, exposing sensitive data in transactional flows.","url":"https://insights.sbomify.com/CVE-2026-27492/"}