# CVE-2025-15222: Dromara Sa-Token SaSerializerTemplateForJdkUseBase64.java ObjectInputStream.readObject deserialization

> Remote attackers can exploit unsafe deserialization in Sa-Token to potentially execute arbitrary code, requiring high complexity and specific conditions.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 30 Dec 2025
- **Updated:** 30 Dec 2025
- **Also known as:** GHSA-9gcg-r6x9-gh93

## What is CVE-2025-15222?

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

### Official description

A vulnerability has been found in Dromara Sa-Token up to 1.44.0. This issue affects the function ObjectInputStream.readObject of the file SaSerializerTemplateForJdkUseBase64.java. Such manipulation leads to deserialization. The attack can be executed remotely. This attack is characterized by high complexity. The exploitability is assessed as difficult. The exploit has been disclosed to the public and may be used. 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-15222?


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

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

## Is CVE-2025-15222 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15222 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15222 is a low-severity unsafe deserialization vulnerability in Dromara Sa-Token, published on 30 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15222 exists.

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-15222/ (Markdown: https://insights.sbomify.com/CVE-2025-15222/index.md)
```

## Sources

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

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