CVE-2025-0937

CVE-2025-0937 is a high-severity vulnerability in Hashicorp Nomad with a CVSS 3.x base score of 7.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-863.

Key facts

Description

Nomad Community and Nomad Enterprise ("Nomad") event stream configured with a wildcard namespace can bypass the ACL Policy allowing reads on other namespaces.

Frequently asked questions

What is CVE-2025-0937?
Nomad Community and Nomad Enterprise ("Nomad") event stream configured with a wildcard namespace can bypass the ACL Policy allowing reads on other namespaces.
How severe is CVE-2025-0937?
CVE-2025-0937 has a CVSS 3.x base score of 7.1, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity low, and availability none.
Is CVE-2025-0937 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (33rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-0937?
CVE-2025-0937 primarily affects Hashicorp Nomad. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2025-0937?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-0937 have an EU (EUVD) identifier?
Yes. CVE-2025-0937 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-1934.
When was CVE-2025-0937 published?
CVE-2025-0937 was published on 2025-02-12 and last updated on 2026-06-17.

References

Affected products (2)

More vulnerabilities in Hashicorp Nomad

All CVEs affecting Hashicorp Nomad →

Other CWE-863 (Incorrect Authorization) vulnerabilities

Browse all CWE-863 (Incorrect Authorization) vulnerabilities →