{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-29142 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-29142 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-29142 is a medium-severity vulnerability in SEPPmail Secure Email Gateway, published on 2 Apr 2026. 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-2026-29142 and fix it if it is affected.\n\nWhat it is: CVE-2026-29142 is a medium-severity vulnerability in SEPPmail Secure Email Gateway, published on 2 Apr 2026. 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-2026-29142 in the wild and no public exploit code.\n\nAffected product: SEPPmail Secure Email Gateway. 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-29142/ (Markdown: https://insights.sbomify.com/CVE-2026-29142/index.md)","id":"CVE-2026-29142","markdown":"https://insights.sbomify.com/CVE-2026-29142/index.md","name":"CVE-2026-29142","record":{"aliases":["GHSA-wph3-c8fm-q2v8"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Secure Email Gateway","requires_auth":"none","summary":"An attacker can forge GINA-encrypted emails due to plaintext exposure in the secure-mail.html file, bypassing email security controls.","user_interaction":"required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"NCSC.ch","cpe":[{"product":"secure_email_gateway","vendor":"seppmail"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-325","name":"Missing Cryptographic Step"}],"description":"SEPPmail Secure Email Gateway before version 15.0.3 allows an attacker to forge a GINA-encrypted email.","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":"Plaintext secure-mail.html","id":"CVE-2026-29142","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"S/MIME Decryption Impersonation","id":"CVE-2026-29143"},"packages":[],"prev":{"headline":"Bounded Subject Tag Sanitization","id":"CVE-2026-29141"},"products":["Secure Email Gateway"],"published":"2026-04-02","related":[{"cvss_score":7.8,"headline":"GINA State Confusion Account Takeover","id":"CVE-2026-29139","kev_date_added":null,"published":"2026-04-02"},{"cvss_score":7.8,"headline":"S/MIME Decryption Impersonation","id":"CVE-2026-29143","kev_date_added":null,"published":"2026-04-02"},{"cvss_score":7.8,"headline":"Unicode Subject Tags","id":"CVE-2026-29144","kev_date_added":null,"published":"2026-04-02"},{"cvss_score":7.7,"headline":"S/MIME Signature Additional Certificate","id":"CVE-2026-29140","kev_date_added":null,"published":"2026-04-02"},{"cvss_score":7.7,"headline":"Bounded Subject Tag Sanitization","id":"CVE-2026-29141","kev_date_added":null,"published":"2026-04-02"},{"cvss_score":6.3,"headline":"ESWmail-Verify Bypass","id":"CVE-2026-29132","kev_date_added":null,"published":"2026-04-02"},{"cvss_score":6.3,"headline":"PGP Decryption Sender LDAP Injection","id":"CVE-2026-29138","kev_date_added":null,"published":"2026-04-02"}],"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-04-02","vendors":["SEPPmail"]},"summary":"An attacker can forge GINA-encrypted emails due to plaintext exposure in the secure-mail.html file, bypassing email security controls.","url":"https://insights.sbomify.com/CVE-2026-29142/"}