← back to feed
CVE-2026-114424

CVE-2026-114424

validatingZero is analyzing and reversing it now.

GHSA-3c43-m234-72qw ↗EUVD-2026-116781 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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-95 Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')
ETK-2026-3476Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss9.2cna vendorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
–running
startingcurrent stage
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0mcheck available+40m
0
+10min
+20min
+30min

description

SEPPmail Secure Email Gateway releases before 15.1.1 are affected when active sender or recipient replacement rules use values derived from incoming messages. An unauthenticated remote sender may execute operating-system commands through the mail-processing worker when a configured rule matches.

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

mitigation

Upgrade SEPPmail Secure Email Gateway to version 15.1.1 or later. Until upgraded, disable affected sender and recipient replacement rules that process message-derived values.

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
17m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-04 08:28Z
Δ 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:28Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-114424

this entry in the feed

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

{
  "etk_id": "ETK-2026-3476",
  "cve_id": "CVE-2026-114424",
  "display_id": "CVE-2026-114424",
  "ghsa_id": "GHSA-3c43-m234-72qw",
  "euvd_id": "EUVD-2026-116781",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Unauthenticated code injection in SEPPmail Secure Email Gateway",
  "summary": "SEPPmail Secure Email Gateway releases before 15.1.1 are affected when active sender or recipient replacement rules use values derived from incoming messages. An unauthenticated remote sender may execute operating-system commands through the mail-processing worker when a configured rule matches.",
  "mitigation": "Upgrade SEPPmail Secure Email Gateway to version 15.1.1 or later. Until upgraded, disable affected sender and recipient replacement rules that process message-derived values.",
  "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": [
    95
  ],
  "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": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 16.890595216666668,
  "t0_at": "2026-11-04T08:28:20.412000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-04T09:07:55.328886+00:00",
      "days": 0.027487463958333333,
      "is_lower_bound": false,
      "measured_at": "2026-11-04T08:28:20.412000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-04T08:28:20.412000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-04T08:28:20.412000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-114424"
    }
  }
}

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.