CVE-2026-41164: nuts-node · Insufficient Verification of Data Authenticity
Affects nuts-nodeSource CVE Database V5
Not known to be exploited · CVSS 4.4 Medium : upgrade to 6.2.3 or 5.4.31 when convenient.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.07% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.2.3, 5.4.31
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 26 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade nuts-node to 6.2.3 or 5.4.31; nuts-foundation/nuts-node to 5.4.31.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| nuts-foundationnuts-node | Affected
| Fixed in
|
| nuts-foundationnuts-node | Affected
| Fixed in
|
GitHubnuts-foundation/nuts-nodepkg:github/nuts-foundation/nuts-nodeOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in nuts-node versions 6.2.3 and 5.4.31. Users should upgrade to these or later versions to remediate the issue. Patch status is not explicitly stated as 'official-fix' in the vendor advisory, but the description confirms the fix is included in these versions. No additional mitigation steps are indicated.
Description
CVE-2026-41164 is a medium severity vulnerability in nuts-foundation's nuts-node prior to versions 6.2.3 and 5.4.31. The v1 access token introspection endpoint incorrectly accepts any JWT signed by a key on the node without properly validating the JWT type, issuer-to-key binding, or required claims. This flaw allows a Verifiable Presentation (VP) JWT to be replayed as an access token and receive an active introspection response. The issue is fixed in versions 6.2.3 and 5.