CVE-2026-104384

validatingZero is analyzing and reversing it now.

GHSA-wm5p-g46q-pcjq ↗EUVD-2026-111588 ↗

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-522 Insufficiently Protected Credentials
ETK-2026-2831Zero's internal tracking ID, independent of the CVE number., permanent identifier
6mrunning
patch analysiscurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0hvalidating
0
+1h
+2h

description

EagleCloud Aquila on-premises installations through 2.6.7.2 are affected in tunnel gateway and provisioning interfaces. A remote attacker without authentication may abuse the affected authentication handling to obtain elevated access to access keys, secret keys, and deployment secrets.

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

mitigation

Restrict tunnel gateway and provisioning interfaces to trusted administrative networks and remove public exposure. Monitor for a vendor update, and rotate potentially exposed access, secret, and deployment keys.

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
6m
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

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-28 04:21Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2831",
  "cve_id": "CVE-2026-104384",
  "display_id": "CVE-2026-104384",
  "ghsa_id": "GHSA-wm5p-g46q-pcjq",
  "euvd_id": "EUVD-2026-111588",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Insufficient credential protection in EagleCloud Aquila",
  "summary": "EagleCloud Aquila on-premises installations through 2.6.7.2 are affected in tunnel gateway and provisioning interfaces. A remote attacker without authentication may abuse the affected authentication handling to obtain elevated access to access keys, secret keys, and deployment secrets.",
  "mitigation": "Restrict tunnel gateway and provisioning interfaces to trusted administrative networks and remove public exposure. Monitor for a vendor update, and rotate potentially exposed access, secret, and deployment keys.",
  "vendor": "EagleCloud",
  "product": "Aquila",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2.6.7.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Aquila",
      "purl": null
    }
  ],
  "cwes": [
    522
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 14.3355901,
  "t0_at": "2026-10-28T04:21:29.717000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-28T04:21:29.717000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-28T04:21:29.717000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-104384"
    }
  }
}

published 2026-10-28 04:34Z
last change 2026-10-28 06:34Z

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.