{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-40514 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-40514 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-40514 is a high-severity vulnerability in SmarterTools Inc. SmarterMail, published on 27 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-40514 and fix it if it is affected.\n\nWhat it is: CVE-2026-40514 is a high-severity vulnerability in SmarterTools Inc. SmarterMail, published on 27 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-40514 in the wild and no public exploit code.\n\nAffected product: SmarterTools Inc. SmarterMail. 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-40514/ (Markdown: https://insights.sbomify.com/CVE-2026-40514/index.md)","id":"CVE-2026-40514","markdown":"https://insights.sbomify.com/CVE-2026-40514/index.md","name":"CVE-2026-40514","record":{"aliases":["GHSA-j74m-34v4-rgqp"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SmarterMail email server","requires_auth":"none","summary":"An unauthenticated attacker can forge sharing tokens to access arbitrary emails and files due to weak random number generation in SmarterMail.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"smartermail","vendor":"smartertools"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-338","name":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)"}],"description":"SmarterTools SmarterMail builds prior to 9610 contain a cryptographic weakness in the file and email sharing endpoints that use DES-CBC encryption with keys and initialization vectors derived from System.Random seeded with insufficient entropy, reducing the seed space to approximately 19,000 possible values. An unauthenticated attacker can use the attachment download endpoint as an oracle to determine the seed in use and derive encryption keys and initialization vectors to forge sharing tokens for arbitrary emails, attachments, or file storage contents without prior access to the targeted content.","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":"SmarterTools SmarterMail \u003c Build 9610 Cryptographic Weakness via Weak RNG","id":"CVE-2026-40514","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"OpenHarness Permission Bypass via grep and glob root argument","id":"CVE-2026-40515"},"packages":[],"prev":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2026-40512"},"products":["SmarterMail"],"published":"2026-04-27","related":[{"cvss_score":10,"headline":"SmarterTools SmarterMail Unrestricted Upload of File with Dangerous Type","id":"CVE-2025-52691","kev_date_added":"2026-01-26","published":"2025-12-29"},{"cvss_score":9.3,"headline":"SmarterTools SmarterMail Missing Authentication for Critical Function","id":"CVE-2026-24423","kev_date_added":"2026-02-05","published":"2026-01-23"},{"cvss_score":9.3,"headline":"SmarterTools SmarterMail Authentication Bypass Using an Alternate Path or Channel","id":"CVE-2026-23760","kev_date_added":"2026-01-26","published":"2026-01-22"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2021-32234","kev_date_added":null,"published":"2021-11-17"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2019-7214","kev_date_added":null,"published":"2019-04-24"},{"cvss_score":8.7,"headline":"SmarterTools SmarterMail \u003c Build 9560 Server Local File Inclusion via the /api/v1/report/summary/{type} API","id":"CVE-2026-7807","kev_date_added":null,"published":"2026-05-08"}],"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-07-14","vendors":["SmarterTools Inc."]},"summary":"An unauthenticated attacker can forge sharing tokens to access arbitrary emails and files due to weak random number generation in SmarterMail.","url":"https://insights.sbomify.com/CVE-2026-40514/"}