Is CVE-2025-59048 exploited in the wild?

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

How severe is CVE-2025-59048?

High severity, with a CVSS score of 8.1, published 23 October 2025.

Which products and versions are affected?

github.com/openbao/openbao-plugins (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=0.1.1.

Is there a fix for CVE-2025-59048?

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

Am I affected by CVE-2025-59048?

Check whether you run github.com/openbao/openbao-plugins (Go) or OpenBao Aws Plugin 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-2025-59048: OpenBao AWS Plugin Vulnerable to Cross-Account IAM Role Impersonation in AWS Auth Method

CVE-2025-59048 · Severity: high · CVSS 8.1 · Published 2025-10-23

OpenBao's AWS Plugin generates AWS access credentials based on IAM policies. Prior to version 0.1.1, the AWS Plugin is vulnerable to cross-account IAM role Impersonation in the AWS auth method. The vulnerability allows an IAM role from an untrusted AWS account to authenticate by impersonating a role with the same name in a trusted account, leading to unauthorized access. This impacts all users of the auth-aws plugin who operate in a multi-account AWS environment where IAM role names may not be unique across accounts. This vulnerability has been patched in version 0.1.1 of the auth-aws plugin. A workaround for this issue involves guaranteeing that IAM role names are unique across all AWS accounts that could potentially interact with your OpenBao environment, and to audit for any duplicate IAM roles.

Vendors: Go, OpenBao.

Quick answers

Is CVE-2025-59048 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-59048 being exploited in the wild.
How severe is CVE-2025-59048?: High severity, with a CVSS score of 8.1, published 23 October 2025.
Which products and versions are affected?: github.com/openbao/openbao-plugins (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=0.1.1.
Is there a fix for CVE-2025-59048?: Yes. github.com/openbao/openbao-plugins (Go): upgrade to 0.1.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-59048?: Check whether you run github.com/openbao/openbao-plugins (Go) or OpenBao Aws Plugin 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-plugins (Go): upgrade to 0.1.1 or later
```
go get github.com/openbao/openbao-plugins@v0.1.1
```

Affected products

github.com/openbao/openbao-plugins (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=0.1.1
OpenBao Aws Plugin

Identifiers

CVE-2025-59048
GHSA-jp7h-4f3c-9rc7
GO-2025-4067

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