CVE-2026-71887

validatedZero produced an exploit or a check.

GHSA-cwf6-pghv-hq93 ↗EUVD-2026-91993 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.81, < 1.86
fixed in 1.86
CWE-347 Improper Verification of Cryptographic Signature
ETK-2026-440, permanent identifier
+3h02mTTV
18mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0hcheck available+3h02magent stopped
0
+1h
+2h

description

bcpg versions before 1.86 can associate a genuine OpenPGP subkey signature with an attacker-controlled certificate identity when applications use the high-level API. Exploitation requires a verifier to process a crafted certificate containing a public signing subkey and a message genuinely signed by that subkey; it does not enable creation of new signatures.

mitigation

Upgrade bcpg to version 1.86 or later. Until then, do not derive signer identity from an enclosing certificate when using the affected high-level API; make trust decisions using the signing subkey fingerprint.

fixed in 1.86

check
available
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.09%below the 1st percentile
agent run time
18m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-03 08:39Z
Δ 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

Mechanism verified: the exploit fired on the vulnerable build and stayed silent on the patched one, but the server it ran against was ours, so no check ships for it.

source signals

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

  1. 2026-10-03 08:39Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-440",
  "cve_id": "CVE-2026-71887",
  "display_id": "CVE-2026-71887",
  "ghsa_id": "GHSA-cwf6-pghv-hq93",
  "euvd_id": "EUVD-2026-91993",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper OpenPGP subkey binding validation in bcpg",
  "summary": "bcpg versions before 1.86 can associate a genuine OpenPGP subkey signature with an attacker-controlled certificate identity when applications use the high-level API. Exploitation requires a verifier to process a crafted certificate containing a public signing subkey and a message genuinely signed by that subkey; it does not enable creation of new signatures.",
  "mitigation": "Upgrade bcpg to version 1.86 or later. Until then, do not derive signer identity from an enclosing certificate when using the affected high-level API; make trust decisions using the signing subkey fingerprint.",
  "vendor": "Legion of the Bouncy Castle Inc.",
  "product": "BC-JAVA",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.81, < 1.86"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.86"
      ],
      "package_name": "bcpg",
      "purl": null
    }
  ],
  "cwes": [
    347
  ],
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/U:Amber",
  "epss_score": 0.0009,
  "epss_percentile": 0.0042,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "mechanism_verified",
  "exploit": false,
  "pipeline_minutes": 17.670085983333333,
  "t0_at": "2026-10-03T08:39:07.997000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-03T11:40:54.924593+00:00",
      "days": 0.12623758788194445,
      "is_lower_bound": false,
      "measured_at": "2026-10-03T08:39:07.997000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-03T08:39:07.997000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-03T08:39:07.997000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-71887"
    }
  }
}

published 2026-10-03 09:13Z
last change 2026-10-21 18: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.