CVE-2026-71883

validatedZero produced an exploit or a check.

GHSA-f5wg-4mfp-h458 ↗EUVD-2026-91992 ↗

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-LTS-JAVA >= 2.73.4, < 2.73.13
fixed in 2.73.13
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
ETK-2026-441, permanent identifier
+2h30mTTV
18mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+2h30magent stopped
0
+1h
+2h

description

bcprov-lts8on versions before 2.73.13 can expose encryption key material when using affected one-shot native cipher operations. An attacker able to trigger an application to encrypt into the same array used for its key may cause the application to store or send that key instead of ciphertext, on JVMs that copy JNI arrays.

mitigation

Upgrade bcprov-lts8on to version 2.73.13 or later. Until upgraded, do not use a key, IV, or authenticated-data array as an encryption output buffer; use separate buffers or unaffected cipher paths.

fixed in 2.73.13

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-441",
  "cve_id": "CVE-2026-71883",
  "display_id": "CVE-2026-71883",
  "ghsa_id": "GHSA-f5wg-4mfp-h458",
  "euvd_id": "EUVD-2026-91992",
  "status": "published",
  "anchor_state": "anchored",
  "title": "In-place encryption key disclosure in bcprov-lts8on",
  "summary": "bcprov-lts8on versions before 2.73.13 can expose encryption key material when using affected one-shot native cipher operations. An attacker able to trigger an application to encrypt into the same array used for its key may cause the application to store or send that key instead of ciphertext, on JVMs that copy JNI arrays.",
  "mitigation": "Upgrade bcprov-lts8on to version 2.73.13 or later. Until upgraded, do not use a key, IV, or authenticated-data array as an encryption output buffer; use separate buffers or unaffected cipher paths.",
  "vendor": "Legion of the Bouncy Castle Inc.",
  "product": "BC-LTS-JAVA",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2.73.4, < 2.73.13"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.73.13"
      ],
      "package_name": "bcprov-lts8on",
      "purl": null
    }
  ],
  "cwes": [
    200
  ],
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/U:Amber",
  "epss_score": 0.0025,
  "epss_percentile": 0.1575,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "mechanism_verified",
  "exploit": false,
  "pipeline_minutes": 17.965651266666665,
  "t0_at": "2026-10-03T08:38:18.749000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-03T11:08:04.707197+00:00",
      "days": 0.10400414579861111,
      "is_lower_bound": false,
      "measured_at": "2026-10-03T08:38:18.749000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-03T08:38:18.749000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-03T08:38:18.749000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-71883"
    }
  }
}

published 2026-10-03 09:16Z
last change 2026-10-21 12:26Z

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.