How severe is CVE-2026-7474?

CVE-2026-7474 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-7474?

CVE-2026-7474 affects the following packages: github.com/hashicorp/nomad (Go). Ecosystems affected: Go.

How do I fix CVE-2026-7474?

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 CVE-2026-7474 is resolved across your whole dependency graph.

How do I detect CVE-2026-7474 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 CVE-2026-7474 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 CVE-2026-7474?

O3 pinpoints whether CVE-2026-7474 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 CVE-2026-7474 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-7474 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 CVE-2026-7474 published, and has it been updated?

CVE-2026-7474 was published on May 12, 2026 and was last updated on July 31, 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

CVE-2026-7474

HIGH

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

Nomad vulnerable to path traversal in dynamic host volume which may lead to code execution

Also known asGHSA-hx53-77qj-8663GO-2026-5445

Published

May 12, 2026

Updated

Jul 31, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jul 31, 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 CVE-2026-7474 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 CVE-2026-7474 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 CVE-2026-7474. 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 CVE-2026-7474 in your dependencies?

O3 detects CVE-2026-7474 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