# CVE-2026-114425: Forged LFT metadata permits arbitrary file read and deletion

Status: published. Published: 2026-11-04. Updated: 2026-11-04.

SEPPmail Secure Email Gateway before 15.1.1 trusts a file path supplied in externally provided Large File Transfer attachment metadata. An unauthenticated remote sender can cause the mail-processing worker to disclose, move, or delete an accessible regular file when LFT is enabled and the message reaches an affected secure-mail processing path. The validated workers ran as root.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- SEPPmail AG / SEPPmail Secure Email Gateway (SEG): ≥ 0; < 15.1.1 (affected, custom). Source: CNA: NCSC.ch

## Severity and prioritization

- CVSS 4.0: 9.2 (critical); 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; source: CNA: NCSC.ch

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-73

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://docs.seppmail.com/en/20_revision-history.html (CNA: NCSC.ch)

## Provenance

- CNA: NCSC.ch: https://www.cve.org/CVERecord?id=CVE-2026-114425; retrieved 2026-11-04; source updated 2026-11-04

Revision: e518fb40cbbeb7cd28baae4ac6ca9df73001f65aae3e20da646e34fcd425f015

Canonical: https://y2.dev/cve/CVE-2026-114425

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.