CVE-2026-84236

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

GHSA-35p8-f7rp-g3wf ↗EUVD-2026-130737 ↗

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.
IBM Guardium Data Protection 12.2
ETK-2026-4971Zero's internal tracking ID, independent of the CVE number., permanent identifier
10h 56msince last run
10mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h59m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

IBM Guardium Data Protection 12.2 includes an insecure deserialization flaw in its SharePoint Tap MulticastTransceiver component. An unauthenticated remote attacker may be able to execute code if they can reach the affected component over the network.

mitigation

Restrict network access to the SharePoint Tap MulticastTransceiver component to trusted systems and networks. Monitor IBM guidance and apply a vendor-provided update when one is released.

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.
–
agent run time
10m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-19 21:03Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-19 21:03Z
    ghsa: trigger signal, started the run
  2. 2026-11-19 21:03Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4971",
  "cve_id": "CVE-2026-84236",
  "display_id": "CVE-2026-84236",
  "ghsa_id": "GHSA-35p8-f7rp-g3wf",
  "euvd_id": "EUVD-2026-130737",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Insecure deserialization in SharePoint Tap MulticastTransceiver",
  "summary": "IBM Guardium Data Protection 12.2 includes an insecure deserialization flaw in its SharePoint Tap MulticastTransceiver component. An unauthenticated remote attacker may be able to execute code if they can reach the affected component over the network.",
  "mitigation": "Restrict network access to the SharePoint Tap MulticastTransceiver component to trusted systems and networks. Monitor IBM guidance and apply a vendor-provided update when one is released.",
  "vendor": "IBM",
  "product": "Guardium Data Protection",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "12.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Guardium Data Protection",
      "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": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 10.302364733333333,
  "t0_at": "2026-11-19T21:03:09.874000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-19T21:03:09.874000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-19T21:03:09.874000+00:00",
      "url": "https://github.com/advisories/GHSA-35p8-f7rp-g3wf"
    }
  }
}

published 2026-11-19 21:51Z
last change 2026-11-20 08:30Z

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.