Menu

Star on GitHub · 3.4k

CVE-2026-115362

2.2 · LOW

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.

Published Oct 22, 2026CWE-613EPSS 0.20%

Overview

CVE-2026-115362 is a low-severity vulnerability. It was published on October 22, 2026 and has a CVSS 3.1 base score of 2.2 (LOW).

This vulnerability has a CVSS 3.1 base score of 2.2, rated LOW. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-115362?

CVE-2026-115362 is a low-severity vulnerability. It was published on October 22, 2026 and has a CVSS 3.1 base score of 2.2 (LOW).

How severe is CVE-2026-115362?

This vulnerability has a CVSS 3.1 base score of 2.2, rated LOW. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-115362?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-115362?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-115362 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related LOW CVEs from 2026

View all
Watch the demo →