CVE-2026-33757

What it is

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 "remote phishing" 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.

At a glance

Exploitability

Can be exploited over the network without logging in, but needs a user to act. High risk of data exposure, data tampering.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-03-27 15:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-07-15 02:20 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.4% in the next 30 days (EPSS).
• Severity: 9.6 CRITICAL (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-03-27 15:16 UTC

Last modified

2026-07-15 02:20 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-384

Record status

Modified

Affected

• Openbao < 2.5.2

Attack profile CVSS 3.1 · 9.6

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

Low

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-33757.md and follow it. Check whether this project is affected by CVE-2026-33757. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge