CVE-2026-104383

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

GHSA-fw38-659r-v3m6 ↗EUVD-2026-111587 ↗

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.
EagleCloud Aquila <= 2.6.7.2
CWE-94 Improper Control of Generation of Code ('Code Injection')
ETK-2026-2832Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 50msince last run
15mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h29m
+2h
+4h
+6h
+8h
+10h
+12h

description

EagleCloud Aquila on-premises installations through 2.6.7.2 are affected in the Pigeon MFA service. An authenticated remote user may execute code on the affected system by exploiting an injection flaw.

mitigation

Restrict authenticated access to the Pigeon MFA service to trusted administrators and isolate it from untrusted networks. Monitor for vendor updates and apply a vendor-provided fix when one is released; no fixed version is recorded.

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.
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.
–
agent run time
15m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-28 04:21Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-10-28 04:21Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2832",
  "cve_id": "CVE-2026-104383",
  "display_id": "CVE-2026-104383",
  "ghsa_id": "GHSA-fw38-659r-v3m6",
  "euvd_id": "EUVD-2026-111587",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authenticated code injection in Aquila Pigeon MFA service",
  "summary": "EagleCloud Aquila on-premises installations through 2.6.7.2 are affected in the Pigeon MFA service. An authenticated remote user may execute code on the affected system by exploiting an injection flaw.",
  "mitigation": "Restrict authenticated access to the Pigeon MFA service to trusted administrators and isolate it from untrusted networks. Monitor for vendor updates and apply a vendor-provided fix when one is released; no fixed version is recorded.",
  "vendor": "EagleCloud",
  "product": "Aquila",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2.6.7.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Aquila",
      "purl": null
    }
  ],
  "cwes": [
    94
  ],
  "cvss_score": 9.4,
  "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:H/SI:H/SA:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 14.763784883333333,
  "t0_at": "2026-10-28T04:21:22.924000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-28T04:21:22.924000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-28T04:21:22.924000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-104383"
    }
  }
}

published 2026-10-28 04:35Z
last change 2026-10-28 06:14Z

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.