CVE-2026-63568

validatedZero produced an exploit or a check.

GHSA-mm8p-p4g9-932c ↗EUVD-2026-91219 ↗

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
CWE-770 Allocation of Resources Without Limits or Throttling
ETK-2026-319, permanent identifier
+1h53mTTV
15mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+1h53magent stopped
0
+1h
+2h

description

BouncyCastle.Cryptography before 2.7.0 can consume excessive CPU while validating password-based MACs in CMP messages or CRMF certificate requests. An unauthenticated remote attacker can cause denial of service if the application processes attacker-supplied requests and uses PKMacBuilder without an explicit iteration limit.

mitigation

Upgrade BouncyCastle.Cryptography to version 2.7.0 or later. Until upgraded, construct PKMacBuilder with an explicit maximum iteration count and restrict processing of untrusted CMP and CRMF requests where possible.

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.32%23rd percentile
agent run time
15m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-02 06:59Z
Δ 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 06:59Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-319",
  "cve_id": "CVE-2026-63568",
  "display_id": "CVE-2026-63568",
  "ghsa_id": "GHSA-mm8p-p4g9-932c",
  "euvd_id": "EUVD-2026-91219",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unbounded MAC iteration denial of service in BouncyCastle.Cryptography",
  "summary": "BouncyCastle.Cryptography before 2.7.0 can consume excessive CPU while validating password-based MACs in CMP messages or CRMF certificate requests. An unauthenticated remote attacker can cause denial of service if the application processes attacker-supplied requests and uses PKMacBuilder without an explicit iteration limit.",
  "mitigation": "Upgrade BouncyCastle.Cryptography to version 2.7.0 or later. Until upgraded, construct PKMacBuilder with an explicit maximum iteration count and restrict processing of untrusted CMP and CRMF requests where possible.",
  "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": [
    770
  ],
  "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",
  "epss_score": 0.0032,
  "epss_percentile": 0.2342,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "mechanism_verified",
  "exploit": false,
  "pipeline_minutes": 14.586429716666666,
  "t0_at": "2026-10-02T06:59:30.557000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-02T08:52:20.561666+00:00",
      "days": 0.07835653548611111,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T06:59:30.557000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-02T06:59:30.557000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T06:59:30.557000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-63568"
    }
  }
}

published 2026-10-02 08:37Z
last change 2026-10-21 18:49Z

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.