CVE-2026-115358: OpenBao before 2.6.3 Sensitive Data Leak in Audit Log via Malformed Parameters
Noroxi assessment
Priority: Monitor (action score 8/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No special conditions are required; it is repeatable.
- Fixed version: openbao openbao 2.6.3, 2.7.1.
Low priority for now. Upgrade to openbao openbao 2.6.3, 2.7.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
OpenBao before 2.6.3 contains an information disclosure vulnerability that allows attackers to leak sensitive data into audit logs by sending malformed plugin parameters. Attackers can submit requests with malformed TypeKVPair or TypeHeader field values, causing error messages containing sensitive input to be recorded in audit logs.
- Published
- Oct 22, 2026
- Updated
- Oct 29, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- CWE-532
Report tools
Action score
8
Monitor
Low priority for now.
- CVSS
- 8 / 40 · 2.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · VulnCheck
- 2.0
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.
openbao openbao
- 2.6.3, 2.6.3, 2.7.1not affected
- before 2.6.3affected · semver
- before 2.6.3affected · semver
- 2.7.0 and later · before 2.7.1affected · semver
Same product
openbao: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-33758OpenBao has Reflected XSS in its OIDC authentication error message37Monitor
- CVE-2026-63132OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack36Monitor
- CVE-2025-54997OpenBao: Privileged Operator May Execute Code on the Underlying Host36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-115356Oct 22, 2026 · OpenBao before 2.6.4 and 2.7.0 before 2.7.1 Kubernetes Auth Method Token Renewal After Revocation21Monitor
- ← EarlierCVE-2026-115357Oct 22, 2026 · OpenBao before 2.6.4 and 2.7.0 before 2.7.1 Improper Audit Logging of Root Generation and Rekey Responses8Monitor
- Later →CVE-2026-115359Oct 22, 2026 · OpenBao before 2.6.4 and 2.7.0 before 2.7.1 Role-Based Rate Limit Quota Bypass via Request Parsing25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| openbao openbao | 2.6.3 | Vendor (CNA) |
| openbao openbao | 2.7.1 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 6, 2026+14 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- opensec-intelligencereporter
- cipherboyfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-62513365 days apartOpenBao leaks HTTPRawBody in Audit Logs22Monitor
- CVE-2025-62705365 days apartOpenBao and Vault Leak []byte Fields in Audit Logs22Monitor
- CVE-2026-4635876 days apartOpenBao's Inline Auth Incorrectly Redacted Headers21Monitor
- CVE-2025-52893484 days apartOpenBao May Leak Sensitive Information in Logs When Processing Malformed Data18Monitor
- CVE-2026-7728529 days apartOpenBao Agent Writes Secrets to Stdout9Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- P
- Scope
- X
Weakness class (CWE)
CWE-532 · Insertion of Sensitive Information into Log FileCVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
- Exploit maturity— → none
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.