Vulnerability in github.com/nuts-foundation/nuts-node (CVE-2026-41164)
Summary
Vulnerability in github.com/nuts-foundation/nuts-node (CVE-2026-41164). Risk of unauthorized operations or information disclosure. Exploitable via iss.
Original description
The description as published by the source.
nuts-node is the reference implementation of the Nuts specification. Prior to 6.2.3 and 5.4.31, the v1 access token introspection endpoint (/auth/v1/introspect_access_token) accepts any JWT signed by a key present on the node, without validating the JWT type, issuer-to-key binding, or required claims. This allows a Verifiable Presentation (VP) JWT to be replayed as an access token and receive an active: true introspection response. This vulnerability is fixed in 6.2.3 and 5.4.31.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-41164 has been found in github.com/nuts-foundation/nuts-node.
Attackers can target a specific entry point like iss over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "github.com/nuts-foundation/nuts-node CVE-2026-41164" on the vendor's site.
CVE-2026-41164 (github.com/nuts-foundation/nuts-node) — CWE-345 / CVSS v3 4.4
Attack vector: remote (network-reachable)
Attack surface: iss / sub / service / typ
Workaround: If users are unable to update their nuts-node, resource servers can mitigate this risk by explicitly validating the introspection response: reject responses where service is empty, where iss is empty or does not match the expected authorizer DID,
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-345) exists in github.com/nuts-foundation/nuts-node. Attackers reach the vulnerable code path via iss.
Check the vendor advisory for the affected versions of github.com/nuts-foundation/nuts-node. Attack surface: iss / sub / service / typ.
Severity: Medium (CVSS 4.4/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Workaround: If users are unable to update their nuts-node, resource servers can mitigate this risk by explicitly validating the introspection response: reject responses where service is empty, where iss is empty or does not match the expected authorizer DID,
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/nuts-foundation/nuts-node' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/nuts-foundation/nuts-node' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/nuts-foundation/nuts-nodeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
If users are unable to update their nuts-node, resource servers can mitigate this risk by explicitly validating the introspection response: reject responses where `service` is empty, where `iss` is empty or does not match the expected authorizer DID,パッチが適用されるまでの応急処置として、If users are unable to update their nuts-node, resource servers can mitigate this risk by explicitly validating the introspection response: reject responses where
serviceis empty, whereissis empty or does not match the expected authorizer DID, を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com