CVE-2026-93941

waiting for further signalsZero needs more public information before it can validate it.

GHSA-66j7-cgjc-vfw6 ↗EUVD-2026-96189 ↗

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.
themerex group Edema <= 1.2.2.2
ETK-2026-1153Zero's internal tracking ID, independent of the CVE number., permanent identifier
9d 18h 44msince last run
27mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+27h59m
0
+2h
+4h
+6h
+8h
+10h

description

Edema versions through 1.2.2.2 are affected by unsafe deserialization that can permit object injection. The supplied advisory metadata indicates an attacker does not need authentication or user interaction to exploit the issue.

mitigation

Restrict access to affected Edema installations and disable or remove the component where feasible. Monitor for a vendor update and upgrade promptly when a fixed release is published.

check
no
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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.33%24th percentile
agent run time
27m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-10 07:00Z
Δ 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

Contextual: an exploit technique exists, 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-10 07:00Z
    ghsa: trigger signal, started the run
  2. 2026-10-10 07:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1153",
  "cve_id": "CVE-2026-93941",
  "display_id": "CVE-2026-93941",
  "ghsa_id": "GHSA-66j7-cgjc-vfw6",
  "euvd_id": "EUVD-2026-96189",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Object injection through unsafe deserialization in Edema",
  "summary": "Edema versions through 1.2.2.2 are affected by unsafe deserialization that can permit object injection. The supplied advisory metadata indicates an attacker does not need authentication or user interaction to exploit the issue.",
  "mitigation": "Restrict access to affected Edema installations and disable or remove the component where feasible. Monitor for a vendor update and upgrade promptly when a fixed release is published.",
  "vendor": "themerex group",
  "product": "Edema",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.2.2.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "edema",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0033,
  "epss_percentile": 0.2485,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 27.3770995,
  "t0_at": "2026-10-10T07:00:37.796000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-10T07:00:37.796000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-10T07:00:37.796000+00:00",
      "url": "https://github.com/advisories/GHSA-66j7-cgjc-vfw6"
    }
  }
}

published 2026-10-10 10:27Z
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.