Vulnerability in SEPPmail Secure Email Gateway (CVE-2026-44127)
Summary
Vulnerability in SEPPmail Secure Email Gateway (CVE-2026-44127). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
SEPPmail Secure Email Gateway before version 15.0.4 contains an unauthenticated path traversal vulnerability in the identifier parameter of /api.app/attachment/preview that allows remote attackers to read arbitrary local files and trigger deletion of files in the targeted directory with the privileges of the api.app process.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44127 has been found in SEPPmail Secure Email Gateway.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "SEPPmail Secure Email Gateway CVE-2026-44127" on the vendor's site.
CVE-2026-44127 (SEPPmail Secure Email Gateway) — CWE-73
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-73) exists in SEPPmail Secure Email Gateway.
Check the vendor advisory for the affected versions of SEPPmail Secure Email Gateway.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで SEPPmail Secure Email Gateway を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web downloads.seppmail.com
- web nvd.nist.gov
- web github.com
- web vulnerability@ncsc.ch
- web labs.infoguard.ch