diff --git a/security/file_integrity_operator/file-integrity-operator-release-notes.adoc b/security/file_integrity_operator/file-integrity-operator-release-notes.adoc
index 93c582c478..2c26a062c7 100644
--- a/security/file_integrity_operator/file-integrity-operator-release-notes.adoc
+++ b/security/file_integrity_operator/file-integrity-operator-release-notes.adoc
@@ -15,6 +15,21 @@ For an overview of the File Integrity Operator, see xref:../../security/file_int
 
 To access the latest release, see xref:../../security/file_integrity_operator/file-integrity-operator-updating.adoc#olm-preparing-upgrade_file-integrity-operator-updating[Updating the File Integrity Operator].
 
+
+[id="file-integrity-operator-release-notes-1-3-8"]
+== OpenShift File Integrity Operator 1.3.8
+
+The following advisory is available for the OpenShift File Integrity Operator 1.3.8:
+
+* link:https://access.redhat.com/errata/RHSA-2025:23542[RHSA-2025:23542 OpenShift File Integrity Operator Update]
+
+[id="file-integrity-operator-1-3-8-bug-fixes"]
+=== Bug fixes
+
+* Previously, the file-integrity-operator pods and the aide pods running the database used by recently installed FIO would go into a terminating state, adding error log entries that were not useful. With this release, the pods needed by FIO do not go into terminating state unless a relevant error occurred or they completed their work.  (link:https://issues.redhat.com/browse/CMP-3757[*CMP-3757*])
+
+* This update includes upgraded dependencies in the underlying base images.
+
 [id="file-integrity-operator-release-notes-1-3-7"]
 == OpenShift File Integrity Operator 1.3.7