# CVE-2025-11899: Flowring Technology｜Agentflow - Use of Hard-coded Cryptographic Key

> Hard-coded cryptographic keys allow attackers to generate valid verification tokens and log in as any user if they know a user ID.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Oct 2025
- **Updated:** 17 Oct 2025
- **Also known as:** GHSA-p79h-rmmr-jmr7

## What is CVE-2025-11899?

CVE-2025-11899 is a critical vulnerability in Flowring Technology Agentflow, published on 17 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2025-11899?


## How do I fix CVE-2025-11899?

No fix has been published for CVE-2025-11899 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-11899 being exploited?

There is no known exploitation of CVE-2025-11899 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11899 and fix it if it is affected.

What it is: CVE-2025-11899 is a critical vulnerability in Flowring Technology Agentflow, published on 17 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-11899 in the wild and no public exploit code.

Affected product: Flowring Technology Agentflow. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-11899/ (Markdown: https://insights.sbomify.com/CVE-2025-11899/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-11899
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-11899
- OSV: https://osv.dev/vulnerability/CVE-2025-11899

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-11899/
Summaries are generated and may contain mistakes; the official description above is the record.