# CVE-2026-86464: Hardcoded credentials in Eclipse aeriOS > Attackers can use default credentials to gain administrative access to the Identity Manager and database, compromising identity data and tokens. - **Severity:** Critical 9.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 8 Sep 2026 - **Updated:** 9 Sep 2026 - **Also known as:** GHSA-mvq6-76gr-6f6h ## What is CVE-2026-86464? CVE-2026-86464 is a critical vulnerability in Eclipse aeriOS, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description In the current development version of Eclipse aeriOS, for which no official release has yet been published, the Identity Manager (IdM) deployment included insecure default configurations and credentials for security-sensitive services. The Helm chart exposed the Keycloak service and its PostgreSQL backing database through Kubernetes NodePort services by default, while the Docker Compose deployment similarly exposed PostgreSQL on all network interfaces. The deployment included fixed default credentials for the Keycloak administrator and PostgreSQL database user, and the previous Helm chart configuration did not provide adequate secret management for these credentials. In addition, predefined application users with known credentials were provided for development and testing without sufficiently warning operators against their use in production environments. An attacker able to reach the exposed services could use the published default credentials to obtain administrative access to the Identity Manager or direct access to its database. This could allow unauthorized access to or modification of identity-management data, including users, roles, client credentials, sessions, and cryptographic material, and could enable the creation of privileged identities or tokens accepted by other aeriOS components. The issue has been addressed by generating a random Keycloak administrator password by default, managing Keycloak and PostgreSQL credentials through Kubernetes Secrets, and restricting PostgreSQL to an internal service in both the Helm chart and Docker Compose deployment. OpenLDAP is also restricted to an internal service. The predefined users intended for development and testing are retained, but the documentation now explicitly warns that their default credentials must not be used in production and that these users should be removed or their credentials changed after installation. Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-1392 (Use of Default Credentials), CWE-306 (Missing Authentication for Critical Functionality), CWE-1188 (Initialization of a Resource with an Insecure Default) ## Which versions are affected by CVE-2026-86464? ## How do I fix CVE-2026-86464? No fix has been published for CVE-2026-86464 yet. Limit exposure of the affected software until one is available. ## Is CVE-2026-86464 being exploited? There is no known exploitation of CVE-2026-86464 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-86464 and fix it if it is affected. What it is: CVE-2026-86464 is a critical vulnerability in Eclipse aeriOS, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-86464 in the wild and no public exploit code. Affected product: Eclipse aeriOS. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-86464/ (Markdown: https://insights.sbomify.com/CVE-2026-86464/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-86464 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-86464 - OSV: https://osv.dev/vulnerability/CVE-2026-86464 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-86464/ Summaries are generated and may contain mistakes; the official description above is the record.