How severe is GHSA-35qp-xq9f-2rjx?

GHSA-35qp-xq9f-2rjx has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-35qp-xq9f-2rjx?

GHSA-35qp-xq9f-2rjx affects the following packages: github.com/hashicorp/nomad (Go), github.com/hashicorp/nomad (Go). Ecosystems affected: Go.

How do I fix GHSA-35qp-xq9f-2rjx?

Update github.com/hashicorp/nomad to 1.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-35qp-xq9f-2rjx is resolved across your whole dependency graph.

How do I detect GHSA-35qp-xq9f-2rjx in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/hashicorp/nomad, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-35qp-xq9f-2rjx 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.

Is GHSA-35qp-xq9f-2rjx actively exploited in the wild?

No public exploit code has been indexed for GHSA-35qp-xq9f-2rjx 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-35qp-xq9f-2rjx?

GHSA-35qp-xq9f-2rjx has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 73th 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.

When was GHSA-35qp-xq9f-2rjx published, and has it been updated?

GHSA-35qp-xq9f-2rjx was published on June 24, 2021 and was last updated on August 21, 2024. 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

Improper Privilege Management in HashiCorp NomadGHSA-35qp-xq9f-2rjx

HIGH

GHSA-35qp-xq9f-2rjx is a high-severity (CVSS 7.5) vulnerability in github.com/hashicorp/nomad. A fix is available for github.com/hashicorp/nomad — see the affected versions and patch details below.

Also known asCVE-2021-3283GO-2022-0622

Published

Jun 24, 2021

Updated

Aug 21, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs73th percentile — riskier than 73% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-35qp-xq9f-2rjx by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected

🐹github.com/hashicorp/nomad🐹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 up to 0.12.9 exec and java task drivers can access processes associated with other tasks on the same node. Fixed in 0.12.10, and 1.0.3.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/hashicorp/nomad`	≥ 1.0.0&&< 1.0.3	1.0.3`go get github.com/hashicorp/nomad@v1.0.3`
🐹Go	`github.com/hashicorp/nomad`	all versions	0.12.10`go get github.com/hashicorp/nomad@v0.12.10`

Affected Products

1 product · 4 configurations

Application

nomadhashicorp

≥ 1.0.0 && < 1.0.3

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/nomad, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/hashicorp/nomad to 1.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-35qp-xq9f-2rjx 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.

Frequently Asked Questions

HashiCorp Nomad and Nomad Enterprise up to 0.12.9 exec and java task drivers can access processes associated with other tasks on the same node. Fixed in 0.12.10, and 1.0.3.

O3 Security · Impact-Aware SCA

Is GHSA-35qp-xq9f-2rjx in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works