How severe is GHSA-9rhf-q362-77mx?

GHSA-9rhf-q362-77mx has a CVSS score of 7.4/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-9rhf-q362-77mx?

GHSA-9rhf-q362-77mx affects the following packages: github.com/hashicorp/consul (Go). Ecosystems affected: Go.

How do I fix GHSA-9rhf-q362-77mx?

Update github.com/hashicorp/consul to 1.16.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9rhf-q362-77mx is resolved across your whole dependency graph.

How do I detect GHSA-9rhf-q362-77mx 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-9rhf-q362-77mx 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-9rhf-q362-77mx?

O3 pinpoints whether GHSA-9rhf-q362-77mx 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-9rhf-q362-77mx actively exploited in the wild?

No public exploit code has been indexed for GHSA-9rhf-q362-77mx 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 type of vulnerability is GHSA-9rhf-q362-77mx?

GHSA-9rhf-q362-77mx is classified as CWE-266 (CWE-266). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-9rhf-q362-77mx published, and has it been updated?

GHSA-9rhf-q362-77mx was published on August 9, 2023 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-9rhf-q362-77mx

HIGH

GHSA-9rhf-q362-77mx is a high-severity (CVSS 7.4) CWE-266 vulnerability in github.com/hashicorp/consul. O3 Security confirms whether GHSA-9rhf-q362-77mx is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Consul JWT Auth in L7 Intentions Allow for Mismatched Service Identity and JWT Providers

Also known asBIT-consul-2023-3518CVE-2023-3518GO-2024-2704

Published

Aug 9, 2023

Updated

Feb 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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 such that using JWT authentication for service mesh incorrectly allows/denies access regardless of service identities. This vulnerability, CVE-2023-3518, affects Consul 1.16.0 and was fixed in 1.16.1.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/hashicorp/consul`	≥ 1.16.0&&< 1.16.1	1.16.1

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.16.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9rhf-q362-77mx 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-9rhf-q362-77mx 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-9rhf-q362-77mx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-9rhf-q362-77mx in your dependencies?

O3 detects GHSA-9rhf-q362-77mx 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