CVE-2026-33757

HIGHNVD 8.38.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.3 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 66% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
8.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.3
EG Score
8.3(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity83% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
33.6%
KEV
Not listed

Published

March 27, 2026

Last Modified

July 15, 2026

Advisory Details (6)

Auto-updated Jun 30, 2026
Patch available. Sources: github, redhat, github_commit.
redhat
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-33757.json
redhat Patch Available

2452269 – (CVE-2026-33757) CVE-2026-33757 OpenBao: lack of user confirmation for OpenBao OIDC direct callback mode

https://bugzilla.redhat.com/show_bug.cgi?id=2452269
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-33757
github Patch Available

Lack of user confirmation for OpenBao OIDC direct callback mode · Advisory · openbao/openbao · GitHub

https://github.com/openbao/openbao/security/advisories/GHSA-7q7g-x6vg-xpc3
github_commit

commit e32103951925 (openbao/openbao)

Fix landed in openbao/openbao commit e32103951925 — awaiting tagged release

https://github.com/openbao/openbao/commit/e32103951925723e9787e33886ab6b6ec20f4964
generic

RFC 8628 - OAuth 2.0 Device Authorization Grant

https://datatracker.ietf.org/doc/html/rfc8628#section-5.4

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/openbao/openbao—0.0.0-20260325142553-e32103951925—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 33× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:09 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:24 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 02:29 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-18 06:59 UTCOSV refresh
  11. 2026-07-16 17:03 UTCEPSS rescore
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 02:22 UTCNVD updateCVSS v3 → 8.3 · severity → HIGH
  15. 2026-07-15 02:00 UTCEPSS rescore
  16. 2026-07-15 01:21 UTCMITRE cvelistV5CVSS v3 → 9.6 · severity → CRITICAL
  17. 2026-07-13 22:30 UTCEPSS rescore
  18. 2026-07-13 06:13 UTCEPSS rescore
  19. 2026-07-13 06:13 UTCEPSS rescore
  20. 2026-07-12 05:46 UTCEPSS rescore
  21. 2026-07-11 08:27 UTCEPSS rescore
  22. 2026-07-09 19:10 UTCEPSS rescore
  23. 2026-07-07 13:46 UTCEPSS rescore
  24. 2026-07-06 16:27 UTCEPSS rescore
  25. 2026-07-06 16:27 UTCEPSS rescore
Show 8 more
  1. 2026-07-06 02:23 UTCEPSS rescore
  2. 2026-07-06 02:23 UTCEPSS rescore
  3. 2026-07-05 02:30 UTCEPSS rescore
  4. 2026-07-04 06:31 UTCEPSS rescore
  5. 2026-07-01 15:06 UTCEPSS rescore
  6. 2026-06-30 23:22 UTCEPSS rescore
  7. 2026-06-30 04:37 UTCEG score recompute
  8. 2026-06-30 04:32 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-33757?
CVE-2026-33757 is a high vulnerability published on March 27, 2026. 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 callbackmode set to direct. This allows an attacker to start an authentication request and perform "remote phishing"…
When was CVE-2026-33757 disclosed?
CVE-2026-33757 was first published in the National Vulnerability Database on March 27, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33757 actively exploited?
CVE-2026-33757 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 33.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-33757?
CVE-2026-33757 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2026-33757?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33757, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33757

Explore →

Is Your Infrastructure Affected by CVE-2026-33757?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs