Is CVE-2026-55774 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-55774 being exploited in the wild.

How severe is CVE-2026-55774?

Medium severity, with a CVSS score of 4, published 15 September 2026.

Which products and versions are affected?

github.com/openbao/openbao (Go) SEMVER:introduced=0,fixed=0.0.0-20260617103932-b20b999dd404,introduced=0.1.0, SEMVER:introduced=0.1.0,last_affected=2.5.4; OpenBao >= 0.1.0, <= 2.5.4.

Is there a fix for CVE-2026-55774?

Yes. github.com/openbao/openbao (Go): upgrade to 0.0.0-20260617103932-b20b999dd404 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-55774 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-55774?

Check whether you run github.com/openbao/openbao (Go) or OpenBao at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-55774: OpenBao cross-namespace lease revocation and renewal bypass

Q: Is there a fix for CVE-2026-55774?

Yes. github.com/openbao/openbao (Go): upgrade to 0.0.0-20260617103932-b20b999dd404 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-55774 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-55774?

Check whether you run github.com/openbao/openbao (Go) or OpenBao at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-55774 · Severity: medium · CVSS 4 · Published 2026-09-15

OpenBao is a security tool used to manage sensitive credentials and secrets across different organizational groups (namespaces). A vulnerability exists where a user in one group can prematurely cancel or renew security credentials belonging to a different group if they know the specific credential ID. This could lead to service disruptions or unauthorized access changes if credential identifiers are leaked between tenants.

Technologies: github.com/openbao/openbao (Go), OpenBao. Vendors: Go, OpenBao.

Quick answers

Is CVE-2026-55774 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-55774 being exploited in the wild.
How severe is CVE-2026-55774?: Medium severity, with a CVSS score of 4, published 15 September 2026.
Which products and versions are affected?: github.com/openbao/openbao (Go) SEMVER:introduced=0,fixed=0.0.0-20260617103932-b20b999dd404,introduced=0.1.0, SEMVER:introduced=0.1.0,last_affected=2.5.4; OpenBao >= 0.1.0, <= 2.5.4.
Is there a fix for CVE-2026-55774?: Yes. github.com/openbao/openbao (Go): upgrade to 0.0.0-20260617103932-b20b999dd404 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-55774 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-55774?: Check whether you run github.com/openbao/openbao (Go) or OpenBao at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/openbao/openbao (Go): upgrade to 0.0.0-20260617103932-b20b999dd404 or later
```
go get github.com/openbao/openbao@v0.0.0-20260617103932-b20b999dd404
```

Technical details

An authorization bypass vulnerability exists in OpenBao's lease management system due to an incomplete fix for a previous issue. Users with access to the 'sys/leases/revoke/:lease_id' or 'sys/leases/renew/:lease_id' endpoints can perform actions on leases outside their own namespace. The root cause is a failure to properly enforce namespace boundaries when processing lease identifiers at these canonical endpoints. An attacker with high privileges in one namespace who obtains a lease ID from another namespace can trigger unauthorized revocation or renewal. This issue is addressed in OpenBao v2.5.5.

Affected products

OpenBao OpenBao >= 0.1.0, <= 2.5.4

Identifiers

CVE-2026-55774
GHSA-c36x-h252-g9x2
GO-2026-5304

Timeline

2026-06-19: advisory: GitHub Advisory GHSA-c36x-h252-g9x2 published
2026-06-19: disclosed
2026-06-17: patched: Fix committed to repository

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.