# CVE-2025-69806: Information disclosure in n/a

> Unauthenticated remote attackers can leak relative information via out-of-bounds read in bareiron server packets.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Feb 2026
- **Updated:** 18 Feb 2026
- **Also known as:** GHSA-ghfm-hghj-9j75

## What is CVE-2025-69806?

CVE-2025-69806 is a high-severity vulnerability in n/a, published on 12 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

p2r3 bareiron commit: 8e4d4020d contains an Out-of-bounds Read, which allows unauthenticated remote attackers to get relative information leakage via a packet sent to the server

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: P2r3 Bareiron.

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

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

## Is CVE-2025-69806 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-69809](https://insights.sbomify.com/CVE-2025-69809/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-69808](https://insights.sbomify.com/CVE-2025-69808/): Information disclosure in n/a (critical 9.1)
- [CVE-2025-69807](https://insights.sbomify.com/CVE-2025-69807/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-69806 is a high-severity vulnerability in n/a, published on 12 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-69806 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-69806/ (Markdown: https://insights.sbomify.com/CVE-2025-69806/index.md)
```

## Sources

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

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