https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 04:50:08 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-15603 bdu:2025-15603 https://cve.radiocsirt.org/vuln/bdu:2025-15603 https://cve.radiocsirt.org/vuln/bit-openbao-2025-62513 <p><strong>Affected:</strong> Bitnami: openbao</p> <p>OpenBao is an open source identity-based secrets management system. In versions 2.2.0 to 2.4.1, OpenBao&#39;s audit log experienced a regression wherein raw HTTP bodies used by few endpoints were not correctly redacted (HMAC&#39;d). This impacts those using the ACME functionality of PKI, resulting in short-lived ACME verification challenge codes being leaked in the audit logs. Additionally, this impacts those using the OIDC issuer functionality of the identity subsystem, auth and token response codes along with claims could be leaked in the audit logs. ACME verification codes are not usable after verification or challenge expiry so are of limited long-term use. This issue has been patched in OpenBao 2.4.2.</p> <p><strong>Affected:</strong> Bitnami: openbao</p> <p>OpenBao is an open source identity-based secrets management system. In versions 2.2.0 to 2.4.1, OpenBao&#39;s audit log experienced a regression wherein raw HTTP bodies used by few endpoints were not correctly redacted (HMAC&#39;d). This impacts those using the ACME functionality of PKI, resulting in short-lived ACME verification challenge codes being leaked in the audit logs. Additionally, this impacts those using the OIDC issuer functionality of the identity subsystem, auth and token response codes along with claims could be leaked in the audit logs. ACME verification codes are not usable after verification or challenge expiry so are of limited long-term use. This issue has been patched in OpenBao 2.4.2.</p> https://cve.radiocsirt.org/vuln/bit-openbao-2025-62513 https://cve.radiocsirt.org/vuln/euvd-2026-256664 EUVD-2026-256664 https://cve.radiocsirt.org/vuln/euvd-2026-256664 https://cve.radiocsirt.org/vuln/fkie_cve-2025-62513 <p>OpenBao is an open source identity-based secrets management system. In versions 2.2.0 to 2.4.1, OpenBao&#39;s audit log experienced a regression wherein raw HTTP bodies used by few endpoints were not correctly redacted (HMAC&#39;d). This impacts those using the ACME functionality of PKI, resulting in short-lived ACME verification challenge codes being leaked in the audit logs. Additionally, this impacts those using the OIDC issuer functionality of the identity subsystem, auth and token response codes along with claims could be leaked in the audit logs. ACME verification codes are not usable after verification or challenge expiry so are of limited long-term use. This issue has been patched in OpenBao 2.4.2.</p> <p>OpenBao is an open source identity-based secrets management system. In versions 2.2.0 to 2.4.1, OpenBao&#39;s audit log experienced a regression wherein raw HTTP bodies used by few endpoints were not correctly redacted (HMAC&#39;d). This impacts those using the ACME functionality of PKI, resulting in short-lived ACME verification challenge codes being leaked in the audit logs. Additionally, this impacts those using the OIDC issuer functionality of the identity subsystem, auth and token response codes along with claims could be leaked in the audit logs. ACME verification codes are not usable after verification or challenge expiry so are of limited long-term use. This issue has been patched in OpenBao 2.4.2.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-62513 https://cve.radiocsirt.org/vuln/ghsa-ghfh-fmx4-26h8 <p><strong>Affected:</strong> Go: github.com/openbao/openbao</p> <p>### Impact</p> <p>OpenBao&#39;s audit log experienced a regression wherein raw HTTP bodies used by few endpoints were not correctly redacted (HMAC&#39;d). This impacted the following subsystems:</p> <p>- When using the ACME functionality of PKI, this would result in short-lived ACME verification challenge codes being leaked in the audit logs. - When using the OIDC issuer functionality of the identity subsystem, auth and token response codes along with claims could be leaked in the audit logs.</p> <p>Third-party plugins may be affected.</p> <p>### Patches</p> <p>OpenBao v2.4.2 will patch this issue.</p> <p>### Workarounds</p> <p>If users do not use the above functionality, they are not impacted. ACME verification codes are not usable after verification or challenge expiry so are of limited long-term use.</p> <p><strong>Affected:</strong> Go: github.com/openbao/openbao</p> <p>### Impact</p> <p>OpenBao&#39;s audit log experienced a regression wherein raw HTTP bodies used by few endpoints were not correctly redacted (HMAC&#39;d). This impacted the following subsystems:</p> <p>- When using the ACME functionality of PKI, this would result in short-lived ACME verification challenge codes being leaked in the audit logs. - When using the OIDC issuer functionality of the identity subsystem, auth and token response codes along with claims could be leaked in the audit logs.</p> <p>Third-party plugins may be affected.</p> <p>### Patches</p> <p>OpenBao v2.4.2 will patch this issue.</p> <p>### Workarounds</p> <p>If users do not use the above functionality, they are not impacted. ACME verification codes are not usable after verification or challenge expiry so are of limited long-term use.</p> https://cve.radiocsirt.org/vuln/ghsa-ghfh-fmx4-26h8 https://cve.radiocsirt.org/vuln/opensuse-su-2025:15663-1 <p>openbao-2.4.3-1.1 on GA media</p> <p>openbao-2.4.3-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:15663-1 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2391 <p>Ein Angreifer kann mehrere Schwachstellen in OpenBao ausnutzen, um Informationen offenzulegen, und um einen Denial of Service Angriff durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in OpenBao ausnutzen, um Informationen offenzulegen, und um einen Denial of Service Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2391