Tóm tắt nhanh
- CVE-2026-55774 là lỗ hổng mức THẤP (CVSS 2.1) ảnh hưởng github.com/openbao/openbao.
- Xác suất bị khai thác trong 30 ngày tới (EPSS): 0.56%, cao hơn 46.7% các lỗ hổng khác.
- Cách xử lý: cập nhật lên 0.0.0-20260617103932-b20b999dd404 hoặc mới hơn.
| Gói / sản phẩm | Phiên bản bị ảnh hưởng | Phiên bản đã vá |
|---|
| github.com/openbao/openbao Go | ≥ 0.1.0, ≤ 2.5.4≥ 0.1.0< 0.0.0-20260617103932-b20b999dd404
| 0.0.0-20260617103932-b20b999dd404
|
Mô tả
Summary
OpenBao users with access to the sys/leases/revoke/:lease_id endpoint in any namespace can revoke leases in any other namespace as long as the lease identifier is known to them, bypassing ACLs that should apply for cross-namespace revocations.
Impact
OpenBao's namespaces provide multi-tenant separation. A tenant who intentionally leaks lease identifiers can have their lease and underlying credential revoked by a user in another tenant.
Patch
This will be fixed in OpenBao v2.5.5.
References
This vulnerability is similar to but distinct from:
- CVE-2026-45808 / GHSA-v8v8-cm84-m686
- CVE-2026-40264 / GHSA-p49j-v9wc-wg57
Mô tả của NVD
OpenBao is an open source identity-based secrets management system. Prior to 2.5.5, an OpenBao user with access to sys/leases/revoke/:lease_id in one namespace could revoke a lease in another namespace when the foreign lease_id was known, bypassing namespace ACL isolation. The affected lease lookup routing in vault/expiration.go allowed FetchLeaseInfo and loadEntry to resolve cached or stored lease data outside the request namespace, allowing a tenant that intentionally disclosed a lease identifier to have the lease and its underlying credential revoked by another tenant. This issue is fixed in version 2.5.5.
Bạn đang dùng một trong các sản phẩm này? Quét site để biết có đang lộ phiên bản có lỗ hổng không.
Quét site miễn phí