CVE-2026-85515

validatedZero produced an exploit or a check.

GHSA-8hgf-w73g-3x6v ↗EUVD-2026-91988 ↗

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.74, < 1.86; >= 2.73.0, < 2.73.13; >= 1.0.7, < 1.0.14; >= 2.0.7, < 2.0.14.1; >= 2.1.0, < 2.1.14
fixed in 1.86, 2.73.13, 1.0.14, 2.0.14.1, 2.1.14
CWE-354 Improper Validation of Integrity Check Value
ETK-2026-442, permanent identifier
+3h18mTTV
29mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+3h18magent stopped
0
+1h
+2h
+3h

description

bcpg versions before 1.86 can fail to report some truncated OpenPGP encrypted messages, potentially causing applications to accept incomplete data or lose trailing packet content. On the main BC-JAVA SEIPD v1 path, affected message shapes can also bypass integrity verification and yield modified plaintext; exploitation requires an application to process a suitably truncated encrypted message through an affected path.

mitigation

Upgrade bcpg to 1.86 or later, bcpg-lts8on to 2.73.13 or later, and bcpg-fips to 1.0.14, 2.0.14.1, or 2.1.14 or later for the corresponding release series. Until upgraded, reject truncated encrypted inputs and explicitly invoke integrity verification where the application API permits it.

fixed in 1.86, 2.73.13, 1.0.14, 2.0.14.1, 2.1.14

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-442",
  "cve_id": "CVE-2026-85515",
  "display_id": "CVE-2026-85515",
  "ghsa_id": "GHSA-8hgf-w73g-3x6v",
  "euvd_id": "EUVD-2026-91988",
  "status": "published",
  "anchor_state": "anchored",
  "title": "bcpg OpenPGP truncation validation failure",
  "summary": "bcpg versions before 1.86 can fail to report some truncated OpenPGP encrypted messages, potentially causing applications to accept incomplete data or lose trailing packet content. On the main BC-JAVA SEIPD v1 path, affected message shapes can also bypass integrity verification and yield modified plaintext; exploitation requires an application to process a suitably truncated encrypted message through an affected path.",
  "mitigation": "Upgrade bcpg to 1.86 or later, bcpg-lts8on to 2.73.13 or later, and bcpg-fips to 1.0.14, 2.0.14.1, or 2.1.14 or later for the corresponding release series. Until upgraded, reject truncated encrypted inputs and explicitly invoke integrity verification where the application API permits it.",
  "vendor": "Legion of the Bouncy Castle Inc.",
  "product": "BC-JAVA",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.74, < 1.86"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.86"
      ],
      "package_name": "bcpg",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2.73.0, < 2.73.13"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.73.13"
      ],
      "package_name": "bcpg-lts8on",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.0.7, < 1.0.14",
        ">= 2.0.7, < 2.0.14.1",
        ">= 2.1.0, < 2.1.14"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.0.14",
        "2.0.14.1",
        "2.1.14"
      ],
      "package_name": "bcpg-fips",
      "purl": null
    }
  ],
  "cwes": [
    354
  ],
  "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.0016,
  "epss_percentile": 0.044,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "mechanism_verified",
  "exploit": false,
  "pipeline_minutes": 28.56406623333333,
  "t0_at": "2026-10-03T08:05:16.553000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-03T11:22:51.200679+00:00",
      "days": 0.1372065703587963,
      "is_lower_bound": false,
      "measured_at": "2026-10-03T08:05:16.553000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-03T08:05:16.553000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-03T08:05:16.553000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-85515"
    }
  }
}

published 2026-10-03 09:22Z
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.