# CVE-2025-4905: iop-apl-uw basestation3 QC.py load_qc_pickl deserialization

> Local attackers can execute arbitrary code via unsafe deserialization in the QC.py module of iop-apl-uw basestation3.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 May 2025
- **Updated:** 19 May 2025
- **Also known as:** GHSA-9pm6-22w2-x4h9

## What is CVE-2025-4905?

CVE-2025-4905 is a medium-severity unsafe deserialization vulnerability in iop-apl-uw basestation3, published on 19 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in iop-apl-uw basestation3 up to 3.0.4 and classified as problematic. This issue affects the function load_qc_pickl of the file basestation3/QC.py. The manipulation of the argument qc_file leads to deserialization. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. The code maintainer tagged the issue as closed. But there is no new commit nor release in the GitHub repository available so far.

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

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

It affects 1 product.


Products: Washington Basestation.

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

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

## Is CVE-2025-4905 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4905 is a medium-severity unsafe deserialization vulnerability in iop-apl-uw basestation3, published on 19 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4905 exists.

Affected product: iop-apl-uw basestation3. 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-4905/ (Markdown: https://insights.sbomify.com/CVE-2025-4905/index.md)
```

## Sources

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

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