https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 06:00:26 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-08727 bdu:2026-08727 https://cve.radiocsirt.org/vuln/bdu:2026-08727 https://cve.radiocsirt.org/vuln/bit-openbao-2026-33757 <p><strong>Affected:</strong> Bitnami: openbao</p> <p>OpenBao is an open source identity-based secrets management system. Prior to version 2.5.2, OpenBao does not prompt for user confirmation when logging in via JWT/OIDC and a role with `callback_mode` set to `direct`. This allows an attacker to start an authentication request and perform &#34;remote phishing&#34; by having the victim visit the URL and automatically log-in to the session of the attacker. Despite being based on the authorization code flow, the `direct` mode calls back directly to the API and allows an attacker to poll for an OpenBao token until it is issued. Version 2.5.2 includes an additional confirmation screen for `direct` type logins that requires manual user interaction in order to finish the authentication. This issue can be worked around either by removing any roles with `callback_mode=direct` or enforcing confirmation for every session on the token issuer side for the Client ID used by OpenBao.</p> <p><strong>Affected:</strong> Bitnami: openbao</p> <p>OpenBao is an open source identity-based secrets management system. Prior to version 2.5.2, OpenBao does not prompt for user confirmation when logging in via JWT/OIDC and a role with `callback_mode` set to `direct`. This allows an attacker to start an authentication request and perform &#34;remote phishing&#34; by having the victim visit the URL and automatically log-in to the session of the attacker. Despite being based on the authorization code flow, the `direct` mode calls back directly to the API and allows an attacker to poll for an OpenBao token until it is issued. Version 2.5.2 includes an additional confirmation screen for `direct` type logins that requires manual user interaction in order to finish the authentication. This issue can be worked around either by removing any roles with `callback_mode=direct` or enforcing confirmation for every session on the token issuer side for the Client ID used by OpenBao.</p> https://cve.radiocsirt.org/vuln/bit-openbao-2026-33757 https://cve.radiocsirt.org/vuln/cnvd-2026-16031 cnvd-2026-16031 https://cve.radiocsirt.org/vuln/cnvd-2026-16031 https://cve.radiocsirt.org/vuln/euvd-2026-337333 EUVD-2026-337333 https://cve.radiocsirt.org/vuln/euvd-2026-337333 https://cve.radiocsirt.org/vuln/fkie_cve-2026-33757 <p>OpenBao is an open source identity-based secrets management system. Prior to version 2.5.2, OpenBao does not prompt for user confirmation when logging in via JWT/OIDC and a role with `callback_mode` set to `direct`. This allows an attacker to start an authentication request and perform &#34;remote phishing&#34; by having the victim visit the URL and automatically log-in to the session of the attacker. Despite being based on the authorization code flow, the `direct` mode calls back directly to the API and allows an attacker to poll for an OpenBao token until it is issued. Version 2.5.2 includes an additional confirmation screen for `direct` type logins that requires manual user interaction in order to finish the authentication. This issue can be worked around either by removing any roles with `callback_mode=direct` or enforcing confirmation for every session on the token issuer side for the Client ID used by OpenBao.</p> <p>OpenBao is an open source identity-based secrets management system. Prior to version 2.5.2, OpenBao does not prompt for user confirmation when logging in via JWT/OIDC and a role with `callback_mode` set to `direct`. This allows an attacker to start an authentication request and perform &#34;remote phishing&#34; by having the victim visit the URL and automatically log-in to the session of the attacker. Despite being based on the authorization code flow, the `direct` mode calls back directly to the API and allows an attacker to poll for an OpenBao token until it is issued. Version 2.5.2 includes an additional confirmation screen for `direct` type logins that requires manual user interaction in order to finish the authentication. This issue can be worked around either by removing any roles with `callback_mode=direct` or enforcing confirmation for every session on the token issuer side for the Client ID used by OpenBao.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-33757 https://cve.radiocsirt.org/vuln/ghsa-7q7g-x6vg-xpc3 <p><strong>Affected:</strong> Go: github.com/openbao/openbao</p> <p>### Impact</p> <p>OpenBao does not prompt for user confirmation when logging in via JWT/OIDC and a role with `callback_mode` set to `direct`.</p> <p>This allows an attacker to start an authentication request and perform &#34;remote phishing&#34; by having the victim visit the URL and automatically log-in to the session of the attacker. Despite being based on the authorization code flow, the `direct` mode calls back directly to the API and allows an attacker to poll for an OpenBao token until it is issued.</p> <p>### Patches Version 2.5.2 includes an additional confirmation screen for `direct` type logins that requires manual user interaction in order to finish the authentication.</p> <p>### Workarounds This issue can be worked around either by removing any roles with `callback_mode=direct` or enforcing confirmation for every session on the token issuer side for the Client ID used by OpenBao.</p> <p><strong>Affected:</strong> Go: github.com/openbao/openbao</p> <p>### Impact</p> <p>OpenBao does not prompt for user confirmation when logging in via JWT/OIDC and a role with `callback_mode` set to `direct`.</p> <p>This allows an attacker to start an authentication request and perform &#34;remote phishing&#34; by having the victim visit the URL and automatically log-in to the session of the attacker. Despite being based on the authorization code flow, the `direct` mode calls back directly to the API and allows an attacker to poll for an OpenBao token until it is issued.</p> <p>### Patches Version 2.5.2 includes an additional confirmation screen for `direct` type logins that requires manual user interaction in order to finish the authentication.</p> <p>### Workarounds This issue can be worked around either by removing any roles with `callback_mode=direct` or enforcing confirmation for every session on the token issuer side for the Client ID used by OpenBao.</p> https://cve.radiocsirt.org/vuln/ghsa-7q7g-x6vg-xpc3 https://cve.radiocsirt.org/vuln/opensuse-su-2026:10438-1 <p>openbao-2.5.2-1.1 on GA media</p> <p>openbao-2.5.2-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:10438-1 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0864 <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in OpenBao ausnutzen, um Sicherheitsvorkehrungen zu umgehen oder einen Cross Site Scripting Angriff durchzuführen.</p> <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in OpenBao ausnutzen, um Sicherheitsvorkehrungen zu umgehen oder einen Cross Site Scripting Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0864