How severe is GHSA-8xmx-h8rq-h94j?

GHSA-8xmx-h8rq-h94j has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-8xmx-h8rq-h94j?

GHSA-8xmx-h8rq-h94j affects the following packages: github.com/hashicorp/consul (Go), github.com/hashicorp/consul (Go), github.com/hashicorp/consul (Go). Ecosystems affected: Go.

How do I fix GHSA-8xmx-h8rq-h94j?

Update github.com/hashicorp/consul to 1.9.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8xmx-h8rq-h94j is resolved across your whole dependency graph.

How do I detect GHSA-8xmx-h8rq-h94j in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/hashicorp/consul. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-8xmx-h8rq-h94j 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.

How does O3 Security protect against GHSA-8xmx-h8rq-h94j?

O3 pinpoints whether GHSA-8xmx-h8rq-h94j is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-8xmx-h8rq-h94j actively exploited in the wild?

No public exploit code has been indexed for GHSA-8xmx-h8rq-h94j 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 GHSA-8xmx-h8rq-h94j?

GHSA-8xmx-h8rq-h94j has an EPSS (Exploit Prediction Scoring System) score of 6.1%, placing it in the 92th 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 GHSA-8xmx-h8rq-h94j?

GHSA-8xmx-h8rq-h94j 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.

Is there exploit tooling available for GHSA-8xmx-h8rq-h94j?

A Nuclei detection template exists for GHSA-8xmx-h8rq-h94j, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-8xmx-h8rq-h94j published, and has it been updated?

GHSA-8xmx-h8rq-h94j was published on May 24, 2022 and was last updated on February 4, 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

GHSA-8xmx-h8rq-h94j

MEDIUM

HashiCorp Consul Cross-site Scripting vulnerability

Also known asBIT-consul-2020-25864CVE-2020-25864GO-2023-1851

Published

May 24, 2022

Updated

Feb 4, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

6.1%probability of exploitation in next 30 days

Lower Risk92th percentile-70.61%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

3 pkgs affected

🐹github.com/hashicorp/consul🐹github.com/hashicorp/consul🐹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

HashiCorp Consul and Consul Enterprise up to version 1.9.4 key-value (KV) raw mode was vulnerable to cross-site scripting. Fixed in 1.9.5, 1.8.10 and 1.7.14.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/hashicorp/consul`	≥ 1.9.0&&< 1.9.5	1.9.5
🐹Go	`github.com/hashicorp/consul`	≥ 1.8.0&&< 1.8.10	1.8.10
🐹Go	`github.com/hashicorp/consul`	all versions	1.7.14

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/hashicorp/consul to 1.9.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8xmx-h8rq-h94j 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.
How O3 protects you
O3 pinpoints whether GHSA-8xmx-h8rq-h94j is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-8xmx-h8rq-h94j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

HashiCorp Consul and Consul Enterprise up to version 1.9.4 key-value (KV) raw mode was vulnerable to cross-site scripting. Fixed in 1.9.5, 1.8.10 and 1.7.14.

O3 Security · Impact-Aware SCA

Is GHSA-8xmx-h8rq-h94j in your dependencies?

O3 detects GHSA-8xmx-h8rq-h94j across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works