# CVE-2025-63927: Use after free in n/a

> A heap-use-after-free in the IEC104 library allows attackers to cause crashes or potential code execution via multi-threaded client execution.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Nov 2025
- **Updated:** 13 Nov 2025
- **Also known as:** GHSA-jwc4-5hfq-4hfm

## What is CVE-2025-63927?

CVE-2025-63927 is a medium-severity use after free vulnerability in n/a, published on 12 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A heap-use-after-free vulnerability exists in airpig2011 IEC104 thru Commit be6d841 (2019-07-08). During multi-threaded client execution, the function Iec10x_Scheduled can access memory that has already been freed, potentially causing program crashes or undefined behavior. This may be exploited to trigger a denial-of-service or memory corruption.

Weakness: CWE-122 (Heap-based Buffer Overflow)

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

It affects 1 product.


Products: Airpig2011 Iec104.

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

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

## Is CVE-2025-63927 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-63929](https://insights.sbomify.com/CVE-2025-63929/): Null dereference in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63927 is a medium-severity use after free vulnerability in n/a, published on 12 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-63927 in the wild and no public exploit code.

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

## Sources

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

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