Vulnerability-Lookup

CNVD-2026-16031

Vulnerability from cnvd - Published: 2026-04-03

Title

OpenBao授权问题漏洞

Description

OpenBao是OpenBao开源的一个敏感数据管理软件。 OpenBao存在授权问题漏洞，该漏洞源于通过JWT/OIDC登录且角色callback_mode设置为direct时未提示用户确认，攻击者可利用该漏洞导致远程钓鱼攻击。

Severity

高

Patch Name

OpenBao授权问题漏洞的补丁

Patch Description

OpenBao是OpenBao开源的一个敏感数据管理软件。 OpenBao存在授权问题漏洞，该漏洞源于通过JWT/OIDC登录且角色callback_mode设置为direct时未提示用户确认，攻击者可利用该漏洞导致远程钓鱼攻击。目前，供应商发布了安全公告及相关补丁信息，修复了此漏洞。

Formal description

目前厂商已发布升级补丁以修复漏洞，补丁获取链接： https://github.com/openbao/openbao/releases

Reference

https://github.com/openbao/openbao/releases

Impacted products

Name
openbao openbao <2.5.2

Show details on source website

JSON

To clipboard

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2026-33757",
      "cveUrl": "https://nvd.nist.gov/vuln/detail/CVE-2026-33757"
    }
  },
  "description": "OpenBao\u662fOpenBao\u5f00\u6e90\u7684\u4e00\u4e2a\u654f\u611f\u6570\u636e\u7ba1\u7406\u8f6f\u4ef6\u3002\n\nOpenBao\u5b58\u5728\u6388\u6743\u95ee\u9898\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u901a\u8fc7JWT/OIDC\u767b\u5f55\u4e14\u89d2\u8272callback_mode\u8bbe\u7f6e\u4e3adirect\u65f6\u672a\u63d0\u793a\u7528\u6237\u786e\u8ba4\uff0c\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u5bfc\u81f4\u8fdc\u7a0b\u9493\u9c7c\u653b\u51fb\u3002",
  "formalWay": "\u76ee\u524d\u5382\u5546\u5df2\u53d1\u5e03\u5347\u7ea7\u8865\u4e01\u4ee5\u4fee\u590d\u6f0f\u6d1e\uff0c\u8865\u4e01\u83b7\u53d6\u94fe\u63a5\uff1a\r\nhttps://github.com/openbao/openbao/releases",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2026-16031",
  "openTime": "2026-04-03",
  "patchDescription": "OpenBao\u662fOpenBao\u5f00\u6e90\u7684\u4e00\u4e2a\u654f\u611f\u6570\u636e\u7ba1\u7406\u8f6f\u4ef6\u3002\r\n\r\nOpenBao\u5b58\u5728\u6388\u6743\u95ee\u9898\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u901a\u8fc7JWT/OIDC\u767b\u5f55\u4e14\u89d2\u8272callback_mode\u8bbe\u7f6e\u4e3adirect\u65f6\u672a\u63d0\u793a\u7528\u6237\u786e\u8ba4\uff0c\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u5bfc\u81f4\u8fdc\u7a0b\u9493\u9c7c\u653b\u51fb\u3002\u76ee\u524d\uff0c\u4f9b\u5e94\u5546\u53d1\u5e03\u4e86\u5b89\u5168\u516c\u544a\u53ca\u76f8\u5173\u8865\u4e01\u4fe1\u606f\uff0c\u4fee\u590d\u4e86\u6b64\u6f0f\u6d1e\u3002",
  "patchName": "OpenBao\u6388\u6743\u95ee\u9898\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": "openbao openbao \u003c2.5.2"
  },
  "referenceLink": "https://github.com/openbao/openbao/releases",
  "serverity": "\u9ad8",
  "submitTime": "2026-04-02",
  "title": "OpenBao\u6388\u6743\u95ee\u9898\u6f0f\u6d1e"
}

CVE-2026-33757 (GCVE-0-2026-33757)

Vulnerability from cvelistv5 – Published: 2026-03-27 14:10 – Updated: 2026-04-01 03:55

Title

OpenBao lacks user confirmation for OIDC direct callback mode

Summary

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.

Severity ?

9.6 (Critical)


                        
                          CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:L

CWE

CWE-384 - Session Fixation

Assigner

GitHub_M

References

URL

Tags

	https://github.com/openbao/openbao/security/advis…	x_refsource_CONFIRM
	https://github.com/openbao/openbao/commit/e321039…	x_refsource_MISC
	https://datatracker.ietf.org/doc/html/rfc8628#sec…	x_refsource_MISC

Impacted products

	Vendor	Product	Version
	openbao	openbao	Affected: < 2.5.2

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-33757",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "total"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-03-31T00:00:00+00:00",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-04-01T03:55:23.497Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "openbao",
          "vendor": "openbao",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c 2.5.2"
            }
          ]
        }
      ],
      "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."
        }
      ],
      "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"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-384",
              "description": "CWE-384: Session Fixation",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-03-27T14:10:58.639Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "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"
        }
      ],
      "source": {
        "advisory": "GHSA-7q7g-x6vg-xpc3",
        "discovery": "UNKNOWN"
      },
      "title": "OpenBao lacks user confirmation for OIDC direct callback mode"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2026-33757",
    "datePublished": "2026-03-27T14:10:58.639Z",
    "dateReserved": "2026-03-23T18:30:14.125Z",
    "dateUpdated": "2026-04-01T03:55:23.497Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

Action not permitted

CNVD-2026-16031

CVE-2026-33757 (GCVE-0-2026-33757)

Tags

Sightings

Nomenclature