Check out the latest research from IONIX: NEW! State of the WAF Report

New CVE Detected

CVE-2026-111692 – Authentication Bypass via Hardcoded HMAC Secret – DataBuff ai-apm-web through 0.1.

Be the first to know when new zero-days emerge:

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: JwtTokenService signs session tokens with a default development HMAC secret (reported as change-me-in-production in JwtProperties.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.

References

Get a free Attack Surface scan to see if you’re exposed.

Get a free Attack Surface scan to see if you’re exposed.

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge