Nomad vulnerable to cross-namespace information disclosure in multiple endpoints
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.1.1, 1.10.18
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
HashiCorp Nomad and Nomad Enterprise are affected by this flaw, which lets a user with read access in one namespace view information about objects in other namespaces through several read-only API endpoints. The impact is unauthorized disclosure of data across namespace boundaries.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
HashiCorp Nomad and Nomad Enterprise are vulnerable to cross-namespace authorization bypasses in several read-only API endpoints that may allow an authenticated user with read permissions in one namespace to view information about objects in other namespaces. This vulnerability (CVE-2026-102260) is fixed in Nomad Community Edition 2.1.1 and Nomad Enterprise 2.1.0, 1.11.12, and 1.10.18.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- HashiCorp Nomad
From 0.11.0 · fixed in 2.1.1
- HashiCorp Nomad Enterprise
From 0.11.0 · fixed in 1.10.18