From 39d4e8069d93e847c76c7e06deb9effd9ca81d86 Mon Sep 17 00:00:00 2001
From: GroceryBoyJr <75502996+GroceryBoyJr@users.noreply.github.com>
Date: Fri, 16 Jan 2026 16:20:24 -0500
Subject: [PATCH] CO 1.8.1 Release Note

---
 .../compliance-operator-release-notes.adoc        | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/security/compliance_operator/compliance-operator-release-notes.adoc b/security/compliance_operator/compliance-operator-release-notes.adoc
index 332dbf2112..5c6b4570dc 100644
--- a/security/compliance_operator/compliance-operator-release-notes.adoc
+++ b/security/compliance_operator/compliance-operator-release-notes.adoc
@@ -17,6 +17,21 @@ To access the latest release, see xref:../../security/compliance_operator/co-man
 
 For more information on compliance support for all Red{nbsp}Hat products, see link:https://access.redhat.com/compliance[Product Compliance].
 
+
+[id="compliance-operator-release-notes-1-8-1_{context}"]
+== OpenShift Compliance Operator 1.8.1
+
+The following advisory is available for the OpenShift Compliance Operator 1.8.1:
+
+* link:https://access.redhat.com/errata/RHSA-2026:0737[RHSA-2026:0737 - OpenShift Compliance Operator 1.8.1 bug fix and enhancement update]
+
+[id="compliance-operator-1-8-1-bug-fixes_{context}"]
+=== Bug Fixes
+
+*  Before this release, Compliance Operator could cause a privilege escalation due to incorrect permissions on `/etc/passwd`. With this release, the permissions have been corrected. For more information, see (link:https://access.redhat.com/security/cve/cve-2025-7195[CVE-2025-7195]).
+
+* Previously, Compliance Operator scans using rhcos4 profile would incorrectly return `NOT-APPLICABLE` scan results when using {op-system-first} 10 systems. With this release, scans using rhcos4 profiles return `COMPLIANT` and `NON-COMPLIANT` results. For more information, see (link:https://issues.redhat.com/browse/CMP-4034[CMP-4034]).
+
 [id="compliance-operator-release-notes-1-8-0_{context}"]
 == OpenShift Compliance Operator 1.8.0