CVE-2026-96940

validatedZero produced an exploit or a check.

GHSA-q9jh-jffv-9xvh ↗EUVD-2026-91771 ↗

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).+3.3dkevAttacks confirmed in the real world.
Microsoft Exchange Server 2016 Cumulative Update 23 >= 15.01.0.0, < 15.01.2507.075; >= 15.02.0.0, < 15.02.1544.048; >= 15.02.0.0, < 15.02.1748.053; >= 15.02.0.0, < 15.02.2562.053
fixed in 15.01.2507.075, 15.02.1544.048, 15.02.1748.053, 15.02.2562.053
CWE-1390 Weak Authentication
ETK-2026-369, permanent identifier
+8.3dTTV
21mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0dpublic poc+3.3dcheck available+8.3dagent stopped
0
+2d
+4d
+6d

description

Microsoft Exchange Server 2016 CU23, Exchange Server 2019 CU14 and CU15, and Exchange Server Subscription Edition RTM are affected. An attacker who can authenticate to a vulnerable server may elevate privileges through network access.

mitigation

Update Exchange Server 2016 CU23 to 15.01.2507.075; Exchange Server 2019 CU14 to 15.02.1544.048 or CU15 to 15.02.1748.053; and Exchange Server Subscription Edition RTM to 15.02.2562.053.

fixed in 15.01.2507.075, 15.02.1544.048, 15.02.1748.053, 15.02.2562.053

check
available
exploit
no
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.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.49%40th percentile
agent run time
21m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-02 19:06Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+3.3d
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual check: a technique exists and was validated, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-02 19:06Z
    cve_org: trigger signal, started the run
  2. 2026-10-05 16:21Z
    Microsoft Exchange Flaw Lets Authenticated Attackers Read Other Users' Mailboxes
  3. 2026-10-06 10:50Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-369",
  "cve_id": "CVE-2026-96940",
  "display_id": "CVE-2026-96940",
  "ghsa_id": "GHSA-q9jh-jffv-9xvh",
  "euvd_id": "EUVD-2026-91771",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authorization flaw in Microsoft Exchange Server",
  "summary": "Microsoft Exchange Server 2016 CU23, Exchange Server 2019 CU14 and CU15, and Exchange Server Subscription Edition RTM are affected. An attacker who can authenticate to a vulnerable server may elevate privileges through network access.",
  "mitigation": "Update Exchange Server 2016 CU23 to 15.01.2507.075; Exchange Server 2019 CU14 to 15.02.1544.048 or CU15 to 15.02.1748.053; and Exchange Server Subscription Edition RTM to 15.02.2562.053.",
  "vendor": "Microsoft",
  "product": "Microsoft Exchange Server 2016 Cumulative Update 23",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 15.01.0.0, < 15.01.2507.075"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "15.01.2507.075"
      ],
      "package_name": "Microsoft Exchange Server 2016 Cumulative Update 23",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 15.02.0.0, < 15.02.1544.048"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "15.02.1544.048"
      ],
      "package_name": "Microsoft Exchange Server 2019 Cumulative Update 14",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 15.02.0.0, < 15.02.1748.053"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "15.02.1748.053"
      ],
      "package_name": "Microsoft Exchange Server 2019 Cumulative Update 15",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 15.02.0.0, < 15.02.2562.053"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "15.02.2562.053"
      ],
      "package_name": "Microsoft Exchange Server Subscription Edition RTM",
      "purl": null
    }
  ],
  "cwes": [
    1390
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C",
  "epss_score": 0.0049,
  "epss_percentile": 0.4049,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 20.6714936,
  "t0_at": "2026-10-02T19:06:19.061000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-11T02:40:41.148694+00:00",
      "days": 8.31553342238426,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T19:06:19.061000+00:00",
      "url": null
    },
    "public_poc": {
      "at": "2026-10-06T01:37:25+00:00",
      "days": 3.2715965162037035,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T19:06:19.061000+00:00",
      "url": "https://github.com/HORKimhab/CVE-2026-96940"
    },
    "trigger_signal": {
      "at": "2026-10-02T19:06:19.061000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T19:06:19.061000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-96940"
    }
  }
}

published 2026-10-02 19:42Z
last change 2026-10-21 06:34Z

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.