# CVE-2025-69986: Memory corruption in n/a

> An attacker can trigger a stack buffer overflow in the ONVIF service via a crafted SOAP request, leading to remote code execution or device crash.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Mar 2026
- **Updated:** 27 Mar 2026
- **Also known as:** GHSA-49jc-jpfq-h27g

## What is CVE-2025-69986?

CVE-2025-69986 is a high-severity memory corruption vulnerability in n/a, published on 27 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A buffer overflow vulnerability exists in the ONVIF GetStreamUri function of LSC Indoor Camera V7.6.32. The application fails to validate the length of the Protocol parameter inside the Transport element. By sending a specially crafted SOAP request containing an oversized protocol string, an attacker can overflow the stack buffer, overwriting the return instruction pointer (RIP). This vulnerability allows for Denial of Service (DoS) via device crash or Remote Code Execution (RCE) in the context of the ONVIF service.

Weakness: CWE-20 (Improper Input Validation), CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2025-69986 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-69986 is a high-severity memory corruption vulnerability in n/a, published on 27 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-69986 exists.

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

## Sources

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

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