CVE-2026-114426

validatingZero is analyzing and reversing it now.

GHSA-3hf5-9fwq-fwv2 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
SEPPmail AG SEPPmail Secure Email Gateway (SEG) < 15.1.1
fixed in 15.1.1
CWE-400 Uncontrolled Resource Consumption
ETK-2026-3475Zero's internal tracking ID, independent of the CVE number., permanent identifier
–running
startingcurrent stage
timeline
0 = cve.org publication
trigger signal (cve.org) +0h
0
+2h
+4h
+6h
+8h
+10h
+12h

description

SEPPmail Secure Email Gateway versions before 15.1.1 process v1 file-interface upload data before authenticating the caller and do not enforce an absolute request-size limit. An unauthenticated remote attacker can send concurrent or slow requests that consume worker capacity and temporary storage, disrupting service availability.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Upgrade SEPPmail Secure Email Gateway to version 15.1.1 or later. Restrict access to the v1 file interface to trusted networks until the upgrade is complete.

fixed in 15.1.1

check
building now
exploit
not yet
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
9m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-04 08:33Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Run in progress: no artifact yet.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-04 08:33Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-114426

{
  "etk_id": "ETK-2026-3475",
  "cve_id": "CVE-2026-114426",
  "display_id": "CVE-2026-114426",
  "ghsa_id": "GHSA-3hf5-9fwq-fwv2",
  "euvd_id": null,
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Pre-authentication resource exhaustion in SEPPmail Secure Email Gateway",
  "summary": "SEPPmail Secure Email Gateway versions before 15.1.1 process v1 file-interface upload data before authenticating the caller and do not enforce an absolute request-size limit. An unauthenticated remote attacker can send concurrent or slow requests that consume worker capacity and temporary storage, disrupting service availability.",
  "mitigation": "Upgrade SEPPmail Secure Email Gateway to version 15.1.1 or later. Restrict access to the v1 file interface to trusted networks until the upgrade is complete.",
  "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": [
    400
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/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.2505447,
  "t0_at": "2026-11-04T08:33:13.228000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-04T08:33:13.228000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-04T08:33:13.228000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-114426"
    }
  }
}

published 2026-11-04 08:50Z
last change 2026-11-04 09:52Z

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.