CVE-2026-50577
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NSummary
CVE-2026-50577 is a high-severity Reusing a Nonce, Key Pair in Encryption (CWE-323) vulnerability in Machinespirits (inferred from references). Its CVSS base score is 7.4 (High).
Operationally, ranked at the 24th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-61057
Vulnerability Data
ePA 3.x Integration implements the authorization workflow and writes Medical Information Objects to Germany's electronic patient record. Prior to 1.3.0, ePA 3.x Integration leaves request_counter unchanged in app/vau/VAUProtokoll.py while constructing VAU messages. The frozen client request counter causes the server…
more
side to reuse AES-GCM nonce and key combinations across responses. A network attacker who collects repeated ciphertexts can recover the XOR of plaintexts and use predictable inner HTTP headers and JSON fields to recover sensitive data, including patient health records. Repeated nonces can also enable recovery of the GHASH authentication key through the Joux forbidden attack, allowing forged AES-GCM messages and injection of malicious responses. The response-counter check also fails to maintain last_response_counter, weakening replay and ordering validation. This issue is fixed in version 1.3.0.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.8.3V11.3.4
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover nonce reuse through static analysis, fuzzing, or known-answer tests.
Engineering principles include correct use of cryptographic primitives such as unique nonces per key.
Selecting and implementing appropriate cryptographic algorithms and modes reduces nonce-reuse exposure.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent nonce/key reuse errors in cryptographic implementations.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Mandates proper cryptographic key and nonce management, directly preventing nonce/key-pair reuse.
Security testing can detect nonce reuse, yet the control addresses many other issues beyond this CWE.
Secure-coding rules can require unique nonces, but the control is broader than this single weakness.