How severe is GHSA-p49j-v9wc-wg57?

No CVSS score has been assigned to GHSA-p49j-v9wc-wg57 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-p49j-v9wc-wg57?

GHSA-p49j-v9wc-wg57 affects the following packages: github.com/openbao/openbao (Go). Ecosystems affected: Go.

How do I fix GHSA-p49j-v9wc-wg57?

Update github.com/openbao/openbao to 0.0.0-20260420162526-f58111d2ca54 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p49j-v9wc-wg57 is resolved across your whole dependency graph.

How do I detect GHSA-p49j-v9wc-wg57 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/openbao/openbao, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-p49j-v9wc-wg57 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-p49j-v9wc-wg57?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-p49j-v9wc-wg57 can be triaged on real exposure rather than presence alone.

Is GHSA-p49j-v9wc-wg57 actively exploited in the wild?

No public exploit code has been indexed for GHSA-p49j-v9wc-wg57 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-p49j-v9wc-wg57?

GHSA-p49j-v9wc-wg57 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 23th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-p49j-v9wc-wg57?

GHSA-p49j-v9wc-wg57 is classified as CWE-1259 (CWE-1259). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-p49j-v9wc-wg57 published, and has it been updated?

GHSA-p49j-v9wc-wg57 was published on April 21, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-p49j-v9wc-wg57 — openbao

Fix: openbao/openbao#2934

GHSA-p49j-v9wc-wg57 is a CWE-1259 vulnerability in github.com/openbao/openbao. A fix is available for github.com/openbao/openbao — see the affected versions and patch details below.

OpenBao's Token Store Allows Cross-Namespace Renewal, Revocation

Also known asBIT-openbao-2026-40264CVE-2026-40264GO-2026-5526

Published

Apr 21, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 18, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-p49j-v9wc-wg57.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs23th percentile — riskier than 23% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🐹github.com/openbao/openbao

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

OpenBao's namespaces provide multi-tenant separation. A tenant who leaks token accessors can have their token revoked or renewed by a privileged administrator in another tenant.

Patches

This was addressed in v2.5.3.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/openbao/openbao`	all versions	0.0.0-20260420162526-f58111d2ca54`go get github.com/openbao/openbao@v0.0.0-20260420162526-f58111d2ca54`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/openbao/openbao, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/openbao/openbao to 0.0.0-20260420162526-f58111d2ca54 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p49j-v9wc-wg57 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-p49j-v9wc-wg57 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-p49j-v9wc-wg57. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact OpenBao's namespaces provide multi-tenant separation. A tenant who leaks token accessors can have their token revoked or renewed by a privileged administrator in another tenant. ### Patches This was addressed in v2.5.3.

O3 Security · Impact-Aware SCA

Is GHSA-p49j-v9wc-wg57 in your dependencies?

O3 Security finds GHSA-p49j-v9wc-wg57 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works