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

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.

Published: 2022-11-10 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-3867 is rated Low Risk (23.8/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.46%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-3867

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.18% 0.46% +0.29%
2 2025-11-15 0.28% 0.18% -0.10%
3 2025-11-11 — 0.28% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-3867

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
2.7 3.1 LOW
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 1.2 1.4 [email protected]
4.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 1.4 [email protected]

Weakness enumeration for CVE-2022-3867

GitHub Security Advisory for CVE-2022-3867

GHSA-9fmc-5fq4-5jwh · Severity: low · Ecosystem: go — HashiCorp Nomad vulnerable to Insufficient Session Expiration

OS Trackers for CVE-2022-3867

vendor priority summary link
ubuntu medium CVE-2022-3867 medium priority: Ubuntu including 1 source packages (nomad), 7 status rows across 7 suites (bionic, focal, jammy, kinetic, trusty, upstream, xenial): DNE 2, ignored 2, needs-triage 2, released 1. https://ubuntu.com/security/CVE-2022-3867

Affected software / configurations for CVE-2022-3867

Vendor Product Version Raw CPE
hashicorp nomad 1.4.0 cpe:2.3:a:hashicorp:nomad:1.4.0:*:*:*:*:*:*:*
hashicorp nomad 1.4.0 cpe:2.3:a:hashicorp:nomad:1.4.0:*:*:*:enterprise:*:*:*
hashicorp nomad 1.4.1 cpe:2.3:a:hashicorp:nomad:1.4.1:*:*:*:*:*:*:*
hashicorp nomad 1.4.1 cpe:2.3:a:hashicorp:nomad:1.4.1:*:*:*:enterprise:*:*:*

References for CVE-2022-3867

cvelogic Threat Intelligence