# CVE-2025-15117: Dromara Sa-Token SaJdkSerializer.java ObjectInputStream.readObject deserialization

> Remote attackers can exploit unsafe deserialization in Sa-Token to potentially execute arbitrary code, though high complexity makes exploitation difficult.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Dec 2025
- **Updated:** 29 Dec 2025
- **Also known as:** GHSA-9786-pc79-p3v7

## What is CVE-2025-15117?

CVE-2025-15117 is a low-severity unsafe deserialization vulnerability in Dromara Sa-Token, published on 28 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A weakness has been identified in Dromara Sa-Token up to 1.44.0. This affects the function ObjectInputStream.readObject of the file SaJdkSerializer.java. Executing manipulation can lead to deserialization. The attack may be launched remotely. This attack is characterized by high complexity. It is indicated that the exploitability is difficult. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-502 (Deserialization of Untrusted Data), CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2025-15117 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15117 is a low-severity unsafe deserialization vulnerability in Dromara Sa-Token, published on 28 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-15117 in the wild and no public exploit code.

Affected product: Dromara Sa-Token. 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-15117/ (Markdown: https://insights.sbomify.com/CVE-2025-15117/index.md)
```

## Sources

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

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