How severe is CVE-2023-0845?

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

Which packages are affected by CVE-2023-0845?

CVE-2023-0845 affects the following packages: github.com/hashicorp/consul (Go). Ecosystems affected: Go.

How do I fix CVE-2023-0845?

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

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

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

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

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

No public exploit code has been indexed for CVE-2023-0845 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-0845?

CVE-2023-0845 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 63th 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-0845?

CVE-2023-0845 is classified as NULL Pointer Dereference (CWE-476). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2023-0845 was published on March 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-0845 — consul

MEDIUM

CVE-2023-0845 is a medium-severity (CVSS 4.9) NULL Pointer Dereference vulnerability in github.com/hashicorp/consul. A fix is available for github.com/hashicorp/consul — see the affected versions and patch details below.

Consul Server Panic when Ingress and API Gateways Configured with Peering

Also known asBIT-consul-2023-0845GHSA-wj6x-hcc2-f32jGO-2023-1639

Published

Mar 9, 2023

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 3, 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-0845.

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs63th percentile — riskier than 63% 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

1 pkg affected

🐹github.com/hashicorp/consul

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

A vulnerability was identified in Consul and Consul Enterprise (“Consul”) an authenticated user with service:write permissions could trigger a workflow that causes Consul server and client agents to crash under certain circumstances. To exploit this vulnerability, an attacker requires access to an ACL token with service:write permissions, and there needs to be at least one running ingress or API gateway that is configured to route traffic to an upstream service.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/hashicorp/consul`	≥ 1.14.0&&< 1.14.5	1.14.5`go get github.com/hashicorp/consul@v1.14.5`

Affected Products

1 product · 1 configurations

Application

consulhashicorp

< 1.14.5

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/consul, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/hashicorp/consul to 1.14.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-0845 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2023-0845 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works