CVE-2026-104084

validatedZero produced an exploit or a check.

GHSA-3wv9-x54m-xfch ↗EUVD-2026-95890 ↗

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.0dkevAttacks confirmed in the real world.
Smartertools Smartermail >= 0, < Build 9777
fixed in Build 9777
ETK-2026-1100Zero's internal tracking ID, independent of the CVE number., permanent identifier
+6h40mTTV
40mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0dcheck available+0.3dagent stoppedpublic poc+3.0d
0
+1d
+2d

description

SmarterMail versions before build 9777 can continue honoring elevated role information stored in previously issued refresh tokens. An attacker with such a token may obtain an access token with the account's former administrative permissions after that account has been demoted. Exposure requires possession of a refresh token issued while the account still held the higher role.

mitigation

Upgrade SmarterMail to build 9777 or later. Until the upgrade is complete, invalidate existing refresh tokens and require reauthentication after administrative role changes where operationally possible.

fixed in Build 9777

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.
deterministic
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.27%18th percentile
agent run time
40m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-09 15:08Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+3.0d
Δ to kevAttacks confirmed in the real world.
–

outcome

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

source signals

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

  1. 2026-10-09 15:08Z
    ghsa: trigger signal, started the run
  2. 2026-10-09 15:08Z
  3. 2026-10-13 17:30Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1100",
  "cve_id": "CVE-2026-104084",
  "display_id": "CVE-2026-104084",
  "ghsa_id": "GHSA-3wv9-x54m-xfch",
  "euvd_id": "EUVD-2026-95890",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Stale refresh-token privilege escalation in SmarterMail",
  "summary": "SmarterMail versions before build 9777 can continue honoring elevated role information stored in previously issued refresh tokens. An attacker with such a token may obtain an access token with the account's former administrative permissions after that account has been demoted. Exposure requires possession of a refresh token issued while the account still held the higher role.",
  "mitigation": "Upgrade SmarterMail to build 9777 or later. Until the upgrade is complete, invalidate existing refresh tokens and require reauthentication after administrative role changes where operationally possible.",
  "vendor": "Smartertools",
  "product": "Smartermail",
  "affected": [
    {
      "affected_notes": [
        ">= 0, < Build 9777"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "Build 9777"
      ],
      "package_name": "Smartermail",
      "purl": null
    }
  ],
  "cwes": null,
  "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",
  "epss_score": 0.0027,
  "epss_percentile": 0.1862,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 39.8762619,
  "t0_at": "2026-10-09T15:08:23.453000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-09T21:48:23.846240+00:00",
      "days": 0.2777823291666667,
      "is_lower_bound": false,
      "measured_at": "2026-10-09T15:08:23.453000+00:00",
      "url": null
    },
    "public_poc": {
      "at": "2026-10-12T14:15:12+00:00",
      "days": 2.9630618865740743,
      "is_lower_bound": false,
      "measured_at": "2026-10-09T15:08:23.453000+00:00",
      "url": "https://github.com/eev4n/smartermail"
    },
    "trigger_signal": {
      "at": "2026-10-09T15:08:23.453000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-09T15:08:23.453000+00:00",
      "url": "https://github.com/advisories/GHSA-3wv9-x54m-xfch"
    }
  }
}

published 2026-10-09 21:08Z
last change 2026-10-21 05:31Z

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.