Summary
CVE-2026-111692 is an authentication bypass vulnerability (CWE-321, Use of Hard-coded Cryptographic Key) in DataBuff ai-apm-web, versions through 0.1.10. Unauthenticated attackers can forge admin session tokens using a hardcoded HMAC secret in JwtTokenService. The CVE record rates it Critical (CVSS v4.0 score 9.3).
Technical details
- Root cause:
JwtTokenServicesigns session tokens with a default development HMAC secret (reported aschange-me-in-productioninJwtProperties.java). The secret is public, and neither the shipped Docker image configuration nor the compose file overrides it. - Trigger conditions: The deployment keeps the default signing secret. According to the researcher’s writeup, the token scheme is a custom HMAC-SHA256 construction. It has no issuer, audience or jti claims, no server-side session validation, and no role check in the interceptor.
- Attack vector: Network, with no authentication or user interaction. An attacker builds a payload with admin privileges and a far-future expiry, signs it with the known secret, and sends it as a Bearer token.
- Impact: Full administrative control over protected API routes, including the Doris SQL query function. The researcher also reports exposure of AI chat sessions, LLM provider settings and alert configuration. They also note a separate path through a default admin password.
Affected software
- DataBuff (databufflabs/databuff) ai-apm-web, versions 0 through 0.1.10
Severity
- CVSS v4.0: 9.3 (Critical),
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N - CVSS v3.1: 9.8 (Critical),
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: The CVE record lists no fixed version. Check the DataBuff repository for a release later than 0.1.10 and upgrade when one is available.
- If no patch is available:
- Do not expose ai-apm-web to the internet. Restrict access with firewall rules, a VPN or an authenticating reverse proxy.
- Override the JWT signing secret with a strong, unique random value. This is a general hardening step following the researcher’s recommendation to avoid default secrets. Vendor documentation does not confirm it.
- Change default admin credentials.
- Rotate any secrets or LLM provider keys stored in the platform. Review access logs for unexpected admin API or SQL query activity.

