How severe is GHSA-hx53-77qj-8663?

GHSA-hx53-77qj-8663 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-hx53-77qj-8663?

GHSA-hx53-77qj-8663 affects the following packages: github.com/hashicorp/nomad (Go). Ecosystems affected: Go.

How do I fix GHSA-hx53-77qj-8663?

Update github.com/hashicorp/nomad to 1.11.0-rc.1.0.20260511152149-cd7240c4099a or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hx53-77qj-8663 is resolved across your whole dependency graph.

How do I detect GHSA-hx53-77qj-8663 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/hashicorp/nomad. 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-hx53-77qj-8663 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-hx53-77qj-8663?

O3 pinpoints whether GHSA-hx53-77qj-8663 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-hx53-77qj-8663 actively exploited in the wild?

No public exploit code has been indexed for GHSA-hx53-77qj-8663 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.

When was GHSA-hx53-77qj-8663 published, and has it been updated?

GHSA-hx53-77qj-8663 was published on May 12, 2026 and was last updated on June 25, 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

GHSA-hx53-77qj-8663

HIGHFix: hashicorp/nomad@cd7240c

GHSA-hx53-77qj-8663 is a high-severity (CVSS 8.8) remote code execution vulnerability in github.com/hashicorp/nomad. O3 Security confirms whether GHSA-hx53-77qj-8663 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

HashiCorp Nomad vulnerable to a path traversal

Also known asCVE-2026-7474GO-2026-5445

Published

May 12, 2026

Updated

Jun 25, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jun 25, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/hashicorp/nomad

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 Nomad and Nomad Enterprise prior to 2.0.1 are vulnerable to code execution on the client host through a path traversal attack. This vulnerability (CVE-2026-7474) is fixed in Nomad 2.0.1, 1.11.5 and 1.10.11.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/hashicorp/nomad`	all versions	1.11.0-rc.1.0.20260511152149-cd7240c4099a

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/nomad. 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/nomad to 1.11.0-rc.1.0.20260511152149-cd7240c4099a or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hx53-77qj-8663 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-hx53-77qj-8663 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-hx53-77qj-8663. 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-hx53-77qj-8663 in your dependencies?

O3 detects GHSA-hx53-77qj-8663 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