CVE-2026-6719

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

GHSA-mppm-vxf7-g245 ↗EUVD-2026-104528 ↗

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.
IBM Concert >= 1.0.0, <= 3.0.0
CWE-330 Use of Insufficiently Random Values
ETK-2026-2075Zero's internal tracking ID, independent of the CVE number., permanent identifier
10h 08msince last run
13mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+26h18m
0
+2h
+4h
+6h
+8h
+10h

description

IBM Concert versions 1.0 through 3.0.0 are affected by weak cryptographic randomness. An attacker may be able to decrypt highly sensitive information; the evidence does not establish additional exploitation preconditions.

mitigation

Restrict network and user access to Concert and limit exposure of sensitive information it processes. Obtain and apply IBM's remediation guidance or updated release when it is available; no fixed version is recorded in the advisory.

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.
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.42%34th percentile
agent run time
13m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-19 17:17Z
Δ 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

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-19 17:17Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2075",
  "cve_id": "CVE-2026-6719",
  "display_id": "CVE-2026-6719",
  "ghsa_id": "GHSA-mppm-vxf7-g245",
  "euvd_id": "EUVD-2026-104528",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Insufficiently random cryptographic values in IBM Concert",
  "summary": "IBM Concert versions 1.0 through 3.0.0 are affected by weak cryptographic randomness. An attacker may be able to decrypt highly sensitive information; the evidence does not establish additional exploitation preconditions.",
  "mitigation": "Restrict network and user access to Concert and limit exposure of sensitive information it processes. Obtain and apply IBM's remediation guidance or updated release when it is available; no fixed version is recorded in the advisory.",
  "vendor": "IBM",
  "product": "Concert",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.0.0, <= 3.0.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Concert",
      "purl": null
    }
  ],
  "cwes": [
    330
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
  "epss_score": 0.0042,
  "epss_percentile": 0.3451,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 13.3118248,
  "t0_at": "2026-10-19T17:17:08.395000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-19T17:17:08.395000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T17:17:08.395000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-6719"
    }
  }
}

published 2026-10-19 18:19Z
last change 2026-10-21 05:31Z

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.