CVE-2026-114425
waiting for further signalsZero needs more public information before it can validate it.GHSA-83v7-h64g-wr4c ↗EUVD-2026-116782 ↗
description
SEPPmail Secure Email Gateway versions before 15.1.1 mishandle file paths associated with Large File Transfer attachments. An unauthenticated sender may cause the mail-processing service to expose, relocate, or remove files it can access when LFT is enabled and a message is handled by the affected secure-mail path.
mitigation
Upgrade SEPPmail Secure Email Gateway to version 15.1.1. Until the upgrade is complete, disable Large File Transfer processing where operationally feasible.
fixed in 15.1.1
outcome
Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-11-04 08:29Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-114425
{ "etk_id": "ETK-2026-3477", "cve_id": "CVE-2026-114425", "display_id": "CVE-2026-114425", "ghsa_id": "GHSA-83v7-h64g-wr4c", "euvd_id": "EUVD-2026-116782", "status": "published", "anchor_state": "anchored", "title": "External file path control in SEPPmail Secure Email Gateway", "summary": "SEPPmail Secure Email Gateway versions before 15.1.1 mishandle file paths associated with Large File Transfer attachments. An unauthenticated sender may cause the mail-processing service to expose, relocate, or remove files it can access when LFT is enabled and a message is handled by the affected secure-mail path.", "mitigation": "Upgrade SEPPmail Secure Email Gateway to version 15.1.1. Until the upgrade is complete, disable Large File Transfer processing where operationally feasible.", "vendor": "SEPPmail AG", "product": "SEPPmail Secure Email Gateway (SEG)", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 0, < 15.1.1" ], "ecosystem": null, "fixed_versions": [ "15.1.1" ], "package_name": "SEPPmail Secure Email Gateway (SEG)", "purl": null } ], "cwes": [ 73 ], "cvss_score": 9.2, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N", "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": "contextual", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": 9.310686083333334, "t0_at": "2026-11-04T08:29:55.914000+00:00", "signals": { "trigger_signal": { "at": "2026-11-04T08:29:55.914000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-11-04T08:29:55.914000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-114425" } } }
published 2026-11-04 09:00Z
last change 2026-11-04 13:07Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.