CVE-2026-103604

validatedZero produced an exploit or a check.

GHSA-p48w-99f8-9598 ↗EUVD-2026-91234 ↗

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-csharp < 2.7.0
fixed in 2.7.0
ETK-2026-329, permanent identifier
+4h13mTTV
13mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+4h13magent stopped
0
+1h
+2h
+3h

description

bc-csharp versions before 2.7.0 can consume excessive CPU while formatting or comparing X.509 distinguished names. An unauthenticated remote party may cause a denial of service by supplying certificate-related data that the application subsequently renders, logs, displays, or compares.

mitigation

Upgrade bc-csharp to version 2.7.0 or later. Until upgraded, reduce exposure by avoiding string conversion or comparison of distinguished names from untrusted certificate-related inputs where practical.

fixed in 2.7.0

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.26%16th percentile
agent run time
13m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-02 07:11Z
Δ 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-02 07:11Z
    ghsa: trigger signal, started the run
  2. 2026-10-02 07:11Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-329",
  "cve_id": "CVE-2026-103604",
  "display_id": "CVE-2026-103604",
  "ghsa_id": "GHSA-p48w-99f8-9598",
  "euvd_id": "EUVD-2026-91234",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Quadratic X.509 name processing in bc-csharp",
  "summary": "bc-csharp versions before 2.7.0 can consume excessive CPU while formatting or comparing X.509 distinguished names. An unauthenticated remote party may cause a denial of service by supplying certificate-related data that the application subsequently renders, logs, displays, or compares.",
  "mitigation": "Upgrade bc-csharp to version 2.7.0 or later. Until upgraded, reduce exposure by avoiding string conversion or comparison of distinguished names from untrusted certificate-related inputs where practical.",
  "vendor": "Legion of the Bouncy Castle Inc.",
  "product": "bc-csharp",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2.7.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.7.0"
      ],
      "package_name": "BouncyCastle.Cryptography",
      "purl": null
    }
  ],
  "cwes": null,
  "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:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
  "epss_score": 0.0026,
  "epss_percentile": 0.1648,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "mechanism_verified",
  "exploit": false,
  "pipeline_minutes": 13.204829116666668,
  "t0_at": "2026-10-02T07:11:04.012000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-02T11:24:12.063003+00:00",
      "days": 0.17578762734953704,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T07:11:04.012000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-02T07:11:04.012000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T07:11:04.012000+00:00",
      "url": "https://github.com/advisories/GHSA-p48w-99f8-9598"
    }
  }
}

published 2026-10-02 11:10Z
last change 2026-10-21 16:09Z

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.