CVE-2026-55103

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

GHSA-jw39-rch6-mhwf ↗EUVD-2026-102202 ↗

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.
discourse discourse-activity-pub
fixed in > 3d5d6e7
CWE-345 Insufficient Verification of Data Authenticity
ETK-2026-1838Zero's internal tracking ID, independent of the CVE number., permanent identifier
3d 10h 57msince last run
58mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+59h37m
0
+2h
+4h
+6h
+8h
+10h

description

Affected discourse-activity-pub versions do not sufficiently validate the relationship between an inbound ActivityPub request signer, the claimed actor, and the referenced federated post. A remote attacker able to submit signed ActivityPub requests may edit, delete, or reply to federated posts without the expected permissions.

mitigation

Upgrade discourse-activity-pub to > 3d5d6e7 or later.

fixed in > 3d5d6e7

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.20%9th percentile
agent run time
58m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-15 17:05Z
Δ 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-15 17:05Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1838",
  "cve_id": "CVE-2026-55103",
  "display_id": "CVE-2026-55103",
  "ghsa_id": "GHSA-jw39-rch6-mhwf",
  "euvd_id": "EUVD-2026-102202",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Actor authorization bypass in discourse-activity-pub",
  "summary": "Affected discourse-activity-pub versions do not sufficiently validate the relationship between an inbound ActivityPub request signer, the claimed actor, and the referenced federated post. A remote attacker able to submit signed ActivityPub requests may edit, delete, or reply to federated posts without the expected permissions.",
  "mitigation": "Upgrade discourse-activity-pub to > 3d5d6e7 or later.",
  "vendor": "discourse",
  "product": "discourse-activity-pub",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 3d5d6e7"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "> 3d5d6e7"
      ],
      "package_name": "discourse-activity-pub",
      "purl": null
    }
  ],
  "cwes": [
    345
  ],
  "cvss_score": 8.6,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N",
  "epss_score": 0.002,
  "epss_percentile": 0.0928,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 58.06254081666667,
  "t0_at": "2026-10-15T17:05:41.414000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-15T17:05:41.414000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-15T17:05:41.414000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-55103"
    }
  }
}

published 2026-10-17 03:27Z
last change 2026-10-21 14:33Z

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.