How severe is GHSA-rc54-2g2c-g36g?

No CVSS score has been assigned to GHSA-rc54-2g2c-g36g yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rc54-2g2c-g36g?

GHSA-rc54-2g2c-g36g affects the following packages: github.com/openbao/openbao (Go). Ecosystems affected: Go.

How do I fix GHSA-rc54-2g2c-g36g?

Update github.com/openbao/openbao to 0.0.0-20251022165510-cc2c476bac66 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rc54-2g2c-g36g is resolved across your whole dependency graph.

How do I detect GHSA-rc54-2g2c-g36g 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-rc54-2g2c-g36g 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.

Is GHSA-rc54-2g2c-g36g actively exploited in the wild?

No public exploit code has been indexed for GHSA-rc54-2g2c-g36g 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-rc54-2g2c-g36g?

GHSA-rc54-2g2c-g36g has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 26th 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-rc54-2g2c-g36g?

GHSA-rc54-2g2c-g36g is classified as CWE-532 (CWE-532). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-rc54-2g2c-g36g published, and has it been updated?

GHSA-rc54-2g2c-g36g was published on October 22, 2025 and was last updated on July 27, 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

OpenBao and Vault Leak []byte Fields in Audit LogsGHSA-rc54-2g2c-g36g

Fix: openbao/openbao@cc2c476

GHSA-rc54-2g2c-g36g is a CWE-532 vulnerability in github.com/openbao/openbao. A fix is available for github.com/openbao/openbao — see the affected versions and patch details below.

Also known asBIT-openbao-2025-62705CVE-2025-62705GO-2025-4052

Published

Oct 22, 2025

Updated

Jul 27, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 6, 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-rc54-2g2c-g36g.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs26th percentile — riskier than 26% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

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 audit log did not appropriately redact fields when relevant subsystems sent []byte response parameters rather than strings. This includes, but is not limited to:

sys/raw with use of encoding=base64, all data would be emitted unredacted to the audit log.
Transit, when performing a signing operation with a derived Ed25519 key, would emit public keys to the audit log.

Third-party plugins may be affected.

This issue has been present since HashiCorp Vault and continues to impact Vault as of v1.20.4.

Patches

OpenBao v2.4.2 will patch this issue.

Workarounds

If users do not use the above functionality, they are not impacted. To prohibit the use of sys/raw globally, ensure raw_storage_endpoint=false is set or missing from the server configuration.

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

openbaoopenbao

< 2.4.2

range

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-20251022165510-cc2c476bac66 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rc54-2g2c-g36g 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.

Frequently Asked Questions

### Impact OpenBao's audit log did not appropriately redact fields when relevant subsystems sent `[]byte` response parameters rather than `string`s. This includes, but is not limited to: - `sys/raw` with use of `encoding=base64`, all data would be emitted unredacted to the audit log. - Transit, when performing a signing operation with a derived Ed25519 key, would emit public keys to the audit log. Third-party plugins may be affected. This issue has been present since HashiCorp Vault and continues to impact Vault as of v1.20.4. ### Patches OpenBao v2.4.2 will patch this issue. ### Worka

O3 Security · Impact-Aware SCA

Is GHSA-rc54-2g2c-g36g in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works