CVE-2026-113403

validatingZero is analyzing and reversing it now.

GHSA-pqfr-846f-jh32 ↗EUVD-2026-104815 ↗

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.
ArmorX Global Technology ArmorX Spam ArmorX Spam versions prior to 8.15.2-3.282.133-1.90.061
CWE-93 Improper Neutralization of CRLF Sequences ('CRLF Injection')
ETK-2026-2286Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 04mrunning
patch analysiscurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0hvalidating
0
+6h
+12h
+18h
+24h

description

ArmorX Spam is affected by an authenticated command-injection flaw in a parameter. An authenticated remote attacker may cause malicious code to be uploaded to the server through crafted input.

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

mitigation

Restrict access to ArmorX Spam to trusted authenticated users and limit its network exposure. No fixed version or vendor workaround is recorded in the available evidence.

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.
–
agent run time
1h 04m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-20 07:04Z
Δ 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:04Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2286",
  "cve_id": "CVE-2026-113403",
  "display_id": "CVE-2026-113403",
  "ghsa_id": "GHSA-pqfr-846f-jh32",
  "euvd_id": "EUVD-2026-104815",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Authenticated command injection in ArmorX Spam",
  "summary": "ArmorX Spam is affected by an authenticated command-injection flaw in a parameter. An authenticated remote attacker may cause malicious code to be uploaded to the server through crafted input.",
  "mitigation": "Restrict access to ArmorX Spam to trusted authenticated users and limit its network exposure. No fixed version or vendor workaround is recorded in the available evidence.",
  "vendor": "ArmorX Global Technology",
  "product": "ArmorX Spam",
  "affected": [
    {
      "affected_notes": [
        "ArmorX Spam versions prior to 8.15.2-3.282.133-1.90.061"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "ArmorX Spam",
      "purl": null
    }
  ],
  "cwes": [
    93
  ],
  "cvss_score": 7.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": "2026-10-20T07:04:25.847000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-20T07:04:25.847000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-20T07:04:25.847000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-113403"
    }
  }
}

published 2026-10-21 05:00Z
last change 2026-10-21 05:31Z

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.