# CVE-2026-108753: Agnaistic agnai through 1.0.555 Hard-Coded Credentials in self-host Docker Compose

> Hard-coded credentials in the self-hosted Docker Compose file allow unauthenticated attackers to gain admin access and modify server configuration.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/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:** 11 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-jvxj-gpfv-vg4v

## What is CVE-2026-108753?

CVE-2026-108753 is a critical vulnerability in agnaistic agnai, published on 11 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Agnaistic agnai through 1.0.555 contains a hard-coded credentials vulnerability in self-host.docker-compose.yml, which sets a fixed admin password and public JWT secret. Unauthenticated attackers can log in as admin or sign their own JWT with admin: true to impersonate users, reset passwords, and change server configuration.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2026-108753?


## How do I fix CVE-2026-108753?

No fix has been published for CVE-2026-108753 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-108753 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108753 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-108753 and fix it if it is affected.

What it is: CVE-2026-108753 is a critical vulnerability in agnaistic agnai, published on 11 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108753 exists.

Affected product: agnaistic agnai. 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-108753/ (Markdown: https://insights.sbomify.com/CVE-2026-108753/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-108753
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-108753
- OSV: https://osv.dev/vulnerability/CVE-2026-108753

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-108753/
Summaries are generated and may contain mistakes; the official description above is the record.