CVE-2026-104733

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

GHSA-339c-8fr4-g2w4 ↗EUVD-2026-91582 ↗

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.
ProcessOne ejabberd <= 26.04
ETK-2026-340, permanent identifier
18d 13h 41msince 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+14h34m
0
+2h
+4h
+6h
+8h
+10h

description

ProcessOne ejabberd versions through 26.04 are affected by insufficient validation of the authorization identity supplied through SASL PLAIN. An attacker able to use that mechanism may impersonate other users.

mitigation

Disable SASL PLAIN where operationally feasible, or limit access to the XMPP service to trusted clients and networks until an upstream fixed release is identified. Monitor ProcessOne ejabberd updates for a vendor-provided remediation.

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.22%11th percentile
agent run time
10m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-02 12:19Z
Δ 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-02 12:19Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-340",
  "cve_id": "CVE-2026-104733",
  "display_id": "CVE-2026-104733",
  "ghsa_id": "GHSA-339c-8fr4-g2w4",
  "euvd_id": "EUVD-2026-91582",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SASL PLAIN authorization identity validation flaw in ejabberd",
  "summary": "ProcessOne ejabberd versions through 26.04 are affected by insufficient validation of the authorization identity supplied through SASL PLAIN. An attacker able to use that mechanism may impersonate other users.",
  "mitigation": "Disable SASL PLAIN where operationally feasible, or limit access to the XMPP service to trusted clients and networks until an upstream fixed release is identified. Monitor ProcessOne ejabberd updates for a vendor-provided remediation.",
  "vendor": "ProcessOne",
  "product": "ejabberd",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 26.04"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "ejabberd",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.4,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:H/SC:H/SI:H/SA:H/E:P",
  "epss_score": 0.0022,
  "epss_percentile": 0.1126,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 10.073685783333334,
  "t0_at": "2026-10-02T12:19:10.635000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-02T12:19:10.635000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T12:19:10.635000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-104733"
    }
  }
}

published 2026-10-02 14:09Z
last change 2026-10-21 15:37Z

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.