CVE-2026-56388

validatingZero is analyzing and reversing it now.

GHSA-57w6-4hvp-7m4g ↗

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
CWE-787 Out-of-bounds Write
ETK-2026-2317Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 11mrunning
differential validationcurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0mvalidating
0
+30min
+60min
+90min

description

Apache bRPC instances that enable Redis service can mishandle malformed Redis protocol input during command parsing. An unauthenticated remote client able to reach that service can trigger an out-of-bounds write and crash the bRPC process; the issue is encountered before command authentication or handling.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Upgrade apache/brpc to version 1.18.0. Until upgraded, disable the Redis service where it is not needed or restrict Redis protocol access to trusted clients.

fixed in 1.18.0

check
building now
exploit
not yet
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 11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-21 11:40Z
Δ 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

Run in progress: no artifact yet.

source signals

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

  1. 2026-10-21 11:40Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2317",
  "cve_id": "CVE-2026-56388",
  "display_id": "CVE-2026-56388",
  "ghsa_id": "GHSA-57w6-4hvp-7m4g",
  "euvd_id": null,
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Out-of-bounds write in Apache bRPC Redis command parsing",
  "summary": "Apache bRPC instances that enable Redis service can mishandle malformed Redis protocol input during command parsing. An unauthenticated remote client able to reach that service can trigger an out-of-bounds write and crash the bRPC process; the issue is encountered before command authentication or handling.",
  "mitigation": "Upgrade apache/brpc to version 1.18.0. Until upgraded, disable the Redis service where it is not needed or restrict Redis protocol access to trusted clients.",
  "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": [
    787
  ],
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": "2026-10-21T11:40:41.743000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-21T11:40:41.743000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-21T11:40:41.743000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-56388"
    }
  }
}

published 2026-10-21 12:03Z
last change 2026-10-21 13:12Z

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.