OpenBao has potential Denial of Service vulnerability when processing malicious unauthenticated JSON requests
High7.5CVE-2025-59043 · Published Oct 17, 2025 · updated Jul 27, 2026
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| github.com/openbao/openbao Go | < 2.4.1 | 2.4.1 |
Details and references
### Summary JSON objects after decoding might use more memory than their serialized version. It is possible to tune a JSON to maximize the factor between serialized memory usage and deserialized memory usage (similar to a zip bomb). While reproducing the issue, we could reach a factor of about 35. This can be used to circumvent the [`max_request_size` (https://openbao.org/docs/configuration/listener/tcp/) configuration parameter, which is meant to protect against Denial of Service attacks, and also makes Denial of Service attacks easier in general, as the attacker needs much less resources. ### Details The request body is parsed into a `map[string]interface{}` https://github.com/openbao/openbao/blob/788536bd3e10818a7b4fb00aac6affc23388e5a9/http/logical.go#L50 very early in the request handling chain (before authentication), which means an attacker can send a specifically crafted JSON object and cause an OOM crash. Additionally, for simpler requests with large numbers of strings, the audit subsystem can consume large quantities of CPU. To remediate, set `max_request_json_memory` and `max_request_json_strings`. ### Impact - Unauthenticated Denial of Service ### Resources This issue was disclosed directly to HashiCorp and is the OpenBao equivalent of the following tickets: - https://discuss.hashicorp.com/t/hcsec-2025-24-vault-denial-of-service-though-complex-json-payloads/76393 - https://nvd.nist.gov/vuln/detail/CVE-2025-6203 HashiCorp attributes the problem to the audit subsystem. For OpenBao, it was noted the problem was additionally in the requests handling logic.
- CVSS 3.1
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-400
- Also known as
- BIT-openbao-2025-59043, CVE-2025-59043, GO-2025-4039
- github.com/openbao/openbao/security/advisories/GHSA-g46h-2rq9-gw5m
- nvd.nist.gov/vuln/detail/CVE-2025-59043
- nvd.nist.gov/vuln/detail/CVE-2025-6203
- github.com/openbao/openbao/pull/1756
- github.com/openbao/openbao/commit/d418f238bc99adc72c73109faf574cc2b672880c
- discuss.hashicorp.com/t/hcsec-2025-24-vault-denial-of-service-though-complex-json-payloads/76393
- github.com/openbao/openbao
- github.com/openbao/openbao/blob/788536bd3e10818a7b4fb00aac6affc23388e5a9/http/logical.go#L50
More openbao advisories
All| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Oct 222025 | OpenBao leaks HTTPRawBody in Audit Logs CVE-2025-62513Mediumfixed in 0.0.0-20251022165510-cc2c476bac66 | Medium | 0.0.0-20251022165510-cc2c476bac66 |
| Oct 222025 | OpenBao and Vault Leak []byte Fields in Audit Logs CVE-2025-62705Mediumfixed in 0.0.0-20251022165510-cc2c476bac66 | Medium | 0.0.0-20251022165510-cc2c476bac66 |
| Nov 242025 | OpenBao is Vulnerable to Privileged Operator Identity Group Root Escalation CVE-2025-64761Highfixed in 2.4.4 | High | 2.4.4 |
| Aug 82025 | OpenBao LDAP MFA Enforcement Bypass When Using Username As Alias CVE-2025-55001Medium6.5fixed in 0.0.0-20250807212521-c52795c1ef74, 2.3.2 | Medium6.5 | 0.0.0-20250807212521-c52795c1ef74, 2.3.2 |
| Aug 82025 | OpenBao Login MFA Bypass of Rate Limiting and TOTP Token Reuse CVE-2025-55003Medium5.7fixed in 0.0.0-20250807113757-8340a6918f6c, 2.3.2 | Medium5.7 | 0.0.0-20250807113757-8340a6918f6c, 2.3.2 |
| Aug 82025 | OpenBao TOTP Secrets Engine Code Reuse CVE-2025-55000Medium6.5fixed in 0.0.0-20250806193153-183891f8d535, 2.3.2 | Medium6.5 | 0.0.0-20250806193153-183891f8d535, 2.3.2 |