Cyber Resilience

CVE-2025-69809

P2R3 Bareiron 2025-09-16

Published
16 March 2026
Modified
27 April 2026
Patch / advisory
View advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0053 42th percentile
Risk Priority 71 floored blend · peak EPSS

Summary

CVE-2025-69809 is a critical-severity Write-what-where Condition (CWE-123) vulnerability in P2R3 Bareiron. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 42th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-16 (Memory Protection) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-69809 is a write-what-where vulnerability affecting p2r3 Bareiron at commit 8e4d40. This flaw allows unauthenticated attackers to write arbitrary values to memory locations of their choosing, leading to arbitrary code execution. The issue is classified under CWE-123 and carries a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), indicating critical severity due to its network accessibility, low complexity, and lack of prerequisites.

Unauthenticated remote attackers can exploit this vulnerability by sending a specially crafted packet to a vulnerable instance of p2r3 Bareiron. Successful exploitation grants full arbitrary code execution, potentially compromising the entire system with high confidentiality, integrity, and availability impacts. No user interaction or privileges are required, making it highly exploitable over the network.

Mitigation details and advisories are documented in the project's GitHub repository at https://github.com/p2r3/bareiron and a dedicated advisory at https://github.com/vmpr0be/bareiron-vr/blob/main/CVE-2025-69809.md. The vulnerability was published on 2026-03-16T19:16:14.960.

EU & UK References

Vulnerability Data

A write-what-where condition in p2r3 Bareiron commit 8e4d40 allows unauthenticated attackers to write arbitrary values to memory, enabling arbitrary code execution via a crafted packet.

CWE(s)
CWE-123

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
T1687 Exploitation for Defense Impairment Defense Impairment
Adversaries may exploit vulnerabilities in security software, infrastructure, or defensive components to degrade, disable, or otherwise continue to impair their ability to prevent, detect, or respond to malicious activity.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-69807Same product: P2R3 Bareiron
CVE-2025-69808Same product: P2R3 Bareiron
CVE-2025-69806Same product: P2R3 Bareiron
CVE-2024-36877Shared CWE-123
CVE-2026-30121Shared CWE-123
CVE-2025-9900Shared CWE-123
CVE-2024-45142Shared CWE-123
CVE-2025-7403Shared CWE-123
CVE-2026-45257Shared CWE-123
CVE-2025-14857Shared CWE-123

Affected Assets

p2r3
bareiron
2025-09-16

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 4 hardening rules · 4 OS baselines
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

SI-16 Memory Protection good match

Memory-protection mechanisms block unauthorized writes to arbitrary locations even if a write-what-where primitive exists.

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles require memory-safe coding and bounds checking that eliminate the root cause of write-what-where flaws.

SC-39 Process Isolation partial match

Process isolation confines the blast radius of an arbitrary write so it cannot affect other domains.

SI-10 Information Input Validation partial match

Input validation directly stops malformed data from triggering buffer overflows that produce arbitrary write-what-where conditions.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent arbitrary write conditions via safe coding, bounds checking, and memory-safe constructs.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance can detect write-what-where conditions before deployment.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle practices directly reduce the likelihood of write-what-where flaws such as buffer overflows.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate input validation and bounds checking that mitigate arbitrary write conditions.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture and engineering principles discourage unsafe memory handling that leads to write-what-where vulnerabilities.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe buffer operations that enable arbitrary memory writes.

A.8.32 Change management partial match
prevents

Change management processes help ensure security fixes for such weaknesses are properly deployed.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248592 OL 8 must clear memory when it is freed to prevent use-after-free attacks. prevents CWE-123
RHEL 8 (1 rule)
  • V-230279 RHEL 8 must clear memory when it is freed to prevent use-after-free attacks. prevents CWE-123
Windows 10 (1 rule)
  • V-220727 Structured Exception Handling Overwrite Protection (SEHOP) must be enabled. prevents CWE-123
Windows 11 (1 rule)
  • V-253284 Structured Exception Handling Overwrite Protection (SEHOP) must be enabled. prevents CWE-123

References