NVD / CVE Program· CNA HashiCorp

CVE-2023-25000: Vault Vulnerable to Cache-Timing Attacks During Seal and Unseal Operations

MediumCVSS 4.7 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 18/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.21% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: HashiCorp Vault 1.11.0, 1.11.9, 1.12.5; HashiCorp Vault Enterprise 1.11.0, 1.11.9, 1.12.5.

Low priority for now. Upgrade to HashiCorp Vault 1.11.0, 1.11.9, 1.12.5; HashiCorp Vault Enterprise 1.11.0, 1.11.9, 1.12.5 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

HashiCorp Vault's implementation of Shamir's secret sharing used precomputed table lookups, and was vulnerable to cache-timing attacks. An attacker with access to, and the ability to observe a large number of unseal operations on the host through a side channel may reduce the search space of a brute force effort to recover the Shamir shares. Fixed in Vault 1.13.1, 1.12.5, and 1.11.9.

Published: Mar 29, 2023
Updated: Jun 17, 2026
EPSS: 0.2% · 11th percentile
CWE: CWE-208

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 18 / 40 · 4.7 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 4.7
CNA · HashiCorp: 5.0; 0.3 point gap

CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:N/A: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.

Is your version affected? Check it

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 help

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

Vendor	Product	CPE
hashicorp	vault	cpe:2.3:a:hashicorp:vault

Versions reported by the vendor

Affected version ranges reported by the assigning authority (HashiCorp). Independent of NVD's CPE analysis and usually ahead of it.

HashiCorp Vault
- 1.13.0 and later · before 1.13.1affected · semver
- 1.12.0 and later · before 1.12.5affected · semver
- 1.11.0 and later · before 1.11.9affected · semver
- before 1.11.0affected · semver
HashiCorp Vault Enterprise
- 1.13.0 and later · before 1.13.1affected · semver
- 1.12.0 and later · before 1.12.5affected · semver
- 1.11.0 and later · before 1.11.9affected · semver
- before 1.11.0affected · semver

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

hashicorp vaultbefore 1.11.9
hashicorp vault1.12.0 and later · before 1.12.5
hashicorp vault1.13.0 and later · before 1.13.1

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Go	github.com/hashicorp/vault	from 1.12.0 · before 1.12.5	1.12.5
Go	github.com/hashicorp/vault	from 1.13.0 · before 1.13.1	1.13.1
Go	github.com/hashicorp/vault	before 1.11.9	1.11.9

Same product

hashicorp: all records

Other highest-scoring records for the same primary product.

CVE-2020-35192The official vault docker images before 0.11.6 contain a blank password for a root user.
40Plan
CVE-2024-2048Vault Cert Auth Method Did Not Correctly Validate Non-CA Certificates
39Monitor
CVE-2020-12757HashiCorp Vault and Vault Enterprise 1.4.0 and 1.4.1, when configured with the GCP Secrets Engine, may incorrectly generate GCP Credentials…
39Monitor

Published before and after this one in the same product

← EarlierCVE-2023-0620Mar 29, 2023 · Vault Vulnerable to SQL Injection When Configuring the Microsoft SQL Database Storage Backend
26Monitor
← EarlierCVE-2023-0665Mar 29, 2023 · Vault PKI Issuer Endpoint Did Not Correctly Authorize Access to Issuer Metadata
26Monitor
Later →CVE-2023-2197May 1, 2023 · Vault Enterprise Vulnerable to Padding Oracle Attacks When Using a CBC-based Encryption Mechanism with a HSM
10Monitor

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
HashiCorp Vault	1.11.0	Vendor (CNA)
HashiCorp Vault	1.11.9	Vendor (CNA)
HashiCorp Vault	1.12.5	Vendor (CNA)
HashiCorp Vault	1.13.1	Vendor (CNA)
HashiCorp Vault Enterprise	1.11.0	Vendor (CNA)
HashiCorp Vault Enterprise	1.11.9	Vendor (CNA)
HashiCorp Vault Enterprise	1.12.5	Vendor (CNA)
HashiCorp Vault Enterprise	1.13.1	Vendor (CNA)
Go:github.com/hashicorp/vault	1.11.9	Package registry (OSV)
Go:github.com/hashicorp/vault	1.12.5	Package registry (OSV)
Go:github.com/hashicorp/vault	1.13.1	Package registry (OSV)

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.