# CVE-2025-9604: coze-studio aes.go hard-coded key

> Attackers can exploit hard-coded cryptographic keys in coze-studio to potentially decrypt sensitive data or bypass security controls.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Aug 2025
- **Updated:** 29 Aug 2025
- **Also known as:** GHSA-966j-x6rp-f492

## What is CVE-2025-9604?

CVE-2025-9604 is a medium-severity vulnerability in coze-studio, published on 29 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was identified in coze-studio up to 0.2.4. The impacted element is an unknown function of the file backend/domain/plugin/encrypt/aes.go. The manipulation of the argument AuthSecretKey/StateSecretKey/OAuthTokenSecretKey leads to use of hard-coded cryptographic key
 . It is possible to initiate the attack remotely. The attack is considered to have high complexity. The exploitability is regarded as difficult. To fix this issue, it is recommended to deploy a patch. The vendor replied to the GitHub issue (translated from simplified Chinese): "For scenarios requiring encryption, we will implement user-defined key management through configuration and optimize the use of encryption tools, such as random salt."

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

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


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

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

## Is CVE-2025-9604 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9604 is a medium-severity vulnerability in coze-studio, published on 29 Aug 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-9604 in the wild and no public exploit code.

Affected product: coze-studio. 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-9604/ (Markdown: https://insights.sbomify.com/CVE-2025-9604/index.md)
```

## Sources

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

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