How Agnaistic Agnai’s Hardcoded Credentials Enable Full Admin Takeover
A critical flaw in Agnaistic Agnai through version 1.0.555 exposes fixed admin passwords and JWT secrets, allowing unauthenticated attackers to seize full control of server configurations.
Key points
- CVE-2026-108753 carries a CVSS score of 9.3, classified as critical severity by the National Vulnerability Database.
- The vulnerability stems from hardcoded credentials in the self-host.docker-compose.yml configuration file.
- Attackers can impersonate administrators, reset user passwords, and alter server settings without prior authentication.
The National Vulnerability Database recorded CVE-2026-108753 as a critical security flaw affecting Agnaistic Agnai software. The issue involves hardcoded credentials within the application’s deployment configuration, specifically in the self-host.docker-compose.yml file. This misconfiguration sets a fixed administrative password and exposes a public JSON Web Token secret, creating a severe trust boundary violation for any instance using this file.
Root cause
The vulnerability is categorized under CWE-798, which denotes use of hardcoded credentials. According to the NVD record, the self-host.docker-compose.yml file contains a static admin password that does not change between installations. Additionally, the file includes a public JWT secret. Because these secrets are embedded directly in the configuration script, they are predictable and accessible to anyone who can view the file or the resulting container environment.
Attack path
Unauthenticated attackers can exploit this flaw by logging in with the known fixed admin password. Alternatively, they can use the exposed public JWT secret to sign their own tokens. By setting the admin claim to true in these forged tokens, attackers can impersonate legitimate administrators. This access allows them to reset user passwords and modify critical server configuration settings without triggering standard authentication checks.
Affected versions
The National Vulnerability Database identifies Agnaistic Agnai versions up to and including 1.0.555 as affected. The description explicitly states "through 1.0.555," indicating that all prior releases contain the vulnerable self-host.docker-compose.yml file. No later versions are mentioned in the source material as being patched or unaffected, so users should verify their specific release number against this upper bound.
Mitigation
- Review the self-host.docker-compose.yml file for any hardcoded passwords or JWT secrets.
- Replace the fixed admin password with a strong, unique credential generated per instance.
- Regenerate the JWT secret to ensure it is private and not publicly accessible.
- Restrict access to configuration files to prevent unauthorized viewing of sensitive data.
What to do and how to stay safe: Agnaistic
- Audit your deployment configurations for any hardcoded secrets or default passwords.
- Monitor server logs for unauthorized administrative actions or unexpected configuration changes.
- Implement strict file permissions on deployment scripts and container configuration files.
- Once the vendor provides an update, apply it immediately to resolve the exposure.
Step-by-step guide: Patch Testing Best Practices That Prevent Production Failures
General security guidance from the CloudSec Press newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is the CVSS score for CVE-2026-108753?
The National Vulnerability Database rates CVE-2026-108753 as critical with a CVSS score of 9.3.
Which file contains the vulnerable credentials?
The vulnerability is located in the self-host.docker-compose.yml file, which sets fixed admin passwords and JWT secrets.
Can unauthenticated users exploit this flaw?
Yes, unauthenticated attackers can log in as admin or sign their own JWTs to impersonate users and change settings.
