Stop Admin Token Forgery in DataBuff ai-apm-web Before Attackers Gain Full Control
Unauthenticated attackers can forge administrative tokens using a hardcoded secret in DataBuff ai-apm-web versions through 0.1.10, granting full access to protected APIs.

Key points
- CVE-2026-111692 allows unauthenticated users to bypass authentication in DataBuff ai-apm-web.
- The flaw stems from a hardcoded HMAC secret used for signing JWT tokens in the application.
- Successful exploitation grants full administrative access to protected web API routes, including the Doris SQL query interface.
An unauthenticated attacker can forge administrative session tokens in DataBuff ai-apm-web, gaining full administrative access to protected application routes. This vulnerability, tracked as CVE-2026-111692, affects all versions of the software through 0.1.10. The National Vulnerability Database rates the issue as critical with a CVSS score of 9.3. Attackers do not need valid credentials to exploit this weakness. They can generate their own valid administrative tokens by leveraging a secret key that is permanently embedded within the application code. This bypasses standard authentication checks entirely.
The core mechanism involves the JwtTokenService component of the software. According to the NVD record, this service uses a hardcoded HMAC secret to sign JSON Web Tokens. An attacker can use this known secret, identified in the description as the default "dev-secret," to sign a custom payload. By setting the payload to include administrative privileges and a future expiration time, the attacker creates a token that the application accepts as legitimate. This allows immediate, full administrative access without interacting with the login process.
Scope of Administrative Access
Once the attacker possesses a forged token, they can access any protected route within the /webapi endpoints. The NVD description specifically highlights access to the Doris SQL query API. The vulnerability is classified under CWE-321, which relates to generation of error codes for cryptographic operations or improper use of cryptographic primitives. In this case, the improper use is the inclusion of a static secret in the codebase rather than using a secure, server-side stored key. The source material states that attackers gain full administrative access to these routes.
Affected Versions and Users
The vulnerability exists in DataBuff ai-apm-web versions up to and including 0.1.10. Any organization or individual running these versions is exposed to this authentication bypass. The NVD record does not mention a patched version. Small-business owners using this application for application performance monitoring should note that the flaw allows unauthenticated attackers to forge admin session tokens. The attacker needs only network access to the application to exploit the flaw. No prior authentication or user interaction is required to initiate the attack.
What to watch
Monitor network traffic for unusual activity originating from the Doris API endpoint. Look for administrative actions performed outside of normal business hours or by unknown user agents. Check server logs for new session tokens that were not issued through the standard login interface. If you detect unauthorized administrative access, isolate the affected system immediately. Watch for official announcements from DataBuff regarding a security update that addresses CVE-2026-111692.
What made it possible
This incident illustrates the risk of embedding cryptographic secrets directly into application source code. When developers hardcode keys for signing tokens, they inadvertently distribute the means to bypass authentication to anyone who can inspect the application or its dependencies. This technique serves the initial access stage of an intrusion, allowing attackers to gain privileged accounts without stealing credentials. Teams usually mitigate this by storing secrets in environment variables or secure vaults, ensuring that the signing key never leaves the protected server environment. Checking whether secrets are hardcoded is a standard security review step.
What to do and how to stay safe: DataBuff
- Verify if your DataBuff ai-apm-web installation is version 0.1.10 or earlier and restrict external network access to the application immediately.
- Monitor application logs for unauthorized administrative token usage, particularly those accessing the Doris SQL query API.
- Implement network segmentation to limit access to the /webapi endpoints to only trusted internal management systems.
Step-by-step guide: How Security Advisories Drive Patch Decisions and Reduce Risk
General security guidance from the Shell Bulletin newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is the CVSS score for CVE-2026-111692?
The National Vulnerability Database assigns a CVSS score of 9.3, rating the vulnerability as critical.
Which versions of DataBuff ai-apm-web are affected?
All versions of DataBuff ai-apm-web through 0.1.10 contain this authentication bypass vulnerability.
Is there a patch available for this vulnerability?
The source material does not state that a fix has been confirmed yet.



