CVE-2026-71890

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

GHSA-jc55-7frr-fv5r ↗EUVD-2026-92006 ↗

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.
Legion of the Bouncy Castle Inc. BC-JAVA >= 1.73, < 1.86
fixed in 1.86
CWE-863 Incorrect Authorization
ETK-2026-444, permanent identifier
18d 03h 50msince last run
10mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+4h45m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

bcmls versions before 1.86 incorrectly validate MLS external commits that request removal of a group member. An attacker with the group's public GroupInfo can cause another member to be removed and take over that member's ratchet-tree position.

mitigation

Upgrade bcmls to version 1.86 or later. Restrict distribution of public GroupInfo until all affected deployments are updated.

fixed in 1.86

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-444",
  "cve_id": "CVE-2026-71890",
  "display_id": "CVE-2026-71890",
  "ghsa_id": "GHSA-jc55-7frr-fv5r",
  "euvd_id": "EUVD-2026-92006",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper external commit validation in bcmls MLS",
  "summary": "bcmls versions before 1.86 incorrectly validate MLS external commits that request removal of a group member. An attacker with the group's public GroupInfo can cause another member to be removed and take over that member's ratchet-tree position.",
  "mitigation": "Upgrade bcmls to version 1.86 or later. Restrict distribution of public GroupInfo until all affected deployments are updated.",
  "vendor": "Legion of the Bouncy Castle Inc.",
  "product": "BC-JAVA",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.73, < 1.86"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.86"
      ],
      "package_name": "bcmls",
      "purl": null
    }
  ],
  "cwes": [
    863
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/U:Amber",
  "epss_score": 0.0025,
  "epss_percentile": 0.152,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 9.6902324,
  "t0_at": "2026-10-03T08:57:00.965000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-03T08:57:00.965000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-03T08:57:00.965000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-71890"
    }
  }
}

published 2026-10-03 09:47Z
last change 2026-10-21 16:15Z

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.