{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-2746 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-2746 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-2746 is a medium-severity vulnerability in SEPPmail Secure Email Gateway, published on 4 Mar 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-2746 and fix it if it is affected.\n\nWhat it is: CVE-2026-2746 is a medium-severity vulnerability in SEPPmail Secure Email Gateway, published on 4 Mar 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-2746 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-2746/ (Markdown: https://insights.sbomify.com/CVE-2026-2746/index.md)","id":"CVE-2026-2746","markdown":"https://insights.sbomify.com/CVE-2026-2746/index.md","name":"CVE-2026-2746","record":{"aliases":["GHSA-27h3-67h6-73p2"],"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":"Attackers can send forged emails that appear verified because the gateway fails to communicate PGP signature verification results to users.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"NCSC.ch","cpe":[{"product":"seppmail","vendor":"seppmail"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"SEPPmail Secure Email Gateway before version 15.0.1 does not properly communicate PGP signature verification results, leaving users unable to detect forged emails.","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":"Missing PGP Signature Tag","id":"CVE-2026-2746","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"PGP Mixed Plaintext and Encrypted Content","id":"CVE-2026-2747"},"packages":[],"prev":{"headline":"Authentication Bypass Using an Alternate Path or Channel in GitLab","id":"CVE-2026-2745"},"products":["Secure Email Gateway"],"published":"2026-03-04","related":[{"cvss_score":10,"headline":"SEPPmail User Web Interface Arbitrary File Write to RCE","id":"CVE-2026-2743","kev_date_added":null,"published":"2026-03-05"},{"cvss_score":9.5,"headline":"PDF Password CMDi","id":"CVE-2026-27441","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":9.3,"headline":"zip_attachments Path Traversal","id":"CVE-2026-27442","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":8.2,"headline":"S/MIME Decryption Tag Sanitization Bypass","id":"CVE-2026-27443","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":7.8,"headline":"Header Email Address Parsing","id":"CVE-2026-27444","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":7.8,"headline":"S/MIME Certificate Subject Whitespace","id":"CVE-2026-2748","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":6.9,"headline":"PGP Signature Reflection","id":"CVE-2026-27445","kev_date_added":null,"published":"2026-03-04"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-04","vendors":["SEPPmail"]},"summary":"Attackers can send forged emails that appear verified because the gateway fails to communicate PGP signature verification results to users.","url":"https://insights.sbomify.com/CVE-2026-2746/"}