# CVE-2025-4740: BeamCtrl Airiana coef deserialization

> A local deserialization vulnerability in BeamCtrl Airiana allows attackers with permissions to potentially execute arbitrary code.

- **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:** 16 May 2025
- **Updated:** 16 May 2025
- **Also known as:** GHSA-7q88-2mv9-q87j

## What is CVE-2025-4740?

CVE-2025-4740 is a medium-severity unsafe deserialization vulnerability in BeamCtrl Airiana, published on 16 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 BeamCtrl Airiana up to 11.0. It has been declared as problematic. This vulnerability affects unknown code of the file coef. The manipulation leads to deserialization. The attack needs to be approached locally. The exploit has been disclosed to the public and may be used.

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

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


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

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

## Is CVE-2025-4740 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4740 is a medium-severity unsafe deserialization vulnerability in BeamCtrl Airiana, published on 16 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-4740 exists.

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

## Sources

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

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