Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-40092 high CVSS 7.5

Vulnerability in nimiq-keys (CVE-2026-40092)

Summary

vulnerability in nimiq-keys (CVE-2026-40092). Risk of unauthorized operations or information disclosure. Exploitable via ``TaggedPublicKey``.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-40092** has been found in nimiq-keys. Attackers can target a specific entry point like ``TaggedPublicKey`` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10. What to do: apply the vendor's official patched release. If unsure, ask your IT team or search "nimiq-keys CVE-2026-40092" on the vendor's site.
CVE-2026-40092 (nimiq-keys) — CWE-252 / CVSS v3 7.5 Attack vector: remote (network-reachable) / unauthenticated / no user interaction Attack surface: `TaggedPublicKey` / `Ed25519PublicKey` / `from_bytes` / `false` 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-252) exists in nimiq-keys. Attackers reach the vulnerable code path via ``TaggedPublicKey`` without authentication.
📍 Affected scope
nimiq-keys — . Attack surface: `TaggedPublicKey` / `Ed25519PublicKey` / `from_bytes` / `false`.
🔥 Severity
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'nimiq-keys' .` 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 'nimiq-keys' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `nimiq-keys` を grep し、稼働しているサービス・バージョンを把握する。

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

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

Affected packages

rust nimiq-keys
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
crates.io nimiq-keys
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"0.2.0"}]}]

References

🍪 About cookies

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

Details →