Unauthenticated credential exposure in EagleCloud Aquila on-premises deployments

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-104384?

CVE-2026-104384 is a vulnerability classified as Insufficiently Protected Credentials, affecting Aquila (affected versions: ≤ 2.6.7.2). This vulnerability is rated High, with a CVSS score of 8.7. Current sources do not report this vulnerability as exploited.

Overview

Original source data

Insufficiently Protected Credentials in tunnel gateway and provisioning interfaces in EagleCloud Aquila versions through 2.6.7.2 on on-premises platforms allows unauthenticated remote attackers to escalate privileges via authentication abuse to access the access keys, secret keys, and deployment secrets.

Affected products and scope

  • EagleCloud Aquila on-premises is affected from version 0 through and including 2.6.7.2, using semver. The default status outside this product and version scope is unaffected.
  • Mandiant's advisory identifies Aquila on-premises 2.6.7.3 as the fixed version.
  • The record identifies only on-premises platforms. The status of other deployment models or release branches is not established by the available evidence.

Technical details

The flaw is classified as CWE-522, Insufficiently Protected Credentials. Mandiant attributes it to insecure API input handling in unauthenticated node provisioning and installation endpoints. When reachable, those endpoints can expose infrastructure access keys, secret keys, and deployment secrets. The affected components are the tunnel gateway and provisioning interfaces, and the advisory describes the vulnerable endpoint as fully exposed to the Internet. An attacker does not need prior authentication or user interaction, but the exact request parameters, response fields, and whether every deployment exposes the same credential material are not publicly specified.

Exploitability

  • The affected interfaces are reachable over the network when exposed by a deployment.
  • Exploitation requires no prior authentication and no user interaction.
  • Mandiant describes the vulnerable endpoint as fully exposed to the Internet and states that obtaining credentials requires no advanced techniques or complex sequence of steps.
  • The supplied record does not identify a specific public exploit, campaign, victim, or IOC. CISA enrichment records exploitation as none within that assessment, but this does not establish that every environment has been free of access attempts.

Technical impact

The flaw allows an unauthenticated attacker to obtain infrastructure credentials from affected interfaces. Those credentials may be used to bypass edge access proxies and impersonate legitimate administrative users, so consequences may extend beyond the Aquila host itself. The confirmed outcome is loss of credential confidentiality and possible escalation of infrastructure access; the record does not establish that an attacker can modify data or disrupt service through this issue. Actual exposure depends on the permissions of the disclosed keys and the systems that accept them.

Business impact

  • Exposed access keys, secret keys, and deployment secrets may enable unauthorized access to related infrastructure.
  • Mandiant states that leaked deployment keys can allow an attacker to bypass edge access proxies and impersonate legitimate administrative users.
  • Because the flaw requires no authentication and may affect public-facing endpoints, affected organizations may need an urgent upgrade, credential review, and replacement of exposed secrets.
  • The available evidence does not confirm a specific compromise, victim, or definite integrity or availability impact.

Remediation

  1. Upgrade Aquila on-premises to 2.6.7.3, which Mandiant's advisory identifies as fixing the issue. Do not assume that parallel release branches or other versions are covered without separate confirmation.
  2. Until the upgrade is complete, restrict untrusted access to the tunnel gateway, provisioning interfaces, and node provisioning or installation endpoints where operationally feasible. This is precautionary containment, not a substitute for the fix.
  3. If the deployment exposed affected endpoints or credentials may have been accessed, revoke and replace the relevant access keys, secret keys, and deployment secrets.
  4. After upgrading, verify the actual version on every node, recheck endpoint reachability, and review logs or audit records for use of old credentials.

Detection

  1. Inventory EagleCloud Aquila on-premises deployments and verify each node's version against the affected range and the published fixed release.
  2. Determine whether the tunnel gateway, provisioning interfaces, and node provisioning or installation endpoints are reachable from the Internet or other untrusted networks.
  3. Review API gateway, reverse proxy, and provisioning logs for unauthenticated requests to these endpoints, unexpected provisioning activity, or unusual access patterns. This is precautionary monitoring, not a vendor-confirmed indicator.
  4. Review audit records for systems that consume access keys, secret keys, or deployment secrets, looking for use from unexpected sources, times, or environments.
  5. If an affected endpoint was exposed or credentials may have been accessed, handle the event as a credential disclosure and investigate use of the exposed keys. The public sources do not provide specific log event names or IOCs.
Sources (12)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.