Quick answers
- Is CVE-2026-92992 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92992 being exploited in the wild.
- How severe is CVE-2026-92992?
- Medium severity, with a CVSS score of 6.3, published 17 September 2026.
- Which products and versions are affected?
- Dromara Mayfly-Go 1.11.0 to 1.11.5.
- Is there a fix for CVE-2026-92992?
- A patch was published on 2026-09-17: Silent patch applied (commit 74bcb926eb4f5f94e7681144d7bf2168a0ec7cde) Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-92992 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-92992?
- Check whether you run Dromara Mayfly-Go at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a missing resource-level authorization flaw (CWE-862) in the AI Assistant's WebSocket endpoint (/api/ai/chat) affecting versions 1.11.0 through 1.11.5. The AI chat component fails to perform CanAccess checks before resolving and executing actions on machines and databases—a control that is consistently implemented in regular APIs. Attackers can supply arbitrary credential or database identifiers, and a command whitelist bypass allows unauthorized commands to execute if any token matches (e.g., "hostname; touch /tmp/x" bypasses approval). The approval flow is self-executed by the same session user, providing no additional authorization gate. Additionally, an OS command injection vulnerability (CWE-78) in machine-script template parameters allows authenticated users with only machine:script:run permission to inject shell commands. The patch (commit 74bcb926eb4f5f94e7681144d7bf2168a0ec7cde) was applied silently.
Affected products
- Dromara mayfly-go 1.11.0 to 1.11.5
Timeline
- 2026-08-21: disclosed: Vulnerability reported to vendor; PR #129 requesting private vulnerability reporting left unanswered for ~4 months
- 2026-09-17: disclosed: Public disclosure via NVD
- 2026-09-17: patched: Silent patch applied (commit 74bcb926eb4f5f94e7681144d7bf2168a0ec7cde)