CVE-2025-59043: OpenBao has potential Denial of Service vulnerability when processing malicious unauthenticated JSON requests
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.
Published Oct 17, 2025
Affected packages
github.com/openbao/openbao
- Ecosystem
- Go
- Affected
- <= 2.4.0
- Fixed in
- 2.4.1
- Check
go list -m github.com/openbao/openbao
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
Credited to phil9909.
References
- https://github.com/openbao/openbao/security/advisories/GHSA-g46h-2rq9-gw5m
- https://nvd.nist.gov/vuln/detail/CVE-2025-6203
- https://discuss.hashicorp.com/t/hcsec-2025-24-vault-denial-of-service-though-complex-json-payloads/76393
- https://github.com/openbao/openbao/blob/788536bd3e10818a7b4fb00aac6affc23388e5a9/http/logical.go#L50
- https://nvd.nist.gov/vuln/detail/CVE-2025-59043
- https://github.com/openbao/openbao/pull/1756
- https://github.com/openbao/openbao/commit/d418f238bc99adc72c73109faf574cc2b672880c
- https://github.com/advisories/GHSA-g46h-2rq9-gw5m
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-63131
OpenBao Skips Stricter Deny Policy for LIST operations
medium6.0No fixSep 22, 2026CVE-2026-63132
OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack
critical9.1No fixSep 22, 2026CVE-2026-71543
OpenBao's Templated Policies Allow Privilege Escalation via Wildcard Characters
high7.5No fixSep 22, 2026CVE-2026-77285
OpenBao Agent Writes Secrets to Stdout
low2.4No fixSep 22, 2026CVE-2026-55770
OpenBao: LDAPi ldaputil (wrong escape func)
medium6.8No fixJun 19, 2026CVE-2026-55774
OpenBao: Cross-namespace lease revocation/renewal via canonical sys/leases/{revoke,renew} — incomplete fix of CVE-2026-45808
low2.1No fixJun 19, 2026
