CVE-2026-96255

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

GHSA-gv9c-r7rv-4q3q ↗EUVD-2026-90520 ↗

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.
Payments for Hubtel < 1.0.2
fixed in 1.0.2
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
ETK-2026-524, permanent identifier
17d 12h 09msince last run
32mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+69h30m
0
+2h
+4h
+6h
+8h
+10h

description

Payments for Hubtel versions before 1.0.2 can expose a publicly accessible debug log containing payment gateway API credentials in plaintext. An unauthenticated attacker may obtain those credentials when the affected plugin's debug log is reachable.

mitigation

Upgrade Payments for Hubtel to version 1.0.2 or later. Restrict public access to any existing debug logs and rotate exposed payment gateway API credentials.

fixed in 1.0.2

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-524",
  "cve_id": "CVE-2026-96255",
  "display_id": "CVE-2026-96255",
  "ghsa_id": "GHSA-gv9c-r7rv-4q3q",
  "euvd_id": "EUVD-2026-90520",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Public debug log exposure in Payments for Hubtel",
  "summary": "Payments for Hubtel versions before 1.0.2 can expose a publicly accessible debug log containing payment gateway API credentials in plaintext. An unauthenticated attacker may obtain those credentials when the affected plugin's debug log is reachable.",
  "mitigation": "Upgrade Payments for Hubtel to version 1.0.2 or later. Restrict public access to any existing debug logs and rotate exposed payment gateway API credentials.",
  "vendor": null,
  "product": "Payments for Hubtel",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 1.0.2"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.0.2"
      ],
      "package_name": "Payments for Hubtel",
      "purl": null
    }
  ],
  "cwes": [
    200
  ],
  "cvss_score": 7.5,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
  "epss_score": 0.0026,
  "epss_percentile": 0.1619,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 31.579788866666668,
  "t0_at": "2026-10-01T06:00:25.989000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-01T06:00:25.989000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T06:00:25.989000+00:00",
      "url": "https://github.com/advisories/GHSA-gv9c-r7rv-4q3q"
    }
  }
}

published 2026-10-04 02:58Z
last change 2026-10-21 14:33Z

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.