CVE-2026-19194
CAP JWT claims validation bypass using non-canonical claim names
Description
The HashiCorp cap JWT validation library before version 0.14.0 is vulnerable to a claims validation bypass that may cause downstream applications to make authorization decisions using claim values different from those validated. Exploitation requires attacker-controlled claims in a JWT signed by a key trusted by the application. This vulnerability (CVE-2026-19194) is fixed in cap 0.14.0.
INFO
Published Date :
Nov. 13, 2026, 10:17 p.m.
Last Modified :
Nov. 13, 2026, 10:17 p.m.
Remotely Exploit :
No
Source :
[email protected]
Affected Products
The following products are affected by CVE-2026-19194
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | |||||
| CVSS 3.1 | MEDIUM | 67fedba0-ff2e-4543-ba5b-aa93e87718cc | ||||
| CVSS 3.1 | MEDIUM | [email protected] | ||||
| CVSS 3.1 | MEDIUM | MITRE-CVE |
Solution
- Update the cap JWT validation library to 0.14.0 or later.
- Validate JWT claims carefully before making authorization decisions.
- Ensure JWTs are signed with trusted keys only.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-19194.
| URL | Resource |
|---|---|
| https://discuss.hashicorp.com/t/hcsec-2026-60-cap-jwt-claims-validation-bypass-using-non-canonical-claim-names/78258 |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-19194 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-19194
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-19194 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-19194 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by [email protected]
Nov. 13, 2026
Action Type Old Value New Value Added Description The HashiCorp cap JWT validation library before version 0.14.0 is vulnerable to a claims validation bypass that may cause downstream applications to make authorization decisions using claim values different from those validated. Exploitation requires attacker-controlled claims in a JWT signed by a key trusted by the application. This vulnerability (CVE-2026-19194) is fixed in cap 0.14.0. Added CVSS V3.1 AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N Added CWE CWE-178 Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/19xxx/CVE-2026-19194.json">CVE-2026-19194</a> Added Reference https://discuss.hashicorp.com/t/hcsec-2026-60-cap-jwt-claims-validation-bypass-using-non-canonical-claim-names/78258 -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Nov. 13, 2026
Action Type Old Value New Value Added SSVC {'id': 'CVE-2026-19194', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'none'}, {'automatable': 'no'}, {'technicalImpact': 'total'}], 'version': '2.0.3', 'timestamp': '2026-11-13T21:30:24.747414Z'}