CVE-2026-74755

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

GHSA-9644-97m2-4fc3 ↗EUVD-2026-107180 ↗

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.
Apache Software Foundation Apache bRPC < 1.18.0
fixed in 1.18.0
ETK-2026-2342Zero's internal tracking ID, independent of the CVE number., permanent identifier
2msince last run
1h 06mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+7h03m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Apache bRPC releases before 1.18.0 can terminate unexpectedly while processing malformed mcpack2 data. A remote unauthenticated attacker can cause a denial of service when the server accepts nshead frames through the ubrpc mcpack2 adaptor. Standard open-source server configurations do not enable the affected protocol path by default.

mitigation

Upgrade Apache bRPC to version 1.18.0 or later. Until upgraded, disable or restrict server exposure of the nshead and ubrpc mcpack2 adaptor path.

fixed in 1.18.0

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.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
1h 06m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-21 11:45Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-2342",
  "cve_id": "CVE-2026-74755",
  "display_id": "CVE-2026-74755",
  "ghsa_id": "GHSA-9644-97m2-4fc3",
  "euvd_id": "EUVD-2026-107180",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Integer underflow in Apache bRPC mcpack2pb",
  "summary": "Apache bRPC releases before 1.18.0 can terminate unexpectedly while processing malformed mcpack2 data. A remote unauthenticated attacker can cause a denial of service when the server accepts nshead frames through the ubrpc mcpack2 adaptor. Standard open-source server configurations do not enable the affected protocol path by default.",
  "mitigation": "Upgrade Apache bRPC to version 1.18.0 or later. Until upgraded, disable or restrict server exposure of the nshead and ubrpc mcpack2 adaptor path.",
  "vendor": "Apache Software Foundation",
  "product": "Apache bRPC",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 1.18.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.18.0"
      ],
      "package_name": "apache/brpc",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 65.89313716666666,
  "t0_at": "2026-10-21T11:45:25.658000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-21T11:45:25.658000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-21T11:45:25.658000+00:00",
      "url": "https://github.com/advisories/GHSA-9644-97m2-4fc3"
    }
  }
}

published 2026-10-21 17:42Z
last change 2026-10-21 18:48Z

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.