Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-41164 medium CVSS 4.4

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``.

AI summary snake-internal / snake-material-v2

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.
❓ What is the problem
**A vulnerability** (CWE-345) exists in github.com/nuts-foundation/nuts-node. Attackers reach the vulnerable code path via ``iss`` without authentication.
📍 Affected scope
github.com/nuts-foundation/nuts-node — . Attack surface: `iss` / `sub` / `service` / `typ`.
🔥 Severity
Severity: Medium (CVSS 4.4/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
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,
🔍 Detection
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 (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify 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 し、稼働しているサービス・バージョンを把握する。

  2. 5
    Apply 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 `service` is empty, where `iss` is empty or does not match the expected authorizer DID, を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 7
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/nuts-foundation/nuts-node
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"1.1.0"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →