CVE-2026-113405

validatingZero is analyzing and reversing it now.

GHSA-84wj-3f7g-6wv4 ↗EUVD-2026-104824 ↗

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.
YS-infoware BA-Workflow < v3.6
fixed in v3.6
CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
ETK-2026-2137Zero's internal tracking ID, independent of the CVE number., permanent identifier
–running
startingcurrent stage
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0mcheck available+54m
0
+15min
+30min
+45min
+60min

description

YS-infoware BA-Workflow contains an SQL injection vulnerability. A remote user with valid authentication may manipulate database operations, potentially accessing, changing, or deleting application data.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Upgrade BA-Workflow to v3.6. Until all instances are updated, limit access to trusted authenticated users.

fixed in v3.6

check
building now
exploit
not yet
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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.37%29th percentile
agent run time
14m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-20 07: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

Run in progress: no artifact yet.

source signals

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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-2137",
  "cve_id": "CVE-2026-113405",
  "display_id": "CVE-2026-113405",
  "ghsa_id": "GHSA-84wj-3f7g-6wv4",
  "euvd_id": "EUVD-2026-104824",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "SQL injection in YS-infoware BA-Workflow",
  "summary": "YS-infoware BA-Workflow contains an SQL injection vulnerability. A remote user with valid authentication may manipulate database operations, potentially accessing, changing, or deleting application data.",
  "mitigation": "Upgrade BA-Workflow to v3.6. Until all instances are updated, limit access to trusted authenticated users.",
  "vendor": "YS-infoware",
  "product": "BA-Workflow",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < v3.6"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "v3.6"
      ],
      "package_name": "BA-Workflow",
      "purl": null
    }
  ],
  "cwes": [
    89
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0037,
  "epss_percentile": 0.2975,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 13.819329266666667,
  "t0_at": "2026-10-20T07:17:45.541000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-20T08:12:08.820200+00:00",
      "days": 0.037769435185185184,
      "is_lower_bound": false,
      "measured_at": "2026-10-20T07:17:45.541000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-20T07:17:45.541000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-20T07:17:45.541000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-113405"
    }
  }
}

published 2026-10-20 08:01Z
last change 2026-10-21 10:59Z

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.