Infrastructure and Network

In Wazuh versions 4.3.0 through 4.12.x a low severity vulnerability CVE-2025-54866 was detected. This vulnerability allows all authenticated users on a Windows machine to access the `authd.pass` file due to missing access control lists (ACLs) on `C:\Program Files (x86)\ossec-agent\authd.pass`, exposing sensitive passwords. To address this issue, users should upgrade Wazuh to version 4.13.0 or later. For more details, visit https://nvd.nist.gov/vuln/detail/CVE-2025-54866.

In Wazuh Agent versions prior to 4.13.0 a high severity vulnerability CVE-2025-30201 was detected. This vulnerability allows authenticated attackers to force NTLM authentication via malicious UNC paths in agent configuration settings, potentially enabling NTLM relay attacks that could lead to privilege escalation and remote code execution. To address this issue, users should upgrade Wazuh to version 4.13.0 or later. For more details, visit https://nvd.nist.gov/vuln/detail/CVE-2025-30201.

In authentik versions prior to 2025.8.5 and 2025.10.2 a medium severity vulnerability CVE-2025-64708 was detected. This vulnerability allows expired invitations to remain valid because invitation validation relied solely on background cleanup tasks, which normally run every five minutes but may be delayed when a large backlog of tasks exists. As a result, expired invitations could still be used until the cleanup occurred. To address this issue, users should upgrade authentik to versions 2025.8.5, 2025.10.2, or later. For more details, visit https://nvd.nist.gov/vuln/detail/CVE-2025-64708.

In authentik versions prior to 2025.8.5 and 2025.10.2 a medium severity vulnerability CVE-2025-64521 was detected. This vulnerability allows authentication to succeed for service accounts created for OAuth providers even when those accounts are deactivated, while other permission checks and assigned policies continue to function correctly. To address this issue, users should upgrade authentik to versions 2025.8.5, 2025.10.2, or later. For more details, visit https://nvd.nist.gov/vuln/detail/CVE-2025-64521.

In Vault Community Edition versions 0.6.0 up to 1.20.4, and in Vault Enterprise versions 0.6.0 up to 1.20.4, 1.19.10, 1.18.15, and 1.16.26 a high severity vulnerability CVE-2025-11621 was detected. This vulnerability allows an attacker to bypass AWS authentication when the role of the configured bound_principal_iam is the same across AWS accounts or uses a wildcard. To address this issue, users should update to Vault Community Edition 1.21.0 or Vault Enterprise 1.21.0, 1.20.5, 1.19.11, or 1.16.27. For more details, visit https://nvd.nist.gov/vuln/detail/CVE-2025-11621.

In OpenVPN versions 2.7_alpha1 through 2.7_beta1 a high severity vulnerability CVE-2025-10680 was detected. This vulnerability allows a remote, authenticated OpenVPN server to inject and execute shell commands on POSIX-based clients via specially crafted DNS variables when the client is run with the –dns-updown option. To address this issue, users should upgrade OpenVPN to versions 2.7_beta2 or later (or otherwise avoid the vulnerable 2.7_alpha1–2.7_beta1 builds). For more details, visit https://nvd.nist.gov/vuln/detail/CVE-2025-10680.

In Vault Community Edition versions 1.20.3 to 1.20.4, and in Vault Enterprise versions 1.20.3 to 1.20.4, 1.19.9 to 1.19.10, 1.18.14 to 1.18.15, and 1.16.25 to 1.16.26 a high severity vulnerability CVE-2025-12044 was detected. This vulnerability allows unauthenticated attackers to trigger a denial of service by sending specially crafted JSON payloads that bypass rate limits due to a regression from a previous fix. To address this issue, users should update to Vault Community Edition 1.21.0 or Vault Enterprise 1.16.27, 1.18.16, 1.19.11, 1.20.5, or 1.21.0. For more details, visit https://nvd.nist.gov/vuln/detail/CVE-2025-12044.

In Vault Community Edition versions prior to 1.20.3 and Vault Enterprise versions prior to 1.20.3, 1.19.9, 1.18.14 and 1.16.25 a high severity vulnerability CVE-2025-6203 was detected. This vulnerability allows an unauthenticated attacker to cause a denial of service by submitting a specially-crafted complex JSON payload that leads to excessive memory and CPU consumption. To address this issue, users should upgrade Vault Community Edition to versions 1.20.3 or Vault Enterprise to versions 1.20.3, 1.19.9, 1.18.14, 1.16.25 or later. For more details, visit https://nvd.nist.gov/vuln/detail/CVE-2025-6203.

In Vault Community Edition versions from 1.10.0 up to 1.20.1 and Vault Enterprise versions from 1.10.0 up to 1.20.1, 1.19.7, 1.18.12, 1.16.23, 1.15.16 a medium severity vulnerability CVE-2025-6013 was found in the LDAP auth method. When username_as_alias was set to true, Vault could fail to enforce MFA if a user had multiple CNs that were identical except for leading or trailing spaces. This could allow an MFA bypass under certain conditions. To address this issue, users should upgrade Vault Community Edition to version 1.20.2 and Vault Enterprise versions 1.20.2, 1.19.8, 1.18.13 and 1.16.24. For more information, visit https://nvd.nist.gov/vuln/detail/CVE-2025-6013.