How severe is GHSA-q6h7-4qgw-2j9p?

GHSA-q6h7-4qgw-2j9p has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-q6h7-4qgw-2j9p?

GHSA-q6h7-4qgw-2j9p 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-q6h7-4qgw-2j9p?

Update github.com/hashicorp/consul to 1.9.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q6h7-4qgw-2j9p is resolved across your whole dependency graph.

How do I detect GHSA-q6h7-4qgw-2j9p 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 GHSA-q6h7-4qgw-2j9p if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is GHSA-q6h7-4qgw-2j9p actively exploited in the wild?

No public exploit code has been indexed for GHSA-q6h7-4qgw-2j9p 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-q6h7-4qgw-2j9p?

GHSA-q6h7-4qgw-2j9p has an EPSS (Exploit Prediction Scoring System) score of 8.7%, placing it in the 95th 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-q6h7-4qgw-2j9p?

GHSA-q6h7-4qgw-2j9p is classified as Server-Side Request Forgery (SSRF) (CWE-918). 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-q6h7-4qgw-2j9p?

A Nuclei detection template exists for GHSA-q6h7-4qgw-2j9p, 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-q6h7-4qgw-2j9p published, and has it been updated?

GHSA-q6h7-4qgw-2j9p was published on April 20, 2022 and was last updated on September 10, 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

HIGH severity

Hashicorp Consul HTTP health check endpoints returning an HTTP redirect may be abused as SSRF vectorGHSA-q6h7-4qgw-2j9p

HIGH

GHSA-q6h7-4qgw-2j9p is a high-severity (CVSS 7.5) Server-Side Request Forgery (SSRF) vulnerability in github.com/hashicorp/consul. A fix is available for github.com/hashicorp/consul — see the affected versions and patch details below.

Also known asBIT-consul-2022-29153CVE-2022-29153GO-2022-0615

Published

Apr 20, 2022

Updated

Sep 10, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

8.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% 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/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

A vulnerability was identified in Consul and Consul Enterprise (“Consul”) such that HTTP health check endpoints returning an HTTP redirect may be abused as a vector for server-side request forgery (SSRF). This vulnerability, CVE-2022-29153, was fixed in Consul 1.9.17, 1.10.10, and 1.11.5.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/hashicorp/consul`	all versions	1.9.17`go get github.com/hashicorp/consul@v1.9.17`
🐹Go	`github.com/hashicorp/consul`	≥ 1.10.0&&< 1.10.10	1.10.10`go get github.com/hashicorp/consul@v1.10.10`
🐹Go	`github.com/hashicorp/consul`	≥ 1.11.0&&< 1.11.5	1.11.5`go get github.com/hashicorp/consul@v1.11.5`

Affected Products

2 products · 7 configurations

fedorafedoraproject

1 version

Application

consulhashicorp

≥ 1.11.0 && < 1.11.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.9.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q6h7-4qgw-2j9p is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

How to detect GHSA-q6h7-4qgw-2j9p

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id ghsa-q6h7-4qgw-2j9p -u https://target

Template: HashiCorp Consul/Consul Enterprise - Server-Side Request Forgery
Severity: high
Impact: Successful exploitation of this vulnerability could allow an attacker to send crafted requests to internal resources, leading to unauthorized access or information disclosure.
Remediation: 1) HTTP + interval health check configuration provides a disable_redirects option to prohibit this behavior. 2) Fixed in 1.9.17, 1.10.10, and 1.11.5.

Template by ProjectDiscovery nuclei-templates (c-sh0), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-q6h7-4qgw-2j9p in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works