# CVE-2025-14606: tiny-rdm Tiny RDM Pickle Decoding pickle_convert.go pickle.loads deserialization

> Remote attackers can exploit unsafe pickle deserialization in Tiny RDM to potentially execute arbitrary code, though exploitation is complex.

- **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:** 13 Dec 2025
- **Updated:** 15 Dec 2025
- **Also known as:** GHSA-q342-f5wx-9hj7

## What is CVE-2025-14606?

CVE-2025-14606 is a low-severity unsafe deserialization vulnerability in tiny-rdm Tiny RDM, published on 13 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security vulnerability has been detected in tiny-rdm Tiny RDM up to 1.2.5. Affected by this vulnerability is the function pickle.loads of the file pickle_convert.go of the component Pickle Decoding. The manipulation leads to deserialization. The attack can be initiated remotely. A high degree of complexity is needed for the attack. The exploitation appears to be difficult. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.

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

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


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

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

## Is CVE-2025-14606 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14606 is a low-severity unsafe deserialization vulnerability in tiny-rdm Tiny RDM, published on 13 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-14606 exists.

Affected product: tiny-rdm Tiny RDM. 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-14606/ (Markdown: https://insights.sbomify.com/CVE-2025-14606/index.md)
```

## Sources

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

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