CVE-2026-93892

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

GHSA-5cw6-3p7p-5r38 ↗EUVD-2026-98084 ↗

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 TRIRIGA Application Platform >= 5.0.0, <= 5.0.8
ETK-2026-1447Zero's internal tracking ID, independent of the CVE number., permanent identifier
8d 04h 04msince last run
44mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h52m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

IBM TRIRIGA Application Platform versions 5.0.0 through 5.0.8 are affected by session tokens being included in HTML responses. A remote attacker with authenticated access may use the exposed tokens to obtain sensitive information.

mitigation

Apply IBM's update for this issue when a supported fixed release is confirmed; the supplied evidence does not identify a specific fixed version. Until then, restrict authenticated access to affected deployments and review responses and logs for unintended token disclosure.

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.28%19th percentile
agent run time
44m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-12 22:48Z
Δ 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-12 22:48Z
    ghsa: trigger signal, started the run
  2. 2026-10-12 22:48Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1447",
  "cve_id": "CVE-2026-93892",
  "display_id": "CVE-2026-93892",
  "ghsa_id": "GHSA-5cw6-3p7p-5r38",
  "euvd_id": "EUVD-2026-98084",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Session token exposure in IBM TRIRIGA Application Platform",
  "summary": "IBM TRIRIGA Application Platform versions 5.0.0 through 5.0.8 are affected by session tokens being included in HTML responses. A remote attacker with authenticated access may use the exposed tokens to obtain sensitive information.",
  "mitigation": "Apply IBM's update for this issue when a supported fixed release is confirmed; the supplied evidence does not identify a specific fixed version. Until then, restrict authenticated access to affected deployments and review responses and logs for unintended token disclosure.",
  "vendor": "IBM",
  "product": "TRIRIGA Application Platform",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 5.0.0, <= 5.0.8"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "TRIRIGA Application Platform",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": 0.0028,
  "epss_percentile": 0.191,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 44.1007225,
  "t0_at": "2026-10-12T22:48:03.274000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-12T22:48:03.274000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-12T22:48:03.274000+00:00",
      "url": "https://github.com/advisories/GHSA-5cw6-3p7p-5r38"
    }
  }
}

published 2026-10-13 00:56Z
last change 2026-10-21 04:45Z

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.