CVE-2026-19494

validatedZero produced an exploit or a check.

GHSA-94g5-424c-59qf ↗EUVD-2026-95276 ↗

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.
IBM Security Verify Access >= 10.0, <= 10.0.9.2; >= 11.0, <= 11.0.3
ETK-2026-1037Zero's internal tracking ID, independent of the CVE number., permanent identifier
+7h17mTTV
46mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+7h17magent stopped
0
+2h
+4h
+6h
+8h

description

Security Verify Access 10.0 through 10.0.9.2 and Verify Identity Access 11.0 through 11.0.3 are affected by an improper-authentication issue. A remote authenticated attacker may bypass security restrictions.

mitigation

Restrict access to affected deployments to trusted, authorized users and review authentication and authorization controls. Monitor for and apply IBM-provided updates when they become available; no fixed version is recorded in the advisory.

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.29%19th percentile
agent run time
46m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-08 21:03Z
Δ 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 check: a technique exists and was validated, 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-08 21:03Z
    ghsa: trigger signal, started the run
  2. 2026-10-08 21:03Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1037",
  "cve_id": "CVE-2026-19494",
  "display_id": "CVE-2026-19494",
  "ghsa_id": "GHSA-94g5-424c-59qf",
  "euvd_id": "EUVD-2026-95276",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper authentication in Security Verify Access",
  "summary": "Security Verify Access 10.0 through 10.0.9.2 and Verify Identity Access 11.0 through 11.0.3 are affected by an improper-authentication issue. A remote authenticated attacker may bypass security restrictions.",
  "mitigation": "Restrict access to affected deployments to trusted, authorized users and review authentication and authorization controls. Monitor for and apply IBM-provided updates when they become available; no fixed version is recorded in the advisory.",
  "vendor": "IBM",
  "product": "Security Verify Access",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 10.0, <= 10.0.9.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Security Verify Access",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 11.0, <= 11.0.3"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Verify Identity Access",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 10.0, <= 10.0.9.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Security Verify Access Container",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 11.0, <= 11.0.3"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Verify Identity Access Container",
      "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.0029,
  "epss_percentile": 0.1996,
  "epss_asof": "2026-10-21",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 46.20285395,
  "t0_at": "2026-10-08T21:03:50.047000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-09T04:20:47.941074+00:00",
      "days": 0.30344784807870373,
      "is_lower_bound": false,
      "measured_at": "2026-10-08T21:03:50.047000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-08T21:03:50.047000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-08T21:03:50.047000+00:00",
      "url": "https://github.com/advisories/GHSA-94g5-424c-59qf"
    }
  }
}

published 2026-10-09 03:48Z
last change 2026-10-21 23: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.