How severe is CVE-2023-2121?

CVE-2023-2121 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2023-2121?

CVE-2023-2121 affects the following packages: github.com/hashicorp/vault (Go), github.com/hashicorp/vault (Go), github.com/hashicorp/vault (Go). Ecosystems affected: Go.

How do I fix CVE-2023-2121?

Update github.com/hashicorp/vault to 1.11.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-2121 is resolved across your whole dependency graph.

How do I detect CVE-2023-2121 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/hashicorp/vault, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-2121 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2023-2121 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-2121 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2023-2121?

CVE-2023-2121 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 36th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-2121?

CVE-2023-2121 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2023-2121 published, and has it been updated?

CVE-2023-2121 was published on June 9, 2023 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

CVE-2023-2121 — vault

MEDIUM

CVE-2023-2121 is a medium-severity (CVSS 4.3) Cross-site Scripting (XSS) vulnerability in github.com/hashicorp/vault. A fix is available for github.com/hashicorp/vault — see the affected versions and patch details below.

Vault’s KV Diff Viewer Allowed for HTML Injection

Also known asBIT-vault-2023-2121GHSA-gq98-53rq-qr5hGO-2023-1849

Published

Jun 9, 2023

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-2121.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs36th percentile — riskier than 36% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

🐹github.com/hashicorp/vault🐹github.com/hashicorp/vault🐹github.com/hashicorp/vault

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Vault and Vault Enterprise's (Vault) key-value v2 (kv-v2) diff viewer allowed HTML injection into the Vault web UI through key values. This vulnerability, CVE-2023-2121, is fixed in Vault 1.14.0, 1.13.3, 1.12.7, and 1.11.11.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/hashicorp/vault`	all versions	1.11.11`go get github.com/hashicorp/vault@v1.11.11`
🐹Go	`github.com/hashicorp/vault`	≥ 1.12.0&&< 1.12.7	1.12.7`go get github.com/hashicorp/vault@v1.12.7`
🐹Go	`github.com/hashicorp/vault`	≥ 1.13.0&&< 1.13.3	1.13.3`go get github.com/hashicorp/vault@v1.13.3`

Affected Products

1 product · 6 configurations

Application

vaulthashicorp

≥ 1.13.0 && < 1.13.3

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/hashicorp/vault, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/hashicorp/vault to 1.11.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-2121 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
RHODF-4.14-RHEL-9	`odf4/ocs-rhel9-operator:v4.14.0-67`	RHSA-2023:6832

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2023-2121 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Jun 9, 2023

Last updated

Oct 28, 2026

Identifiers

CVE-2023-2121

GHSA-gq98-53rq-qr5h

BIT-vault-2023-2121

GO-2023-1849

References

Advisorygithub.com · CVE 2023 2121.json Advisorynvd.nist.gov · CVE 2023 2121 Webdiscuss.hashicorp.com Packagegithub.com · vault

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting vault are rated as high or higher (top: high).

CVE-2026-4525CVE-2026-5807CVE-2026-5052CVE-2026-3605CVE-2025-11621CVE-2025-12044CVE-2025-6203CVE-2025-6013

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2023-2121 — vault

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2023-2121 in your dependencies?