# CVE-2025-69988: Missing authorization in n/a

> Unauthenticated attackers in physical proximity can access the camera's private network to view live video and audio streams without credentials.

- **Severity:** Medium 6.5 (`CVSS:3.1/AC:L/AV:A/A:N/C:H/I:N/PR:N/S:U/UI:N`)
- **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:** 27 Mar 2026
- **Updated:** 27 Mar 2026
- **Also known as:** GHSA-fjvv-w3wx-mfff

## What is CVE-2025-69988?

CVE-2025-69988 is a medium-severity missing authorization vulnerability in n/a, published on 27 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

BS Producten Petcam 33.1.0.0818 is vulnerable to Incorrect Access Control. An unauthenticated attacker in physical proximity can associate with this open network. Once connected, the attacker gains access to the camera's private network interface and can retrieve sensitive information, including the live video and audio stream, without providing credentials.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2025-69988 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-69988 is a medium-severity missing authorization vulnerability in n/a, published on 27 Mar 2026. 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-69988 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-69988/ (Markdown: https://insights.sbomify.com/CVE-2025-69988/index.md)
```

## Sources

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

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