CVE-2026-113404

validatingZero is analyzing and reversing it now.

GHSA-jppw-qwg2-2hgc ↗EUVD-2026-104808 ↗

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.
Uniong WebITR <= 2_1_0_34
CWE-502 Deserialization of Untrusted Data
ETK-2026-2126Zero's internal tracking ID, independent of the CVE number., permanent identifier
–running
startingcurrent stage
timeline
0 = cve.org publication
trigger signal (cve.org) +0h
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Uniong WebITR is affected by an insecure deserialization flaw involving an embedded cryptographic key. An authenticated remote attacker able to use that key may cause code to run on the server by submitting crafted serialized input.

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

mitigation

Restrict access to WebITR to trusted authenticated users and disable or isolate interfaces that accept serialized data where possible. Replace the embedded key and remove reliance on unsafe deserialization; no fixed WebITR version is recorded.

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.35%27th percentile
agent run time
20m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-20 06:24Z
Δ 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 06:24Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2126",
  "cve_id": "CVE-2026-113404",
  "display_id": "CVE-2026-113404",
  "ghsa_id": "GHSA-jppw-qwg2-2hgc",
  "euvd_id": "EUVD-2026-104808",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Insecure deserialization in Uniong WebITR",
  "summary": "Uniong WebITR is affected by an insecure deserialization flaw involving an embedded cryptographic key. An authenticated remote attacker able to use that key may cause code to run on the server by submitting crafted serialized input.",
  "mitigation": "Restrict access to WebITR to trusted authenticated users and disable or isolate interfaces that accept serialized data where possible. Replace the embedded key and remove reliance on unsafe deserialization; no fixed WebITR version is recorded.",
  "vendor": "Uniong",
  "product": "WebITR",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2_1_0_34"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "WebITR",
      "purl": null
    }
  ],
  "cwes": [
    502
  ],
  "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.0035,
  "epss_percentile": 0.2733,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 20.233271316666666,
  "t0_at": "2026-10-20T06:24:08.653000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-20T06:24:08.653000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-20T06:24:08.653000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-113404"
    }
  }
}

published 2026-10-20 06:51Z
last change 2026-10-21 11:18Z

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.