CVE-2025-54999: Github.com/openbao/openbao OpenBao Has A Timing Side-Channel Vulnerability
LOWCVE-2025-54999 is a LOW (CVSS 3.7) openbao has a timing side-channel vulnerability (CWE-203: Observable Discrepancy) affecting Github.com/openbao/openbao libraries in the Go ecosystem. The issue involves openbao has a timing side-channel in the userpass auth method. Remediation is available by upgrading affected packages to version 2.3.2, 0.0.0-20250806193356-4d9b5d3d6486.
CVE-2025-54999 at a Glance
Security Impact
CVSS: 3.7
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N).
How to Fix CVE-2025-54999
To remediate this vulnerability, upgrade all affected Github.com/openbao/openbao dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/openbao/openbao to 2.3.2
Upgrade github.com/openbao/openbao to 0.0.0-20250806193356-4d9b5d3d6486
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/openbao/openbao
How to Check if You Are Affected
To determine whether your application is affected by CVE-2025-54999, inspect your project dependencies for Github.com/openbao/openbao:
inspect dependencies for github.com/openbao/openbao
Analyze the terminal output to locate any version of Github.com/openbao/openbao in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.3.2), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-203: Observable Discrepancy, where the product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor. In Github.com/openbao/openbao, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2025-54999 Affected Github.com/openbao/openbao Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/openbao/openbao
|
Go |
≥ 0.1.0
< 2.3.2
|
2.3.2
|
|
github.com/openbao/openbao
|
Go |
< 0.0.0-20250806193356-4d9b5d3d6486
|
0.0.0-20250806193356-4d9b5d3d6486
|
References
Frequently Asked Questions
What is CVE-2025-54999?
Which Github.com/openbao/openbao versions are affected?
What version fixes CVE-2025-54999?
Is github.com/openbao/openbao affected?
What is the CVSS score of CVE-2025-54999?
What CWE is associated with CVE-2025-54999?
How can I check Go dependencies for CVE-2025-54999?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-hh28-h22f-8357",
"modified" : "2025-08-11T13:56:40Z",
"published" : "2025-08-08T14:41:14Z",
"aliases" : [ "CVE-2025-54999" ],
"summary" : "OpenBao has a Timing Side-Channel in the Userpass Auth Method",
"details" : "### Impact\n\nWhen using OpenBao's `userpass` auth method, user enumeration was possible due to timing difference between non-existent users and users with stored credentials. This is independent of whether the supplied credentials were valid for the given user. \n\n### Patches\n\nOpenBao v2.3.2 will patch this issue.\n\n### Workarounds\n\nUsers may use another auth method or apply rate limiting quotas to limit the number of requests in a period of time: https://openbao.org/api-docs/system/rate-limit-quotas/\n\n### References\n\nThis issue was disclosed to HashiCorp and is the OpenBao equivalent of the following tickets:\n\n- https://discuss.hashicorp.com/t/hcsec-2025-15-timing-side-channel-in-vault-s-userpass-auth-method/76034\n- https://nvd.nist.gov/vuln/detail/CVE-2025-6011\n\nBarring further information, this is also assumed to cover and remediate the following additional vulnerability:\n\n- https://discuss.hashicorp.com/t/hcsec-2025-21-vault-user-enumeration-in-userpass-auth-method/76095\n- https://nvd.nist.gov/vuln/detail/CVE-2025-6010\n\nIf this is not the case as further details emerge, a new CVE will be assigned for remediating that. Otherwise, no further CVE will be sought.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/openbao/openbao"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0.1.0"
}, {
"fixed" : "2.3.2"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/openbao/openbao"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.0.0-20250806193356-4d9b5d3d6486"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/openbao/openbao/security/advisories/GHSA-hh28-h22f-8357"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-54999"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-6011"
}, {
"type" : "WEB",
"url" : "https://github.com/openbao/openbao/commit/4d9b5d3d6486ab9fbd5b644173fa0097015d6626"
}, {
"type" : "WEB",
"url" : "https://discuss.hashicorp.com/t/hcsec-2025-15-timing-side-channel-in-vault-s-userpass-auth-method/76034"
}, {
"type" : "WEB",
"url" : "https://discuss.hashicorp.com/t/hcsec-2025-21-vault-user-enumeration-in-userpass-auth-method/76095"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/openbao/openbao"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-203" ],
"severity" : "LOW",
"github_reviewed" : true,
"github_reviewed_at" : "2025-08-08T14:41:14Z",
"nvd_published_at" : "2025-08-09T03:15:46Z"
}
}