Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.new Create a CVE report
Check your stack
CVE-2026-115362low2.2

OpenBao before 2.6.4 and 2.7.0 before 2.7.1 Expired AppRole SecretID Authentication Bypass

Impact

OpenBao versions before 2.6.4 and 2.7.x before 2.7.1 do not check Secret ID expiration, allowing attackers with an expired Secret ID to log in. An attacker must have an expired, untidied Secret ID. The impact is gaining access beyond the ID's TTL.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Affected packages

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

openbao · VulnCheck

openbao

4 ranges
VulnCheck version evidence

Package identity

pkg:golang/github.com/openbao/openbao/v2Explore github.com/openbao/openbao/v2 →

Identity supplied by VulnCheck. Version matching requires compatible range evidence.

Compare with this publisher’s ranges. This does not inspect your installation.

affected

0 → before 2.6.4

semver versions

2.7.0 → before 2.7.1

semver versions

unaffected

2.6.4

semver versions

2.7.1

semver versions

unknown

Other versions: unaffected

Original source description

OpenBao before 2.6.4 and 2.7.x before 2.7.1 does not check Secret ID expiration at use in the AppRole auth method, leaving expired Secret IDs valid until the periodic tidy removes them. An attacker holding an expired, untidied Secret ID can log in and gain access beyond its TTL.

Inside the record

Evidence available

Package identity
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-115362

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-613 ↗

Insufficient Session Expiration

VulnCheck

Related →

Environment requirements

These conditions apply together as specified by the publisher. A matching product name alone does not establish exposure.

VulnCheck · platform conditions

Any condition may hold

Vulnerable product

cpe:2.3:a:openbao:openbao:*:*:*:*:*:*:*:*

Before: 2.6.4

Vulnerable product

cpe:2.3:a:openbao:openbao:*:*:*:*:*:*:*:*

From (inclusive): 2.7.0

Before: 2.7.1

Original applicability statements
[
  {
    "nodes": [
      {
        "operator": "OR",
        "negate": false,
        "cpeMatch": [
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:a:openbao:openbao:*:*:*:*:*:*:*:*",
            "versionEndExcluding": "2.6.4"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:a:openbao:openbao:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "2.7.0",
            "versionEndExcluding": "2.7.1"
          }
        ]
      }
    ]
  }
]
Contributing organizations · 2
VulnCheck

Assigning organization

2026-10-22
CISA-ADP

Additional data publisher

2026-10-29

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

References

2 sources
github.com/openbao/openbao/security/advisories/GHSA-7m59-mp95-w6ph
vendor-advisoryVulnCheck
www.vulncheck.com/advisories/openbao-before-2.6.4-and-2.7.0-before-2.7.1-expired-approle-secretid-authentication-bypass
third-party-advisoryVulnCheck