CVE-2025-11899: Flowring Technology Agentflow · Use of Hard-coded Cryptographic Key
Affects Flowring Technology AgentflowSource CVE Database V5
Not known to be exploited · CVSS 9.2 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Flowring Technology Agentflow | Affected
| Fixed in– |
AI-suggested
Since no official patches or updates are currently available, European organizations should implement immediate compensating controls. These include restricting network access to Agentflow services by implementing strict firewall rules and network segmentation to limit exposure to trusted hosts only. Organizations should enforce strong monitoring and logging of authentication attempts and anomalous activities related to Agentflow, enabling rapid detection of exploitation attempts. Employ multi-factor authentication (MFA) at the network or application layer where possible to add an additional barrier beyond the compromised cryptographic key. Conduct thorough audits of user accounts and privilege levels to minimize the impact of potential account compromise. Engage with Flowring Technology for timelines on patches and apply updates as soon as they are released. Consider temporary disabling or isolating Agentflow 4.0 instances if feasible until a fix is available. Educate security teams about this vulnerability and prepare incident response plans tailored to potential exploitation scenarios. Finally, review and enhance cryptographic key management policies to prevent similar issues in future deployments.
Description
Agentflow developed by Flowring has an Use of Hard-coded Cryptographic Key vulnerability, allowing unauthenticated remote attackers to exploit the fixed key to generate verification information, thereby logging into the system as any user. Attacker must first obtain an user ID in order to exploit this vulnerability.