{ "dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": { "cveId": "CVE-2026-33757", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "state": "PUBLISHED", "assignerShortName": "GitHub_M", "dateReserved": "2026-03-23T18:30:14.125Z", "datePublished": "2026-03-27T14:10:58.639Z", "dateUpdated": "2026-03-27T14:10:58.639Z" }, "containers": { "cna": { "title": "OpenBao lacks user confirmation for OIDC direct callback mode", "problemTypes": [ { "descriptions": [ { "cweId": "CWE-384", "lang": "en", "description": "CWE-384: Session Fixation", "type": "CWE" } ] } ], "metrics": [ { "cvssV3_1": { "attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "LOW", "baseScore": 9.6, "baseSeverity": "CRITICAL", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "CHANGED", "userInteraction": "REQUIRED", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:L", "version": "3.1" } } ], "references": [ { "name": "https://github.com/openbao/openbao/security/advisories/GHSA-7q7g-x6vg-xpc3", "tags": [ "x_refsource_CONFIRM" ], "url": "https://github.com/openbao/openbao/security/advisories/GHSA-7q7g-x6vg-xpc3" }, { "name": "https://github.com/openbao/openbao/commit/e32103951925723e9787e33886ab6b6ec20f4964", "tags": [ "x_refsource_MISC" ], "url": "https://github.com/openbao/openbao/commit/e32103951925723e9787e33886ab6b6ec20f4964" }, { "name": "https://datatracker.ietf.org/doc/html/rfc8628#section-5.4", "tags": [ "x_refsource_MISC" ], "url": "https://datatracker.ietf.org/doc/html/rfc8628#section-5.4" } ], "affected": [ { "vendor": "openbao", "product": "openbao", "versions": [ { "version": "< 2.5.2", "status": "affected" } ] } ], "providerMetadata": { "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2026-03-27T14:10:58.639Z" }, "descriptions": [ { "lang": "en", "value": "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." } ], "source": { "advisory": "GHSA-7q7g-x6vg-xpc3", "discovery": "UNKNOWN" } } } }