CVE-2026-71888

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

GHSA-j453-27jp-4cph ↗EUVD-2026-91991 ↗

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.86; >= 1.70, < 1.86; >= 2.73.0, < 2.73.13; >= 1.0.0, < 1.0.13; >= 2.0.0, < 2.0.13; >= 2.1.0, < 2.1.13; >= 2.0.0, < 2.0.8; >= 2.1.0, < 2.1.8
fixed in 1.86, 2.73.13, 1.0.13, 2.0.13, 2.1.13, 2.0.8, 2.1.8
CWE-354 Improper Validation of Integrity Check Value
ETK-2026-438, permanent identifier
18d 01h 12msince last run
12mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+3h49m
0
+2h
+6h
+8h
+10h
+12h

description

Affected Bouncy Castle CMS streaming parsers can expose authenticated-attribute values that were not covered by the message integrity check. An attacker able to modify a CMS AuthenticatedData message in transit could influence authorization, routing, or labeling decisions if the receiving application relies on those attributes. The message content itself remains integrity-protected.

mitigation

Upgrade bcpkix and bcutil to 1.86 or later, or bcpkix-lts8on and bcutil-lts8on to 2.73.13 or later. For FIPS deployments, update bcpkix-fips to 1.0.13, 2.0.13, or 2.1.13 for the applicable branch, and bcutil-fips to 2.0.8 or 2.1.8 for the applicable branch.

fixed in 1.86, 2.73.13, 1.0.13, 2.0.13, 2.1.13, 2.0.8, 2.1.8

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.
–
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.11%1st percentile
agent run time
12m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-03 08:36Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-438",
  "cve_id": "CVE-2026-71888",
  "display_id": "CVE-2026-71888",
  "ghsa_id": "GHSA-j453-27jp-4cph",
  "euvd_id": "EUVD-2026-91991",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Bouncy Castle CMS authenticated-attribute integrity bypass",
  "summary": "Affected Bouncy Castle CMS streaming parsers can expose authenticated-attribute values that were not covered by the message integrity check. An attacker able to modify a CMS AuthenticatedData message in transit could influence authorization, routing, or labeling decisions if the receiving application relies on those attributes. The message content itself remains integrity-protected.",
  "mitigation": "Upgrade bcpkix and bcutil to 1.86 or later, or bcpkix-lts8on and bcutil-lts8on to 2.73.13 or later. For FIPS deployments, update bcpkix-fips to 1.0.13, 2.0.13, or 2.1.13 for the applicable branch, and bcutil-fips to 2.0.8 or 2.1.8 for the applicable branch.",
  "vendor": "Legion of the Bouncy Castle Inc.",
  "product": "BC-JAVA",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 1.86"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.86"
      ],
      "package_name": "bcpkix",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.70, < 1.86"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.86"
      ],
      "package_name": "bcutil",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2.73.0, < 2.73.13"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.73.13"
      ],
      "package_name": "bcpkix-lts8on",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2.73.0, < 2.73.13"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.73.13"
      ],
      "package_name": "bcutil-lts8on",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.0.0, < 1.0.13",
        ">= 2.0.0, < 2.0.13",
        ">= 2.1.0, < 2.1.13"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.0.13",
        "2.0.13",
        "2.1.13"
      ],
      "package_name": "bcpkix-fips",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2.0.0, < 2.0.8",
        ">= 2.1.0, < 2.1.8"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.0.8",
        "2.1.8"
      ],
      "package_name": "bcutil-fips",
      "purl": null
    }
  ],
  "cwes": [
    354
  ],
  "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.0011,
  "epss_percentile": 0.0131,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 11.87303895,
  "t0_at": "2026-10-03T08:36:12.960000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-03T08:36:12.960000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-03T08:36:12.960000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-71888"
    }
  }
}

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