Search

Find a vulnerability

Search criteria

    45 vulnerabilities found for nimiq_proof-of-stake by nimiq

    FKIE_CVE-2026-34063

    Vulnerability from fkie_nvd - Published: 2026-04-22 20:16 - Updated: 2026-10-26 22:10
    Summary
    Nimiq's network-libp2p is a Nimiq network implementation based on libp2p. Prior to version 1.3.0, `network-libp2p` discovery uses a libp2p `ConnectionHandler` state machine. the handler assumes there is at most one inbound and one outbound discovery substream per connection. if a remote peer opens/negotiate the discovery protocol substream a second time on the same connection, the handler hits a `panic!(\"Inbound already connected\")` / `panic!(\"Outbound already connected\")` path instead of failing closed. This causes a remote crash of the networking task (swarm), taking the node's p2p networking offline until restart. The patch for this vulnerability is formally released as part of v1.3.0. No known workarounds are available.
    Impacted products
    Vendor Product Version
    nimiq nimiq_proof-of-stake *

    {
      "affected": [
        {
          "affectedData": [
            {
              "product": "network-libp2p",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "source": "security-advisories@github.com"
        }
      ],
      "configurations": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:nimiq:nimiq_proof-of-stake:*:*:*:*:*:rust:*:*",
                  "matchCriteriaId": "CD0CAAD1-7626-4A4A-A6F8-9DC46FE50731",
                  "versionEndExcluding": "1.3.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "cveTags": [],
      "descriptions": [
        {
          "lang": "en",
          "value": "Nimiq\u0027s network-libp2p is a Nimiq network implementation based on libp2p. Prior to version 1.3.0, `network-libp2p` discovery uses a libp2p `ConnectionHandler` state machine. the handler assumes there is at most one inbound and one outbound discovery substream per connection. if a remote peer opens/negotiate the discovery protocol substream a second time on the same connection, the handler hits a `panic!(\\\"Inbound already connected\\\")` / `panic!(\\\"Outbound already connected\\\")` path instead of failing closed. This causes a remote crash of the networking task (swarm), taking the node\u0027s p2p networking offline until restart. The patch for this vulnerability is formally released as part of v1.3.0. No known workarounds are available."
        },
        {
          "lang": "es",
          "value": "El network-libp2p de Nimiq es una implementaci\u00f3n de red de Nimiq basada en libp2p. Antes de la versi\u00f3n 1.3.0, el descubrimiento de \u201cnetwork-libp2p\u201d utiliza una m\u00e1quina de estados \u201cConnectionHandler\u201d de libp2p. El gestor asume que hay como m\u00e1ximo un subflujo de descubrimiento entrante y uno saliente por conexi\u00f3n. Si un par remoto abre/negocia el subflujo del protocolo de descubrimiento una segunda vez en la misma conexi\u00f3n, el gestor alcanza una ruta \u201cpanic!(\u2019Inbound already connected\u2019)\u201d / \u201cpanic!(\u2019Outbound already connected\u2019)\u201d en lugar de fallar de forma controlada. Esto provoca un fallo remoto de la tarea de red (swarm), dejando la red p2p del nodo fuera de l\u00ednea hasta el reinicio. El parche para esta vulnerabilidad se publica formalmente como parte de la v1.3.0. No se conocen soluciones alternativas disponibles."
        }
      ],
      "id": "CVE-2026-34063",
      "lastModified": "2026-10-26T22:10:00.163",
      "metrics": {
        "cvssMetricV31": [
          {
            "cvssData": {
              "attackComplexity": "LOW",
              "attackVector": "NETWORK",
              "availabilityImpact": "HIGH",
              "baseScore": 7.5,
              "baseSeverity": "HIGH",
              "confidentialityImpact": "NONE",
              "integrityImpact": "NONE",
              "privilegesRequired": "NONE",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
              "version": "3.1"
            },
            "exploitabilityScore": 3.9,
            "impactScore": 3.6,
            "source": "security-advisories@github.com",
            "type": "Secondary"
          }
        ],
        "ssvcV203": [
          {
            "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
            "ssvcData": {
              "id": "CVE-2026-34063",
              "options": [
                {
                  "exploitation": "none"
                },
                {
                  "automatable": "yes"
                },
                {
                  "technicalImpact": "partial"
                }
              ],
              "role": "CISA Coordinator",
              "timestamp": "2026-04-23T13:51:51.197194Z",
              "version": "2.0.3"
            }
          }
        ]
      },
      "published": "2026-04-22T20:16:40.713",
      "references": [
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/commit/e0d4e01994f061bf41d3c2835bc74040d3c084f5"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Issue Tracking",
            "Patch"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/pull/3666"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Release Notes"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch",
            "Vendor Advisory"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-74hp-mhfx-m45h"
        }
      ],
      "sourceIdentifier": "security-advisories@github.com",
      "vulnStatus": "Analyzed",
      "weaknesses": [
        {
          "description": [
            {
              "lang": "en",
              "value": "CWE-617"
            }
          ],
          "source": "security-advisories@github.com",
          "type": "Secondary"
        }
      ]
    }

    FKIE_CVE-2026-34068

    Vulnerability from fkie_nvd - Published: 2026-04-22 21:17 - Updated: 2026-10-26 22:10
    Summary
    nimiq-transaction provides the transaction primitive to be used in Nimiq's Rust implementation. Prior to version 1.3.0, the staking contract accepts `UpdateValidator` transactions that set `new_voting_key=Some(...)` while omitting `new_proof_of_knowledge`. this skips the proof-of-knowledge requirement that is needed to prevent BLS rogue-key attacks when public keys are aggregated. Because tendermint macro block justification verification aggregates validator voting keys and verifies a single aggregated BLS signature against that aggregate public key, a rogue-key voting key in the validator set can allow an attacker to forge a quorum-looking justification while only producing a single signature. While the impact is critical, the exploitability is low: The voting keys are fixed for the epoch, so the attacker would need to know the next epoch validator set (chosen through VRF), which is unlikely. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.
    Impacted products
    Vendor Product Version
    nimiq nimiq_proof-of-stake *

    {
      "affected": [
        {
          "affectedData": [
            {
              "product": "nimiq-transaction",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "source": "security-advisories@github.com"
        }
      ],
      "configurations": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:nimiq:nimiq_proof-of-stake:*:*:*:*:*:rust:*:*",
                  "matchCriteriaId": "CD0CAAD1-7626-4A4A-A6F8-9DC46FE50731",
                  "versionEndExcluding": "1.3.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "cveTags": [],
      "descriptions": [
        {
          "lang": "en",
          "value": "nimiq-transaction provides the transaction primitive to be used in Nimiq\u0027s Rust implementation. Prior to version 1.3.0, the staking contract accepts `UpdateValidator` transactions that set `new_voting_key=Some(...)` while omitting `new_proof_of_knowledge`. this skips the proof-of-knowledge requirement that is needed to prevent BLS rogue-key attacks when public keys are aggregated. Because tendermint macro block justification verification aggregates validator voting keys and verifies a single aggregated BLS signature against that aggregate public key, a rogue-key voting key in the validator set can allow an attacker to forge a quorum-looking justification while only producing a single signature. While the impact is critical, the exploitability is low: The voting keys are fixed for the epoch, so the attacker would need to know the next epoch validator set (chosen through VRF), which is unlikely. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available."
        },
        {
          "lang": "es",
          "value": "nimiq-transaction proporciona la primitiva de transacci\u00f3n para ser utilizada en la implementaci\u00f3n de Nimiq en Rust. Antes de la versi\u00f3n 1.3.0, el contrato de staking acepta transacciones \u2019UpdateValidator\u2019 que establecen \u2019new_voting_key=Some(...)\u2019 mientras omiten \u2019new_proof_of_knowledge\u2019. Esto omite el requisito de prueba de conocimiento que es necesario para prevenir ataques de clave maliciosa BLS cuando las claves p\u00fablicas son agregadas. Debido a que la verificaci\u00f3n de justificaci\u00f3n de macrobloques de Tendermint agrega las claves de votaci\u00f3n de los validadores y verifica una \u00fanica firma BLS agregada contra esa clave p\u00fablica agregada, una clave de votaci\u00f3n de clave maliciosa en el conjunto de validadores puede permitir a un atacante forjar una justificaci\u00f3n que parezca un qu\u00f3rum mientras solo produce una \u00fanica firma. Si bien el impacto es cr\u00edtico, la explotabilidad es baja: Las claves de votaci\u00f3n est\u00e1n fijas para la \u00e9poca, por lo que el atacante necesitar\u00eda conocer el conjunto de validadores de la pr\u00f3xima \u00e9poca (elegido a trav\u00e9s de VRF), lo cual es poco probable. El parche para esta vulnerabilidad est\u00e1 incluido como parte de la v1.3.0. No hay soluciones alternativas conocidas disponibles."
        }
      ],
      "id": "CVE-2026-34068",
      "lastModified": "2026-10-26T22:10:00.163",
      "metrics": {
        "cvssMetricV31": [
          {
            "cvssData": {
              "attackComplexity": "HIGH",
              "attackVector": "NETWORK",
              "availabilityImpact": "NONE",
              "baseScore": 6.8,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "NONE",
              "integrityImpact": "HIGH",
              "privilegesRequired": "NONE",
              "scope": "CHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N",
              "version": "3.1"
            },
            "exploitabilityScore": 2.2,
            "impactScore": 4.0,
            "source": "security-advisories@github.com",
            "type": "Secondary"
          }
        ],
        "ssvcV203": [
          {
            "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
            "ssvcData": {
              "id": "CVE-2026-34068",
              "options": [
                {
                  "exploitation": "none"
                },
                {
                  "automatable": "no"
                },
                {
                  "technicalImpact": "partial"
                }
              ],
              "role": "CISA Coordinator",
              "timestamp": "2026-04-23T12:56:19.048672Z",
              "version": "2.0.3"
            }
          }
        ]
      },
      "published": "2026-04-22T21:17:08.197",
      "references": [
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/commit/e7f0ab7d2115e17d6e5548ddc60f10df1a5d645f"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Issue Tracking",
            "Patch"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/pull/3654"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Release Notes"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch",
            "Vendor Advisory"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-pf4j-pf3w-95f9"
        }
      ],
      "sourceIdentifier": "security-advisories@github.com",
      "vulnStatus": "Analyzed",
      "weaknesses": [
        {
          "description": [
            {
              "lang": "en",
              "value": "CWE-347"
            }
          ],
          "source": "security-advisories@github.com",
          "type": "Secondary"
        }
      ]
    }

    FKIE_CVE-2026-34067

    Vulnerability from fkie_nvd - Published: 2026-04-22 21:17 - Updated: 2026-10-26 22:10
    Summary
    nimiq-transaction provides the transaction primitive to be used in Nimiq's Rust implementation. Prior to version 1.3.0, `HistoryTreeProof::verify` panics on a malformed proof where `history.len() != positions.len()` due to `assert_eq!(history.len(), positions.len())`. The proof object is derived from untrusted p2p responses (`ResponseTransactionsProof.proof`) and is therefore attacker-controlled at the network boundary until validated. A malicious peer could trigger a crash by returning a crafted inclusion proof with a length mismatch. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.
    Impacted products
    Vendor Product Version
    nimiq nimiq_proof-of-stake *

    {
      "affected": [
        {
          "affectedData": [
            {
              "product": "nimiq-transaction",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "source": "security-advisories@github.com"
        }
      ],
      "configurations": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:nimiq:nimiq_proof-of-stake:*:*:*:*:*:rust:*:*",
                  "matchCriteriaId": "CD0CAAD1-7626-4A4A-A6F8-9DC46FE50731",
                  "versionEndExcluding": "1.3.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "cveTags": [],
      "descriptions": [
        {
          "lang": "en",
          "value": "nimiq-transaction provides the transaction primitive to be used in Nimiq\u0027s Rust implementation. Prior to version 1.3.0, `HistoryTreeProof::verify` panics on a malformed proof where `history.len() != positions.len()` due to `assert_eq!(history.len(), positions.len())`. The proof object is derived from untrusted p2p responses (`ResponseTransactionsProof.proof`) and is therefore attacker-controlled at the network boundary until validated. A malicious peer could trigger a crash by returning a crafted inclusion proof with a length mismatch. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available."
        },
        {
          "lang": "es",
          "value": "nimiq-transaction proporciona la primitiva de transacci\u00f3n para ser utilizada en la implementaci\u00f3n de Nimiq en Rust. Antes de la versi\u00f3n 1.3.0, \u2019HistoryTreeProof::verify\u2019 entra en p\u00e1nico ante una prueba malformada donde \u2019history.len() != positions.len()\u2019 debido a \u2019assert_eq!(history.len(), positions.len())\u2019. El objeto de prueba se deriva de respuestas p2p no confiables (\u2019ResponseTransactionsProof.proof\u2019) y, por lo tanto, es controlado por el atacante en el l\u00edmite de la red hasta que sea validado. Un par malicioso podr\u00eda desencadenar un fallo al devolver una prueba de inclusi\u00f3n manipulada con una discrepancia de longitud. El parche para esta vulnerabilidad est\u00e1 incluido como parte de la v1.3.0. No se conocen soluciones alternativas disponibles."
        }
      ],
      "id": "CVE-2026-34067",
      "lastModified": "2026-10-26T22:10:00.163",
      "metrics": {
        "cvssMetricV31": [
          {
            "cvssData": {
              "attackComplexity": "HIGH",
              "attackVector": "NETWORK",
              "availabilityImpact": "LOW",
              "baseScore": 3.1,
              "baseSeverity": "LOW",
              "confidentialityImpact": "NONE",
              "integrityImpact": "NONE",
              "privilegesRequired": "NONE",
              "scope": "UNCHANGED",
              "userInteraction": "REQUIRED",
              "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L",
              "version": "3.1"
            },
            "exploitabilityScore": 1.6,
            "impactScore": 1.4,
            "source": "security-advisories@github.com",
            "type": "Secondary"
          },
          {
            "cvssData": {
              "attackComplexity": "LOW",
              "attackVector": "NETWORK",
              "availabilityImpact": "HIGH",
              "baseScore": 6.5,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "NONE",
              "integrityImpact": "NONE",
              "privilegesRequired": "NONE",
              "scope": "UNCHANGED",
              "userInteraction": "REQUIRED",
              "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
              "version": "3.1"
            },
            "exploitabilityScore": 2.8,
            "impactScore": 3.6,
            "source": "nvd@nist.gov",
            "type": "Primary"
          }
        ],
        "ssvcV203": [
          {
            "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
            "ssvcData": {
              "id": "CVE-2026-34067",
              "options": [
                {
                  "exploitation": "none"
                },
                {
                  "automatable": "no"
                },
                {
                  "technicalImpact": "partial"
                }
              ],
              "role": "CISA Coordinator",
              "timestamp": "2026-04-23T14:17:49.301869Z",
              "version": "2.0.3"
            }
          }
        ]
      },
      "published": "2026-04-22T21:17:07.760",
      "references": [
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/commit/6ff0800e8e031363e787c827d8d033e5694e4e6a"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Issue Tracking",
            "Patch"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/pull/3659"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Release Notes"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch",
            "Vendor Advisory"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-264v-m8fm-76jm"
        }
      ],
      "sourceIdentifier": "security-advisories@github.com",
      "vulnStatus": "Analyzed",
      "weaknesses": [
        {
          "description": [
            {
              "lang": "en",
              "value": "CWE-617"
            }
          ],
          "source": "security-advisories@github.com",
          "type": "Secondary"
        }
      ]
    }

    FKIE_CVE-2026-34065

    Vulnerability from fkie_nvd - Published: 2026-04-22 20:16 - Updated: 2026-10-26 22:10
    Summary
    nimiq-primitives contains primitives (e.g., block, account, transaction) to be used in Nimiq's Rust implementation. Prior to version 1.3.0, an untrusted p2p peer can cause a node to panic by announcing an election macro block whose `validators` set contains an invalid compressed BLS voting key. Hashing an election macro header hashes `validators` and reaches `Validators::voting_keys()`, which calls `validator.voting_key.uncompress().unwrap()` and panics on invalid bytes. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.
    Impacted products
    Vendor Product Version
    nimiq nimiq_proof-of-stake *

    {
      "affected": [
        {
          "affectedData": [
            {
              "product": "nimiq-primitives",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "source": "security-advisories@github.com"
        }
      ],
      "configurations": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:nimiq:nimiq_proof-of-stake:*:*:*:*:*:rust:*:*",
                  "matchCriteriaId": "CD0CAAD1-7626-4A4A-A6F8-9DC46FE50731",
                  "versionEndExcluding": "1.3.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "cveTags": [],
      "descriptions": [
        {
          "lang": "en",
          "value": "nimiq-primitives contains primitives (e.g., block, account, transaction) to be used in Nimiq\u0027s Rust implementation. Prior to version 1.3.0, an untrusted p2p peer can cause a node to panic by announcing an election macro block whose `validators` set contains an invalid compressed BLS voting key. Hashing an election macro header hashes `validators` and reaches `Validators::voting_keys()`, which calls `validator.voting_key.uncompress().unwrap()` and panics on invalid bytes. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available."
        },
        {
          "lang": "es",
          "value": "nimiq-primitives contiene primitivas (p. ej., bloque, cuenta, transacci\u00f3n) para ser utilizadas en la implementaci\u00f3n de Nimiq en Rust. Antes de la versi\u00f3n 1.3.0, un par p2p no confiable puede causar un p\u00e1nico en un nodo al anunciar un macrobloque de elecci\u00f3n cuyo conjunto de \u2019validators\u2019 contiene una clave de votaci\u00f3n BLS comprimida inv\u00e1lida. El hash de una cabecera de macro de elecci\u00f3n aplica hash a \u2019validators\u2019 y llega a \u2019Validators::voting_keys()\u2019, que llama a \u2019validator.voting_key.uncompress().unwrap()\u2019 y entra en p\u00e1nico con bytes inv\u00e1lidos. El parche para esta vulnerabilidad est\u00e1 incluido como parte de la v1.3.0. No se conocen soluciones alternativas disponibles."
        }
      ],
      "id": "CVE-2026-34065",
      "lastModified": "2026-10-26T22:10:00.163",
      "metrics": {
        "cvssMetricV31": [
          {
            "cvssData": {
              "attackComplexity": "LOW",
              "attackVector": "NETWORK",
              "availabilityImpact": "HIGH",
              "baseScore": 7.5,
              "baseSeverity": "HIGH",
              "confidentialityImpact": "NONE",
              "integrityImpact": "NONE",
              "privilegesRequired": "NONE",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
              "version": "3.1"
            },
            "exploitabilityScore": 3.9,
            "impactScore": 3.6,
            "source": "security-advisories@github.com",
            "type": "Secondary"
          }
        ],
        "ssvcV203": [
          {
            "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
            "ssvcData": {
              "id": "CVE-2026-34065",
              "options": [
                {
                  "exploitation": "none"
                },
                {
                  "automatable": "yes"
                },
                {
                  "technicalImpact": "partial"
                }
              ],
              "role": "CISA Coordinator",
              "timestamp": "2026-04-23T14:16:52.791989Z",
              "version": "2.0.3"
            }
          }
        ]
      },
      "published": "2026-04-22T20:16:41.077",
      "references": [
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/commit/e10eaebcd7774e5da6d0ff5e88ed13503474f0ff"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Issue Tracking",
            "Patch"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/pull/3662"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Release Notes"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch",
            "Vendor Advisory"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-7c4j-2m43-2mgh"
        }
      ],
      "sourceIdentifier": "security-advisories@github.com",
      "vulnStatus": "Analyzed",
      "weaknesses": [
        {
          "description": [
            {
              "lang": "en",
              "value": "CWE-252"
            },
            {
              "lang": "en",
              "value": "CWE-755"
            }
          ],
          "source": "security-advisories@github.com",
          "type": "Secondary"
        }
      ]
    }

    FKIE_CVE-2026-33471

    Vulnerability from fkie_nvd - Published: 2026-04-22 20:16 - Updated: 2026-10-26 21:10
    Summary
    nimiq-block contains block primitives to be used in Nimiq's Rust implementation. `SkipBlockProof::verify` computes its quorum check using `BitSet.len()`, then iterates `BitSet` indices and casts each `usize` index to `u16` (`slot as u16`) for slot lookup. Prior to version 1.3.0, if an attacker can get a `SkipBlockProof` verified where `MultiSignature.signers` contains out-of-range indices spaced by 65536, these indices inflate `len()` but collide onto the same in-range `u16` slot during aggregation. This makes it possible for a malicious validator with far fewer than `2f+1` real signer slots to pass skip block proof verification by multiplying a single BLS signature by the same factor. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.
    Impacted products
    Vendor Product Version
    nimiq nimiq_proof-of-stake *

    {
      "affected": [
        {
          "affectedData": [
            {
              "product": "nimiq-block",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "source": "security-advisories@github.com"
        }
      ],
      "configurations": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:nimiq:nimiq_proof-of-stake:*:*:*:*:*:rust:*:*",
                  "matchCriteriaId": "CD0CAAD1-7626-4A4A-A6F8-9DC46FE50731",
                  "versionEndExcluding": "1.3.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "cveTags": [],
      "descriptions": [
        {
          "lang": "en",
          "value": "nimiq-block contains block primitives to be used in Nimiq\u0027s Rust implementation. `SkipBlockProof::verify` computes its quorum check using `BitSet.len()`, then iterates `BitSet` indices and casts each `usize` index to `u16` (`slot as u16`) for slot lookup. Prior to version 1.3.0, if an attacker can get a `SkipBlockProof` verified where `MultiSignature.signers` contains out-of-range indices spaced by 65536, these indices inflate `len()` but collide onto the same in-range `u16` slot during aggregation. This makes it possible for a malicious validator with far fewer than `2f+1` real signer slots to pass skip block proof verification by multiplying a single BLS signature by the same factor. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available."
        },
        {
          "lang": "es",
          "value": "nimiq-block contiene primitivas de bloque para ser utilizadas en la implementaci\u00f3n de Nimiq en Rust. SkipBlockProof::verify calcula su verificaci\u00f3n de qu\u00f3rum usando BitSet.len(), luego itera los \u00edndices de BitSet y convierte cada \u00edndice usize a u16 (slot as u16) para la b\u00fasqueda de slot. Antes de la versi\u00f3n 1.3.0, si un atacante puede lograr que se verifique un SkipBlockProof donde MultiSignature.signers contiene \u00edndices fuera de rango espaciados por 65536, estos \u00edndices inflan len() pero colisionan en el mismo slot u16 dentro del rango durante la agregaci\u00f3n. Esto hace posible que un validador malicioso con muchos menos de 2f+1 slots de firmante reales pase la verificaci\u00f3n de prueba de bloque de salto multiplicando una \u00fanica firma BLS por el mismo factor. El parche para esta vulnerabilidad se incluye como parte de la v1.3.0. No se conocen soluciones alternativas disponibles."
        }
      ],
      "id": "CVE-2026-33471",
      "lastModified": "2026-10-26T21:10:00.170",
      "metrics": {
        "cvssMetricV31": [
          {
            "cvssData": {
              "attackComplexity": "LOW",
              "attackVector": "NETWORK",
              "availabilityImpact": "HIGH",
              "baseScore": 9.6,
              "baseSeverity": "CRITICAL",
              "confidentialityImpact": "NONE",
              "integrityImpact": "HIGH",
              "privilegesRequired": "LOW",
              "scope": "CHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H",
              "version": "3.1"
            },
            "exploitabilityScore": 3.1,
            "impactScore": 5.8,
            "source": "security-advisories@github.com",
            "type": "Secondary"
          }
        ],
        "ssvcV203": [
          {
            "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
            "ssvcData": {
              "id": "CVE-2026-33471",
              "options": [
                {
                  "exploitation": "none"
                },
                {
                  "automatable": "no"
                },
                {
                  "technicalImpact": "partial"
                }
              ],
              "role": "CISA Coordinator",
              "timestamp": "2026-04-23T14:15:09.611330Z",
              "version": "2.0.3"
            }
          }
        ]
      },
      "published": "2026-04-22T20:16:40.317",
      "references": [
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/commit/d02059053181ed8ddad6b59a0adfd661ef5cd823"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Release Notes"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch",
            "Vendor Advisory"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-6973-8887-87ff"
        }
      ],
      "sourceIdentifier": "security-advisories@github.com",
      "vulnStatus": "Analyzed",
      "weaknesses": [
        {
          "description": [
            {
              "lang": "en",
              "value": "CWE-20"
            },
            {
              "lang": "en",
              "value": "CWE-190"
            },
            {
              "lang": "en",
              "value": "CWE-345"
            },
            {
              "lang": "en",
              "value": "CWE-1284"
            }
          ],
          "source": "security-advisories@github.com",
          "type": "Secondary"
        }
      ]
    }

    FKIE_CVE-2026-34069

    Vulnerability from fkie_nvd - Published: 2026-04-14 00:16 - Updated: 2026-10-26 21:10
    Summary
    nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. In versions 1.2.2 and below, an unauthenticated p2p peer can cause the RequestMacroChain message handler task to panic. Sending a RequestMacroChain message where the first locator hash on the victim’s main chain is a micro block hash (not a macro block hash) causes said panic. The RequestMacroChain::handle handler selects the locator based only on "is on main chain", then calls get_macro_blocks() and panics via .unwrap() when the selected hash is not a macro block (BlockchainError::BlockIsNotMacro). This issue has been fixed in version 1.3.0.
    Impacted products
    Vendor Product Version
    nimiq nimiq_proof-of-stake *

    {
      "affected": [
        {
          "affectedData": [
            {
              "product": "core-rs-albatross",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "source": "security-advisories@github.com"
        }
      ],
      "configurations": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:nimiq:nimiq_proof-of-stake:*:*:*:*:*:rust:*:*",
                  "matchCriteriaId": "CD0CAAD1-7626-4A4A-A6F8-9DC46FE50731",
                  "versionEndExcluding": "1.3.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "cveTags": [],
      "descriptions": [
        {
          "lang": "en",
          "value": "nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. In versions 1.2.2 and below, an unauthenticated p2p peer can cause the RequestMacroChain message handler task to panic. Sending a RequestMacroChain message where the first locator hash on the victim\u2019s main chain is a micro block hash (not a macro block hash) causes said panic. The RequestMacroChain::handle handler selects the locator based only on \"is on main chain\", then calls get_macro_blocks() and panics via .unwrap() when the selected hash is not a macro block (BlockchainError::BlockIsNotMacro). This issue has been fixed in version 1.3.0."
        },
        {
          "lang": "es",
          "value": "nimiq/core-rs-albatross es una implementaci\u00f3n en Rust del protocolo Nimiq Proof-of-Stake basado en el algoritmo de consenso Albatross. En las versiones 1.2.2 e inferiores, un par p2p no autenticado puede provocar que la tarea del gestor de mensajes RequestMacroChain entre en p\u00e1nico. Enviar un mensaje RequestMacroChain donde el primer hash localizador en la cadena principal de la v\u00edctima es un hash de microbloque (no un hash de macrobloque) provoca dicho p\u00e1nico. El gestor RequestMacroChain::handle selecciona el localizador bas\u00e1ndose \u00fanicamente en \u2019is on main chain\u2019, luego llama a get_macro_blocks() y entra en p\u00e1nico a trav\u00e9s de .unwrap() cuando el hash seleccionado no es un macrobloque (BlockchainError::BlockIsNotMacro). Este problema ha sido solucionado en la versi\u00f3n 1.3.0."
        }
      ],
      "id": "CVE-2026-34069",
      "lastModified": "2026-10-26T21:10:00.170",
      "metrics": {
        "cvssMetricV31": [
          {
            "cvssData": {
              "attackComplexity": "LOW",
              "attackVector": "NETWORK",
              "availabilityImpact": "LOW",
              "baseScore": 5.3,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "NONE",
              "integrityImpact": "NONE",
              "privilegesRequired": "NONE",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
              "version": "3.1"
            },
            "exploitabilityScore": 3.9,
            "impactScore": 1.4,
            "source": "security-advisories@github.com",
            "type": "Secondary"
          }
        ],
        "ssvcV203": [
          {
            "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
            "ssvcData": {
              "id": "CVE-2026-34069",
              "options": [
                {
                  "exploitation": "none"
                },
                {
                  "automatable": "yes"
                },
                {
                  "technicalImpact": "partial"
                }
              ],
              "role": "CISA Coordinator",
              "timestamp": "2026-04-14T15:35:06.474382Z",
              "version": "2.0.3"
            }
          }
        ]
      },
      "published": "2026-04-14T00:16:07.023",
      "references": [
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/commit/ae6c1e92342e72f80fd12accbe66ee80dd6802ac"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Issue Tracking",
            "Patch"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/pull/3660"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Release Notes"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch",
            "Vendor Advisory"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-48m6-486p-9j8p"
        }
      ],
      "sourceIdentifier": "security-advisories@github.com",
      "vulnStatus": "Analyzed",
      "weaknesses": [
        {
          "description": [
            {
              "lang": "en",
              "value": "CWE-617"
            }
          ],
          "source": "security-advisories@github.com",
          "type": "Secondary"
        }
      ]
    }

    FKIE_CVE-2026-34066

    Vulnerability from fkie_nvd - Published: 2026-04-22 20:16 - Updated: 2026-10-26 21:10
    Summary
    nimiq-blockchain provides persistent block storage for Nimiq's Rust implementation. Prior to version 1.3.0, `HistoryStore::put_historic_txns` uses an `assert!` to enforce invariants about `HistoricTransaction.block_number` (must be within the macro block being pushed and within the same epoch). During history sync, a peer can influence the `history: &[HistoricTransaction]` input passed into `Blockchain::push_history_sync`, and a malformed history list can violate these invariants and trigger a panic. `extend_history_sync` calls `this.history_store.add_to_history(..)` before comparing the computed history root against the macro block header (`block.history_root()`), so the panic can happen before later rejection checks run. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.
    Impacted products
    Vendor Product Version
    nimiq nimiq_proof-of-stake *

    {
      "affected": [
        {
          "affectedData": [
            {
              "product": "nimiq-blockchain",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "source": "security-advisories@github.com"
        }
      ],
      "configurations": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:nimiq:nimiq_proof-of-stake:*:*:*:*:*:rust:*:*",
                  "matchCriteriaId": "CD0CAAD1-7626-4A4A-A6F8-9DC46FE50731",
                  "versionEndExcluding": "1.3.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "cveTags": [],
      "descriptions": [
        {
          "lang": "en",
          "value": "nimiq-blockchain provides persistent block storage for Nimiq\u0027s Rust implementation. Prior to version 1.3.0, `HistoryStore::put_historic_txns` uses an `assert!` to enforce invariants about `HistoricTransaction.block_number` (must be within the macro block being pushed and within the same epoch). During history sync, a peer can influence the `history: \u0026[HistoricTransaction]` input passed into `Blockchain::push_history_sync`, and a malformed history list can violate these invariants and trigger a panic. `extend_history_sync` calls `this.history_store.add_to_history(..)` before comparing the computed history root against the macro block header (`block.history_root()`), so the panic can happen before later rejection checks run. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available."
        },
        {
          "lang": "es",
          "value": "nimiq-blockchain proporciona almacenamiento persistente de bloques para la implementaci\u00f3n en Rust de Nimiq. Antes de la versi\u00f3n 1.3.0, \u2019HistoryStore::put_historic_txns\u2019 utiliza un \u2019assert!\u2019 para hacer cumplir invariantes sobre \u2019HistoricTransaction.block_number\u2019 (debe estar dentro del macrobloque que se est\u00e1 insertando y dentro de la misma \u00e9poca). Durante la sincronizaci\u00f3n del historial, un par puede influir en la entrada \u2019history: \u0026[HistoricTransaction]\u2019 pasada a \u2019Blockchain::push_history_sync\u2019, y una lista de historial malformada puede violar estas invariantes y desencadenar un p\u00e1nico. \u2019extend_history_sync\u2019 llama a \u2019this.history_store.add_to_history(..)\u2019 antes de comparar la ra\u00edz del historial calculada con la cabecera del macrobloque (\u2019block.history_root()\u2019), por lo que el p\u00e1nico puede ocurrir antes de que se ejecuten las comprobaciones de rechazo posteriores. El parche para esta vulnerabilidad est\u00e1 incluido como parte de la v1.3.0. No se conocen soluciones alternativas disponibles."
        }
      ],
      "id": "CVE-2026-34066",
      "lastModified": "2026-10-26T21:10:00.170",
      "metrics": {
        "cvssMetricV31": [
          {
            "cvssData": {
              "attackComplexity": "HIGH",
              "attackVector": "NETWORK",
              "availabilityImpact": "HIGH",
              "baseScore": 5.3,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "NONE",
              "integrityImpact": "NONE",
              "privilegesRequired": "NONE",
              "scope": "UNCHANGED",
              "userInteraction": "REQUIRED",
              "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H",
              "version": "3.1"
            },
            "exploitabilityScore": 1.6,
            "impactScore": 3.6,
            "source": "security-advisories@github.com",
            "type": "Secondary"
          }
        ],
        "ssvcV203": [
          {
            "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
            "ssvcData": {
              "id": "CVE-2026-34066",
              "options": [
                {
                  "exploitation": "none"
                },
                {
                  "automatable": "no"
                },
                {
                  "technicalImpact": "partial"
                }
              ],
              "role": "CISA Coordinator",
              "timestamp": "2026-04-23T12:56:55.597573Z",
              "version": "2.0.3"
            }
          }
        ]
      },
      "published": "2026-04-22T20:16:41.237",
      "references": [
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/commit/6f5511309c199d84b012fe6b9aba7e5582892c50"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Issue Tracking",
            "Patch"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/pull/3656"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Release Notes"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch",
            "Vendor Advisory"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-j99g-7rqw-q9jg"
        }
      ],
      "sourceIdentifier": "security-advisories@github.com",
      "vulnStatus": "Analyzed",
      "weaknesses": [
        {
          "description": [
            {
              "lang": "en",
              "value": "CWE-20"
            },
            {
              "lang": "en",
              "value": "CWE-617"
            },
            {
              "lang": "en",
              "value": "CWE-754"
            }
          ],
          "source": "security-advisories@github.com",
          "type": "Secondary"
        }
      ]
    }

    FKIE_CVE-2026-32605

    Vulnerability from fkie_nvd - Published: 2026-04-13 20:16 - Updated: 2026-10-26 21:10
    Summary
    nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, an untrusted peer could crash a validator by publishing a signed tendermint proposal message where signer == validators.num_validators(). ProposalSender::send uses > instead of >= for the signer bounds check, so the equality case passes and reaches validators.get_validator_by_slot_band(signer), which panics with an out-of-bounds index before any signature verification runs. This issue has been fixed in version 1.3.0.
    Impacted products
    Vendor Product Version
    nimiq nimiq_proof-of-stake *

    {
      "affected": [
        {
          "affectedData": [
            {
              "product": "core-rs-albatross",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "source": "security-advisories@github.com"
        }
      ],
      "configurations": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:nimiq:nimiq_proof-of-stake:*:*:*:*:*:rust:*:*",
                  "matchCriteriaId": "CD0CAAD1-7626-4A4A-A6F8-9DC46FE50731",
                  "versionEndExcluding": "1.3.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "cveTags": [],
      "descriptions": [
        {
          "lang": "en",
          "value": "nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, an untrusted peer could crash a validator by publishing a signed tendermint proposal message where signer == validators.num_validators(). ProposalSender::send uses \u003e instead of \u003e= for the signer bounds check, so the equality case passes and reaches validators.get_validator_by_slot_band(signer), which panics with an out-of-bounds index before any signature verification runs. This issue has been fixed in version 1.3.0."
        },
        {
          "lang": "es",
          "value": "nimiq/core-rs-albatross es una implementaci\u00f3n en Rust del protocolo Nimiq Proof-of-Stake basado en el algoritmo de consenso Albatross. Antes de la versi\u00f3n 1.3.0, un par no confiable podr\u00eda colapsar un validador al publicar un mensaje de propuesta tendermint firmado donde signer == validators.num_validators(). ProposalSender::send usa \u003e en lugar de \u003e= para la comprobaci\u00f3n de l\u00edmites del firmante, por lo que el caso de igualdad pasa y llega a validators.get_validator_by_slot_band(signer), lo que provoca un p\u00e1nico con un \u00edndice fuera de l\u00edmites antes de que se ejecute cualquier verificaci\u00f3n de firma. Este problema ha sido solucionado en la versi\u00f3n 1.3.0."
        }
      ],
      "id": "CVE-2026-32605",
      "lastModified": "2026-10-26T21:10:00.170",
      "metrics": {
        "cvssMetricV31": [
          {
            "cvssData": {
              "attackComplexity": "LOW",
              "attackVector": "NETWORK",
              "availabilityImpact": "HIGH",
              "baseScore": 7.5,
              "baseSeverity": "HIGH",
              "confidentialityImpact": "NONE",
              "integrityImpact": "NONE",
              "privilegesRequired": "NONE",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
              "version": "3.1"
            },
            "exploitabilityScore": 3.9,
            "impactScore": 3.6,
            "source": "security-advisories@github.com",
            "type": "Secondary"
          }
        ],
        "ssvcV203": [
          {
            "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
            "ssvcData": {
              "id": "CVE-2026-32605",
              "options": [
                {
                  "exploitation": "none"
                },
                {
                  "automatable": "yes"
                },
                {
                  "technicalImpact": "partial"
                }
              ],
              "role": "CISA Coordinator",
              "timestamp": "2026-04-16T13:20:25.349665Z",
              "version": "2.0.3"
            }
          }
        ]
      },
      "published": "2026-04-13T20:16:33.787",
      "references": [
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/commit/9199364b60c7acae4219800d194bbe07d2997b8c"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Issue Tracking",
            "Patch"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/pull/3661"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Release Notes"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch",
            "Vendor Advisory"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-g99c-h7j7-rfhv"
        }
      ],
      "sourceIdentifier": "security-advisories@github.com",
      "vulnStatus": "Analyzed",
      "weaknesses": [
        {
          "description": [
            {
              "lang": "en",
              "value": "CWE-125"
            },
            {
              "lang": "en",
              "value": "CWE-193"
            }
          ],
          "source": "security-advisories@github.com",
          "type": "Secondary"
        }
      ]
    }

    FKIE_CVE-2026-34064

    Vulnerability from fkie_nvd - Published: 2026-04-22 20:16 - Updated: 2026-10-26 21:10
    Summary
    nimiq-account contains account primitives to be used in Nimiq's Rust implementation. Prior to version 1.3.0, `VestingContract::can_change_balance` returns `AccountError::InsufficientFunds` when `new_balance < min_cap`, but it constructs the error using `balance: self.balance - min_cap`. `Coin::sub` panics on underflow, so if an attacker can reach a state where `min_cap > balance`, the node crashes while trying to return an error. The `min_cap > balance` precondition is attacker-reachable because the vesting contract creation data (32-byte format) allows encoding `total_amount` without validating `total_amount <= transaction.value` (the real contract balance). After creating such a vesting contract, the attacker can broadcast an outgoing transaction to trigger the panic during mempool admission and block processing. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.
    Impacted products
    Vendor Product Version
    nimiq nimiq_proof-of-stake *

    {
      "affected": [
        {
          "affectedData": [
            {
              "product": "nimiq-account",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "source": "security-advisories@github.com"
        }
      ],
      "configurations": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:nimiq:nimiq_proof-of-stake:*:*:*:*:*:rust:*:*",
                  "matchCriteriaId": "CD0CAAD1-7626-4A4A-A6F8-9DC46FE50731",
                  "versionEndExcluding": "1.3.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "cveTags": [],
      "descriptions": [
        {
          "lang": "en",
          "value": "nimiq-account contains account primitives to be used in Nimiq\u0027s Rust implementation. Prior to version 1.3.0, `VestingContract::can_change_balance` returns `AccountError::InsufficientFunds` when `new_balance \u003c min_cap`, but it constructs the error using `balance: self.balance - min_cap`. `Coin::sub` panics on underflow, so if an attacker can reach a state where `min_cap \u003e balance`, the node crashes while trying to return an error. The `min_cap \u003e balance` precondition is attacker-reachable because the vesting contract creation data (32-byte format) allows encoding `total_amount` without validating `total_amount \u003c= transaction.value` (the real contract balance). After creating such a vesting contract, the attacker can broadcast an outgoing transaction to trigger the panic during mempool admission and block processing. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available."
        },
        {
          "lang": "es",
          "value": "nimiq-account contiene primitivas de cuenta para ser utilizadas en la implementaci\u00f3n de Nimiq en Rust. Antes de la versi\u00f3n 1.3.0, \u201cVestingContract::can_change_balance\u201d devuelve \u201cAccountError::InsufficientFunds\u201d cuando \u201cnew_balance \u003c min_cap\u201d, pero construye el error usando \u201cbalance: self.balance - min_cap\u201d. \u201cCoin::sub\u201d entra en p\u00e1nico por desbordamiento negativo, as\u00ed que si un atacante puede alcanzar un estado donde \u201cmin_cap \u003e balance\u201d, el nodo falla mientras intenta devolver un error. La precondici\u00f3n \u201cmin_cap \u003e balance\u201d es alcanzable por el atacante porque los datos de creaci\u00f3n del contrato de vesting (formato de 32 bytes) permiten codificar \u201ctotal_amount\u201d sin validar \u201ctotal_amount \u003c= transaction.value\u201d (el saldo real del contrato). Despu\u00e9s de crear dicho contrato de vesting, el atacante puede difundir una transacci\u00f3n saliente para desencadenar el p\u00e1nico durante la admisi\u00f3n en el mempool y el procesamiento de bloques. El parche para esta vulnerabilidad est\u00e1 incluido como parte de la v1.3.0. No se conocen soluciones alternativas disponibles."
        }
      ],
      "id": "CVE-2026-34064",
      "lastModified": "2026-10-26T21:10:00.170",
      "metrics": {
        "cvssMetricV31": [
          {
            "cvssData": {
              "attackComplexity": "LOW",
              "attackVector": "NETWORK",
              "availabilityImpact": "NONE",
              "baseScore": 5.3,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "NONE",
              "integrityImpact": "LOW",
              "privilegesRequired": "NONE",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
              "version": "3.1"
            },
            "exploitabilityScore": 3.9,
            "impactScore": 1.4,
            "source": "security-advisories@github.com",
            "type": "Secondary"
          },
          {
            "cvssData": {
              "attackComplexity": "LOW",
              "attackVector": "NETWORK",
              "availabilityImpact": "HIGH",
              "baseScore": 8.2,
              "baseSeverity": "HIGH",
              "confidentialityImpact": "NONE",
              "integrityImpact": "LOW",
              "privilegesRequired": "NONE",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H",
              "version": "3.1"
            },
            "exploitabilityScore": 3.9,
            "impactScore": 4.2,
            "source": "nvd@nist.gov",
            "type": "Primary"
          }
        ],
        "ssvcV203": [
          {
            "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
            "ssvcData": {
              "id": "CVE-2026-34064",
              "options": [
                {
                  "exploitation": "none"
                },
                {
                  "automatable": "yes"
                },
                {
                  "technicalImpact": "partial"
                }
              ],
              "role": "CISA Coordinator",
              "timestamp": "2026-04-23T13:06:41.242710Z",
              "version": "2.0.3"
            }
          }
        ]
      },
      "published": "2026-04-22T20:16:40.900",
      "references": [
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/commit/4d01946f0b3d6c6e31786f91cdfb3eb902908da0"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Issue Tracking",
            "Patch"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/pull/3658"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Release Notes"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch",
            "Vendor Advisory"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-vc34-39q2-m6q3"
        }
      ],
      "sourceIdentifier": "security-advisories@github.com",
      "vulnStatus": "Analyzed",
      "weaknesses": [
        {
          "description": [
            {
              "lang": "en",
              "value": "CWE-191"
            }
          ],
          "source": "security-advisories@github.com",
          "type": "Secondary"
        }
      ]
    }

    FKIE_CVE-2026-34062

    Vulnerability from fkie_nvd - Published: 2026-04-22 20:16 - Updated: 2026-10-26 21:10
    Summary
    nimiq-libp2p is a Nimiq network implementation based on libp2p. Prior to version 1.3.0, `MessageCodec::read_request` and `read_response` call `read_to_end()` on inbound substreams, so a remote peer can send only a partial frame and keep the substream open. because `Behaviour::new` also sets `with_max_concurrent_streams(1000)`, the node exposes a much larger stalled-slot budget than the library default. The patch for this vulnerability is formally released as part of v1.3.0. No known workarounds are available.
    Impacted products
    Vendor Product Version
    nimiq nimiq_proof-of-stake *

    {
      "affected": [
        {
          "affectedData": [
            {
              "product": "network-libp2p",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "source": "security-advisories@github.com"
        }
      ],
      "configurations": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:nimiq:nimiq_proof-of-stake:*:*:*:*:*:rust:*:*",
                  "matchCriteriaId": "CD0CAAD1-7626-4A4A-A6F8-9DC46FE50731",
                  "versionEndExcluding": "1.3.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "cveTags": [],
      "descriptions": [
        {
          "lang": "en",
          "value": "nimiq-libp2p is a Nimiq network implementation based on libp2p. Prior to version 1.3.0, `MessageCodec::read_request` and `read_response` call `read_to_end()` on inbound substreams, so a remote peer can send only a partial frame and keep the substream open. because `Behaviour::new` also sets `with_max_concurrent_streams(1000)`, the node exposes a much larger stalled-slot budget than the library default. The patch for this vulnerability is formally released as part of v1.3.0. No known workarounds are available."
        },
        {
          "lang": "es",
          "value": "nimiq-libp2p es una implementaci\u00f3n de red Nimiq basada en libp2p. Antes de la versi\u00f3n 1.3.0, \u2019MessageCodec::read_request\u2019 y \u2019read_response\u2019 llaman a \u2019read_to_end()\u2019 en subflujos entrantes, de modo que un par remoto puede enviar solo una trama parcial y mantener el subflujo abierto. Debido a que \u2019Behaviour::new\u2019 tambi\u00e9n establece \u2019with_max_concurrent_streams(1000)\u2019, el nodo expone un presupuesto de ranuras estancadas mucho mayor que el valor predeterminado de la biblioteca. El parche para esta vulnerabilidad se lanza formalmente como parte de la v1.3.0. No se conocen soluciones alternativas disponibles."
        }
      ],
      "id": "CVE-2026-34062",
      "lastModified": "2026-10-26T21:10:00.170",
      "metrics": {
        "cvssMetricV31": [
          {
            "cvssData": {
              "attackComplexity": "LOW",
              "attackVector": "NETWORK",
              "availabilityImpact": "LOW",
              "baseScore": 5.3,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "NONE",
              "integrityImpact": "NONE",
              "privilegesRequired": "NONE",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
              "version": "3.1"
            },
            "exploitabilityScore": 3.9,
            "impactScore": 1.4,
            "source": "security-advisories@github.com",
            "type": "Secondary"
          }
        ],
        "ssvcV203": [
          {
            "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
            "ssvcData": {
              "id": "CVE-2026-34062",
              "options": [
                {
                  "exploitation": "none"
                },
                {
                  "automatable": "yes"
                },
                {
                  "technicalImpact": "partial"
                }
              ],
              "role": "CISA Coordinator",
              "timestamp": "2026-04-23T12:57:31.642650Z",
              "version": "2.0.3"
            }
          }
        ]
      },
      "published": "2026-04-22T20:16:40.530",
      "references": [
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/commit/c021a5337b808c73571b44999f9753051bac7508"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Release Notes"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch",
            "Vendor Advisory"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-gh7r-qh4p-q4fr"
        }
      ],
      "sourceIdentifier": "security-advisories@github.com",
      "vulnStatus": "Analyzed",
      "weaknesses": [
        {
          "description": [
            {
              "lang": "en",
              "value": "CWE-770"
            }
          ],
          "source": "security-advisories@github.com",
          "type": "Secondary"
        }
      ]
    }

    FKIE_CVE-2026-40093

    Vulnerability from fkie_nvd - Published: 2026-04-09 21:16 - Updated: 2026-10-26 00:10
    Summary
    nimiq-blockchain provides persistent block storage for Nimiq's Rust implementation. In 1.3.0 and earlier, block timestamp validation enforces that timestamp >= parent.timestamp for non-skip blocks and timestamp == parent.timestamp + MIN_PRODUCER_TIMEOUT for skip blocks, but there is no visible upper bound check against the wall clock. A malicious block-producing validator can set block timestamps arbitrarily far in the future. This directly affects reward calculations via Policy::supply_at() and batch_delay() in blockchain/src/reward.rs, inflating the monetary supply beyond the intended emission schedule.
    Impacted products
    Vendor Product Version
    nimiq nimiq_proof-of-stake *

    {
      "affected": [
        {
          "affectedData": [
            {
              "product": "core-rs-albatross",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c= 1.3.0"
                }
              ]
            }
          ],
          "source": "security-advisories@github.com"
        }
      ],
      "configurations": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:nimiq:nimiq_proof-of-stake:*:*:*:*:*:rust:*:*",
                  "matchCriteriaId": "CD0CAAD1-7626-4A4A-A6F8-9DC46FE50731",
                  "versionEndExcluding": "1.3.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "cveTags": [],
      "descriptions": [
        {
          "lang": "en",
          "value": "nimiq-blockchain provides persistent block storage for Nimiq\u0027s Rust implementation. In 1.3.0 and earlier, block timestamp validation enforces that timestamp \u003e= parent.timestamp for non-skip blocks and timestamp == parent.timestamp + MIN_PRODUCER_TIMEOUT for skip blocks, but there is no visible upper bound check against the wall clock. A malicious block-producing validator can set block timestamps arbitrarily far in the future. This directly affects reward calculations via Policy::supply_at() and batch_delay() in blockchain/src/reward.rs, inflating the monetary supply beyond the intended emission schedule."
        },
        {
          "lang": "es",
          "value": "nimiq-blockchain proporciona almacenamiento persistente de bloques para la implementaci\u00f3n en Rust de Nimiq. En la versi\u00f3n 1.3.0 y anteriores, la validaci\u00f3n de la marca de tiempo del bloque impone que la marca de tiempo \u003e= la marca de tiempo del padre para bloques no omitidos y la marca de tiempo == la marca de tiempo del padre + MIN_PRODUCER_TIMEOUT para bloques omitidos, pero no hay una comprobaci\u00f3n visible de l\u00edmite superior contra el reloj de pared. Un validador malicioso que produce bloques puede establecer las marcas de tiempo de los bloques arbitrariamente lejos en el futuro. Esto afecta directamente los c\u00e1lculos de recompensa a trav\u00e9s de Policy::supply_at() y batch_delay() en blockchain/src/reward.rs, inflando la oferta monetaria m\u00e1s all\u00e1 del cronograma de emisi\u00f3n previsto."
        }
      ],
      "id": "CVE-2026-40093",
      "lastModified": "2026-10-26T00:10:00.150",
      "metrics": {
        "cvssMetricV31": [
          {
            "cvssData": {
              "attackComplexity": "LOW",
              "attackVector": "NETWORK",
              "availabilityImpact": "HIGH",
              "baseScore": 8.1,
              "baseSeverity": "HIGH",
              "confidentialityImpact": "NONE",
              "integrityImpact": "HIGH",
              "privilegesRequired": "LOW",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H",
              "version": "3.1"
            },
            "exploitabilityScore": 2.8,
            "impactScore": 5.2,
            "source": "security-advisories@github.com",
            "type": "Secondary"
          }
        ],
        "ssvcV203": [
          {
            "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
            "ssvcData": {
              "id": "CVE-2026-40093",
              "options": [
                {
                  "exploitation": "none"
                },
                {
                  "automatable": "no"
                },
                {
                  "technicalImpact": "partial"
                }
              ],
              "role": "CISA Coordinator",
              "timestamp": "2026-04-13T15:05:36.431662Z",
              "version": "2.0.3"
            }
          }
        ]
      },
      "published": "2026-04-09T21:16:11.937",
      "references": [
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Broken Link"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-49xc-52mp-cc9j"
        }
      ],
      "sourceIdentifier": "security-advisories@github.com",
      "vulnStatus": "Analyzed",
      "weaknesses": [
        {
          "description": [
            {
              "lang": "en",
              "value": "CWE-1284"
            }
          ],
          "source": "security-advisories@github.com",
          "type": "Secondary"
        }
      ]
    }

    FKIE_CVE-2026-33184

    Vulnerability from fkie_nvd - Published: 2026-04-03 23:17 - Updated: 2026-07-24 22:10
    Summary
    nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, the discovery handler accepts a peer-controlled limit during handshake and stores it unchanged. The immediate HandshakeAck path then honors limit = 0 and returns zero contacts, which makes the session look benign. Later, after the same session reaches Established, the periodic update path computes self.peer_list_limit.unwrap() as usize - 1. With limit = 0, that wraps to usize::MAX and then in rand 0.9.2, choose_multiple() immediately attempts Vec::with_capacity(amount), which deterministically panics with capacity overflow. This issue has been patched in version 1.3.0.
    Impacted products
    Vendor Product Version
    nimiq nimiq_proof-of-stake *

    {
      "affected": [
        {
          "affectedData": [
            {
              "product": "core-rs-albatross",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "source": "security-advisories@github.com"
        }
      ],
      "configurations": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:nimiq:nimiq_proof-of-stake:*:*:*:*:*:rust:*:*",
                  "matchCriteriaId": "F1D1AFE5-536A-424A-B7D3-AFCE79533E39",
                  "versionEndIncluding": "1.2.2",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "cveTags": [],
      "descriptions": [
        {
          "lang": "en",
          "value": "nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, the discovery handler accepts a peer-controlled limit during handshake and stores it unchanged. The immediate HandshakeAck path then honors limit = 0 and returns zero contacts, which makes the session look benign. Later, after the same session reaches Established, the periodic update path computes self.peer_list_limit.unwrap() as usize - 1. With limit = 0, that wraps to usize::MAX and then in rand 0.9.2, choose_multiple() immediately attempts Vec::with_capacity(amount), which deterministically panics with capacity overflow. This issue has been patched in version 1.3.0."
        },
        {
          "lang": "es",
          "value": "nimiq/core-rs-albatross es una implementaci\u00f3n en Rust del protocolo Nimiq Proof-of-Stake basado en el algoritmo de consenso Albatross. Antes de la versi\u00f3n 1.3.0, el gestor de descubrimiento acepta un l\u00edmite controlado por el par durante el handshake y lo almacena sin cambios. La ruta inmediata de HandshakeAck entonces respeta l\u00edmite = 0 y devuelve cero contactos, lo que hace que la sesi\u00f3n parezca benigna. M\u00e1s tarde, despu\u00e9s de que la misma sesi\u00f3n alcanza el estado Establecido, la ruta de actualizaci\u00f3n peri\u00f3dica calcula self.peer_list_limit.unwrap() como usize - 1. Con l\u00edmite = 0, eso se ajusta a usize::MAX y luego en rand 0.9.2, choose_multiple() intenta inmediatamente Vec::with_capacity(amount), lo que provoca un p\u00e1nico determinista por desbordamiento de capacidad. Este problema ha sido parcheado en la versi\u00f3n 1.3.0."
        }
      ],
      "id": "CVE-2026-33184",
      "lastModified": "2026-07-24T22:10:00.140",
      "metrics": {
        "cvssMetricV31": [
          {
            "cvssData": {
              "attackComplexity": "LOW",
              "attackVector": "NETWORK",
              "availabilityImpact": "HIGH",
              "baseScore": 7.5,
              "baseSeverity": "HIGH",
              "confidentialityImpact": "NONE",
              "integrityImpact": "NONE",
              "privilegesRequired": "NONE",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
              "version": "3.1"
            },
            "exploitabilityScore": 3.9,
            "impactScore": 3.6,
            "source": "security-advisories@github.com",
            "type": "Secondary"
          }
        ],
        "ssvcV203": [
          {
            "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
            "ssvcData": {
              "id": "CVE-2026-33184",
              "options": [
                {
                  "exploitation": "none"
                },
                {
                  "automatable": "yes"
                },
                {
                  "technicalImpact": "partial"
                }
              ],
              "role": "CISA Coordinator",
              "timestamp": "2026-04-06T13:19:23.883699Z",
              "version": "2.0.3"
            }
          }
        ]
      },
      "published": "2026-04-03T23:17:03.600",
      "references": [
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/commit/8f60a2d75b74b55764ecf34bd4435f4961630595"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/pull/3664"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Release Notes"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Vendor Advisory"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-5rm9-893q-vmhm"
        }
      ],
      "sourceIdentifier": "security-advisories@github.com",
      "vulnStatus": "Analyzed",
      "weaknesses": [
        {
          "description": [
            {
              "lang": "en",
              "value": "CWE-191"
            }
          ],
          "source": "security-advisories@github.com",
          "type": "Secondary"
        }
      ]
    }

    FKIE_CVE-2026-34061

    Vulnerability from fkie_nvd - Published: 2026-04-03 23:17 - Updated: 2026-07-24 22:10
    Summary
    nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, an elected validator proposer can send an election macro block whose header.interlink does not match the canonical next interlink. Honest validators accept that proposal in verify_macro_block_proposal() because the proposal path validates header shape, successor relation, proposer, body root, and state, but never checks the interlink binding for election blocks. The same finalized block is later rejected by verify_block() during push with InvalidInterlink. Because validators prevote and precommit the malformed header hash itself, the failure happens after Tendermint decides the block, not before voting. This issue has been patched in version 1.3.0.
    Impacted products
    Vendor Product Version
    nimiq nimiq_proof-of-stake *

    {
      "affected": [
        {
          "affectedData": [
            {
              "product": "core-rs-albatross",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "source": "security-advisories@github.com"
        }
      ],
      "configurations": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:nimiq:nimiq_proof-of-stake:*:*:*:*:*:rust:*:*",
                  "matchCriteriaId": "F1D1AFE5-536A-424A-B7D3-AFCE79533E39",
                  "versionEndIncluding": "1.2.2",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "cveTags": [],
      "descriptions": [
        {
          "lang": "en",
          "value": "nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, an elected validator proposer can send an election macro block whose header.interlink does not match the canonical next interlink. Honest validators accept that proposal in verify_macro_block_proposal() because the proposal path validates header shape, successor relation, proposer, body root, and state, but never checks the interlink binding for election blocks. The same finalized block is later rejected by verify_block() during push with InvalidInterlink. Because validators prevote and precommit the malformed header hash itself, the failure happens after Tendermint decides the block, not before voting. This issue has been patched in version 1.3.0."
        },
        {
          "lang": "es",
          "value": "nimiq/core-rs-albatross es una implementaci\u00f3n en Rust del protocolo Nimiq Proof-of-Stake basado en el algoritmo de consenso Albatross. Antes de la versi\u00f3n 1.3.0, un proponente validador elegido puede enviar un macrobloque de elecci\u00f3n cuyo header.interlink no coincide con el siguiente interlink can\u00f3nico. Los validadores honestos aceptan esa propuesta en verify_macro_block_proposal() porque la ruta de la propuesta valida la forma del encabezado, la relaci\u00f3n de sucesor, el proponente, la ra\u00edz del cuerpo y el estado, pero nunca verifica la vinculaci\u00f3n del interlink para los bloques de elecci\u00f3n. El mismo bloque finalizado es posteriormente rechazado por verify_block() durante el push con InvalidInterlink. Debido a que los validadores prevotan y preconfirman el hash del encabezado malformado en s\u00ed, la falla ocurre despu\u00e9s de que Tendermint decide el bloque, no antes de la votaci\u00f3n. Este problema ha sido parcheado en la versi\u00f3n 1.3.0."
        }
      ],
      "id": "CVE-2026-34061",
      "lastModified": "2026-07-24T22:10:00.140",
      "metrics": {
        "cvssMetricV31": [
          {
            "cvssData": {
              "attackComplexity": "LOW",
              "attackVector": "NETWORK",
              "availabilityImpact": "HIGH",
              "baseScore": 4.9,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "NONE",
              "integrityImpact": "NONE",
              "privilegesRequired": "HIGH",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H",
              "version": "3.1"
            },
            "exploitabilityScore": 1.2,
            "impactScore": 3.6,
            "source": "security-advisories@github.com",
            "type": "Secondary"
          },
          {
            "cvssData": {
              "attackComplexity": "LOW",
              "attackVector": "NETWORK",
              "availabilityImpact": "HIGH",
              "baseScore": 6.5,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "NONE",
              "integrityImpact": "NONE",
              "privilegesRequired": "LOW",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
              "version": "3.1"
            },
            "exploitabilityScore": 2.8,
            "impactScore": 3.6,
            "source": "nvd@nist.gov",
            "type": "Primary"
          }
        ],
        "ssvcV203": [
          {
            "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
            "ssvcData": {
              "id": "CVE-2026-34061",
              "options": [
                {
                  "exploitation": "none"
                },
                {
                  "automatable": "no"
                },
                {
                  "technicalImpact": "partial"
                }
              ],
              "role": "CISA Coordinator",
              "timestamp": "2026-04-06T15:37:16.058073Z",
              "version": "2.0.3"
            }
          }
        ]
      },
      "published": "2026-04-03T23:17:03.940",
      "references": [
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/commit/9d7d17c9163384e79f61cdbbfe9853ae57bb8bf7"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/pull/3668"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Release Notes"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Third Party Advisory"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-gr83-j5f8-p2r5"
        }
      ],
      "sourceIdentifier": "security-advisories@github.com",
      "vulnStatus": "Analyzed",
      "weaknesses": [
        {
          "description": [
            {
              "lang": "en",
              "value": "CWE-345"
            }
          ],
          "source": "security-advisories@github.com",
          "type": "Secondary"
        }
      ]
    }

    FKIE_CVE-2026-35468

    Vulnerability from fkie_nvd - Published: 2026-04-03 23:17 - Updated: 2026-07-24 21:10
    Summary
    nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, two peer-facing consensus request handlers assume that the history index is always available and call blockchain.history_store.history_index().unwrap() directly. That assumption is false by construction. HistoryStoreProxy::history_index() explicitly returns None for the valid HistoryStoreProxy::WithoutIndex state. when a full node is syncing or otherwise running without the history index, a remote peer can send RequestTransactionsProof or RequestTransactionReceiptsByAddress and trigger an Option::unwrap() panic on the request path. This issue has been patched in version 1.3.0.
    Impacted products
    Vendor Product Version
    nimiq nimiq_proof-of-stake *

    {
      "affected": [
        {
          "affectedData": [
            {
              "product": "core-rs-albatross",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "source": "security-advisories@github.com"
        }
      ],
      "configurations": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:nimiq:nimiq_proof-of-stake:*:*:*:*:*:rust:*:*",
                  "matchCriteriaId": "F1D1AFE5-536A-424A-B7D3-AFCE79533E39",
                  "versionEndIncluding": "1.2.2",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "cveTags": [],
      "descriptions": [
        {
          "lang": "en",
          "value": "nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, two peer-facing consensus request handlers assume that the history index is always available and call blockchain.history_store.history_index().unwrap() directly. That assumption is false by construction. HistoryStoreProxy::history_index() explicitly returns None for the valid HistoryStoreProxy::WithoutIndex state. when a full node is syncing or otherwise running without the history index, a remote peer can send RequestTransactionsProof or RequestTransactionReceiptsByAddress and trigger an Option::unwrap() panic on the request path. This issue has been patched in version 1.3.0."
        },
        {
          "lang": "es",
          "value": "nimiq/core-rs-albatross es una implementaci\u00f3n en Rust del protocolo Nimiq Proof-of-Stake basado en el algoritmo de consenso Albatross. Antes de la versi\u00f3n 1.3.0, dos manejadores de solicitudes de consenso orientados a pares asumen que el \u00edndice de historial siempre est\u00e1 disponible y llaman directamente a blockchain.history_store.history_index().unwrap(). Esa suposici\u00f3n es falsa por construcci\u00f3n. HistoryStoreProxy::history_index() devuelve expl\u00edcitamente None para el estado v\u00e1lido HistoryStoreProxy::WithoutIndex. Cuando un nodo completo est\u00e1 sincronizando o de otro modo ejecut\u00e1ndose sin el \u00edndice de historial, un par remoto puede enviar RequestTransactionsProof o RequestTransactionReceiptsByAddress y desencadenar un p\u00e1nico de Option::unwrap() en la ruta de solicitud. Este problema ha sido parcheado en la versi\u00f3n 1.3.0."
        }
      ],
      "id": "CVE-2026-35468",
      "lastModified": "2026-07-24T21:10:00.143",
      "metrics": {
        "cvssMetricV31": [
          {
            "cvssData": {
              "attackComplexity": "LOW",
              "attackVector": "NETWORK",
              "availabilityImpact": "LOW",
              "baseScore": 5.3,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "NONE",
              "integrityImpact": "NONE",
              "privilegesRequired": "NONE",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
              "version": "3.1"
            },
            "exploitabilityScore": 3.9,
            "impactScore": 1.4,
            "source": "security-advisories@github.com",
            "type": "Secondary"
          },
          {
            "cvssData": {
              "attackComplexity": "LOW",
              "attackVector": "NETWORK",
              "availabilityImpact": "HIGH",
              "baseScore": 7.5,
              "baseSeverity": "HIGH",
              "confidentialityImpact": "NONE",
              "integrityImpact": "NONE",
              "privilegesRequired": "NONE",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
              "version": "3.1"
            },
            "exploitabilityScore": 3.9,
            "impactScore": 3.6,
            "source": "nvd@nist.gov",
            "type": "Primary"
          }
        ],
        "ssvcV203": [
          {
            "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
            "ssvcData": {
              "id": "CVE-2026-35468",
              "options": [
                {
                  "exploitation": "none"
                },
                {
                  "automatable": "yes"
                },
                {
                  "technicalImpact": "partial"
                }
              ],
              "role": "CISA Coordinator",
              "timestamp": "2026-04-06T17:21:56.424442Z",
              "version": "2.0.3"
            }
          }
        ]
      },
      "published": "2026-04-03T23:17:06.963",
      "references": [
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/commit/0e5c90a6c75b722f3d6091769776a4040e694dba"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/pull/3667"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Release Notes"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Vendor Advisory"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-xr78-2jhh-9wf9"
        }
      ],
      "sourceIdentifier": "security-advisories@github.com",
      "vulnStatus": "Analyzed",
      "weaknesses": [
        {
          "description": [
            {
              "lang": "en",
              "value": "CWE-252"
            }
          ],
          "source": "security-advisories@github.com",
          "type": "Secondary"
        }
      ]
    }

    FKIE_CVE-2026-28402

    Vulnerability from fkie_nvd - Published: 2026-02-27 22:16 - Updated: 2026-06-17 10:28
    Summary
    nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.2.2, a malicious or compromised validator that is elected as proposer can publish a macro block proposal where `header.body_root` does not match the actual macro body hash. The proposal can pass proposal verification because the macro proposal verification path validates the header but does not validate the binding `body_root == hash(body)`; later code expects this binding and may panic on mismatch, crashing validators. Note that the impact is only for validator nodes. The patch for this vulnerability is formally released as part of v1.2.2. The patch adds the corresponding body root verification in the proposal checks. No known workarounds are available.
    Impacted products
    Vendor Product Version
    nimiq nimiq_proof-of-stake *

    {
      "affected": [
        {
          "affectedData": [
            {
              "product": "core-rs-albatross",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.2.2"
                }
              ]
            }
          ],
          "source": "security-advisories@github.com"
        }
      ],
      "configurations": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:nimiq:nimiq_proof-of-stake:*:*:*:*:*:rust:*:*",
                  "matchCriteriaId": "9BCFC726-4536-43C8-ABF8-42AFF032FB78",
                  "versionEndExcluding": "1.2.2",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "cveTags": [],
      "descriptions": [
        {
          "lang": "en",
          "value": "nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.2.2, a malicious or compromised validator that is elected as proposer can publish a macro block proposal where `header.body_root` does not match the actual macro body hash. The proposal can pass proposal verification because the macro proposal verification path validates the header but does not validate the binding `body_root == hash(body)`; later code expects this binding and may panic on mismatch, crashing validators. Note that the impact is only for validator nodes. The patch for this vulnerability is formally released as part of v1.2.2. The patch adds the corresponding body root verification in the proposal checks. No known workarounds are available."
        },
        {
          "lang": "es",
          "value": "nimiq/core-rs-albatross es una implementaci\u00f3n en Rust del protocolo Nimiq Proof-of-Stake basado en el algoritmo de consenso Albatross. Antes de la versi\u00f3n 1.2.2, un validador malicioso o comprometido que es elegido como proponente puede publicar una propuesta de macrobloque donde `header.body_root` no coincide con el hash real del cuerpo del macrobloque. La propuesta puede pasar la verificaci\u00f3n de la propuesta porque la ruta de verificaci\u00f3n de la macropropuesta valida el encabezado pero no valida la vinculaci\u00f3n `body_root == hash(body)`; el c\u00f3digo posterior espera esta vinculaci\u00f3n y puede entrar en p\u00e1nico en caso de falta de coincidencia, provocando la ca\u00edda de los validadores. Tenga en cuenta que el impacto es solo para los nodos validadores. El parche para esta vulnerabilidad se lanza formalmente como parte de la v1.2.2. El parche a\u00f1ade la verificaci\u00f3n correspondiente del body root en las comprobaciones de la propuesta. No se conocen soluciones alternativas disponibles."
        }
      ],
      "id": "CVE-2026-28402",
      "lastModified": "2026-06-17T10:28:33.450",
      "metrics": {
        "cvssMetricV31": [
          {
            "cvssData": {
              "attackComplexity": "LOW",
              "attackVector": "NETWORK",
              "availabilityImpact": "HIGH",
              "baseScore": 7.1,
              "baseSeverity": "HIGH",
              "confidentialityImpact": "NONE",
              "integrityImpact": "LOW",
              "privilegesRequired": "LOW",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H",
              "version": "3.1"
            },
            "exploitabilityScore": 2.8,
            "impactScore": 4.2,
            "source": "security-advisories@github.com",
            "type": "Secondary"
          }
        ],
        "ssvcV203": [
          {
            "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
            "ssvcData": {
              "id": "CVE-2026-28402",
              "options": [
                {
                  "exploitation": "none"
                },
                {
                  "automatable": "no"
                },
                {
                  "technicalImpact": "partial"
                }
              ],
              "role": "CISA Coordinator",
              "timestamp": "2026-03-03T20:31:49.868298Z",
              "version": "2.0.3"
            }
          }
        ]
      },
      "published": "2026-02-27T22:16:23.343",
      "references": [
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/commit/6454c26d966858c5520f55739a30b94c17656c85"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Patch"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/pull/3623"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Release Notes"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.2.2"
        },
        {
          "source": "security-advisories@github.com",
          "tags": [
            "Third Party Advisory"
          ],
          "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-7wh6-rmxx-ww47"
        }
      ],
      "sourceIdentifier": "security-advisories@github.com",
      "vulnStatus": "Analyzed",
      "weaknesses": [
        {
          "description": [
            {
              "lang": "en",
              "value": "CWE-354"
            }
          ],
          "source": "security-advisories@github.com",
          "type": "Secondary"
        }
      ]
    }

    CVE-2026-34068 (GCVE-0-2026-34068)

    Vulnerability from nvd – Published: 2026-04-22 19:55 – Updated: 2026-04-23 12:56
    VLAI
    Title
    nimiq-transaction: UpdateValidator transactions allows voting key change without proof-of-knowledge
    Summary
    nimiq-transaction provides the transaction primitive to be used in Nimiq's Rust implementation. Prior to version 1.3.0, the staking contract accepts `UpdateValidator` transactions that set `new_voting_key=Some(...)` while omitting `new_proof_of_knowledge`. this skips the proof-of-knowledge requirement that is needed to prevent BLS rogue-key attacks when public keys are aggregated. Because tendermint macro block justification verification aggregates validator voting keys and verifies a single aggregated BLS signature against that aggregate public key, a rogue-key voting key in the validator set can allow an attacker to forge a quorum-looking justification while only producing a single signature. While the impact is critical, the exploitability is low: The voting keys are fixed for the epoch, so the attacker would need to know the next epoch validator set (chosen through VRF), which is unlikely. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.
    SSVC
    Exploitation: none Automatable: no Technical Impact: partial
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-04-23 12:56 UTC
    CWE
    • CWE-347 - Improper Verification of Cryptographic Signature
    Assigner
    GitHub_M CNA under the mitre root
    CNA scorecard C 72/100 over 8074 records in the last 180 days details
    Impacted products
    Vendor Product Version
    nimiq nimiq-transaction Affected: < 1.3.0
    Create a notification for this product.
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-34068",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-04-23T12:56:19.048672Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-04-23T12:56:27.980Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "nimiq-transaction",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "descriptions": [
            {
              "lang": "en",
              "value": "nimiq-transaction provides the transaction primitive to be used in Nimiq\u0027s Rust implementation. Prior to version 1.3.0, the staking contract accepts `UpdateValidator` transactions that set `new_voting_key=Some(...)` while omitting `new_proof_of_knowledge`. this skips the proof-of-knowledge requirement that is needed to prevent BLS rogue-key attacks when public keys are aggregated. Because tendermint macro block justification verification aggregates validator voting keys and verifies a single aggregated BLS signature against that aggregate public key, a rogue-key voting key in the validator set can allow an attacker to forge a quorum-looking justification while only producing a single signature. While the impact is critical, the exploitability is low: The voting keys are fixed for the epoch, so the attacker would need to know the next epoch validator set (chosen through VRF), which is unlikely. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "attackComplexity": "HIGH",
                "attackVector": "NETWORK",
                "availabilityImpact": "NONE",
                "baseScore": 6.8,
                "baseSeverity": "MEDIUM",
                "confidentialityImpact": "NONE",
                "integrityImpact": "HIGH",
                "privilegesRequired": "NONE",
                "scope": "CHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N",
                "version": "3.1"
              }
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-347",
                  "description": "CWE-347: Improper Verification of Cryptographic Signature",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-04-22T19:55:24.731Z",
            "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
            "shortName": "GitHub_M"
          },
          "references": [
            {
              "name": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-pf4j-pf3w-95f9",
              "tags": [
                "x_refsource_CONFIRM"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-pf4j-pf3w-95f9"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/pull/3654",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/pull/3654"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/commit/e7f0ab7d2115e17d6e5548ddc60f10df1a5d645f",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/commit/e7f0ab7d2115e17d6e5548ddc60f10df1a5d645f"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
            }
          ],
          "source": {
            "advisory": "GHSA-pf4j-pf3w-95f9",
            "discovery": "UNKNOWN"
          },
          "title": "nimiq-transaction: UpdateValidator transactions allows voting key change without proof-of-knowledge"
        }
      },
      "cveMetadata": {
        "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "assignerShortName": "GitHub_M",
        "cveId": "CVE-2026-34068",
        "datePublished": "2026-04-22T19:55:08.219Z",
        "dateReserved": "2026-03-25T16:21:40.867Z",
        "dateUpdated": "2026-04-23T12:56:27.980Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-34067 (GCVE-0-2026-34067)

    Vulnerability from nvd – Published: 2026-04-22 19:52 – Updated: 2026-04-23 14:17
    VLAI
    Title
    nimiq-transaction vulnerable to panic via `HistoryTreeProof` length mismatch
    Summary
    nimiq-transaction provides the transaction primitive to be used in Nimiq's Rust implementation. Prior to version 1.3.0, `HistoryTreeProof::verify` panics on a malformed proof where `history.len() != positions.len()` due to `assert_eq!(history.len(), positions.len())`. The proof object is derived from untrusted p2p responses (`ResponseTransactionsProof.proof`) and is therefore attacker-controlled at the network boundary until validated. A malicious peer could trigger a crash by returning a crafted inclusion proof with a length mismatch. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.
    SSVC
    Exploitation: none Automatable: no Technical Impact: partial
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-04-23 14:17 UTC
    CWE
    Assigner
    GitHub_M CNA under the mitre root
    CNA scorecard C 72/100 over 8074 records in the last 180 days details
    Impacted products
    Vendor Product Version
    nimiq nimiq-transaction Affected: < 1.3.0
    Create a notification for this product.
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-34067",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-04-23T14:17:49.301869Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-04-23T14:17:59.735Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "nimiq-transaction",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "descriptions": [
            {
              "lang": "en",
              "value": "nimiq-transaction provides the transaction primitive to be used in Nimiq\u0027s Rust implementation. Prior to version 1.3.0, `HistoryTreeProof::verify` panics on a malformed proof where `history.len() != positions.len()` due to `assert_eq!(history.len(), positions.len())`. The proof object is derived from untrusted p2p responses (`ResponseTransactionsProof.proof`) and is therefore attacker-controlled at the network boundary until validated. A malicious peer could trigger a crash by returning a crafted inclusion proof with a length mismatch. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "attackComplexity": "HIGH",
                "attackVector": "NETWORK",
                "availabilityImpact": "LOW",
                "baseScore": 3.1,
                "baseSeverity": "LOW",
                "confidentialityImpact": "NONE",
                "integrityImpact": "NONE",
                "privilegesRequired": "NONE",
                "scope": "UNCHANGED",
                "userInteraction": "REQUIRED",
                "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L",
                "version": "3.1"
              }
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-617",
                  "description": "CWE-617: Reachable Assertion",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-04-22T19:52:43.916Z",
            "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
            "shortName": "GitHub_M"
          },
          "references": [
            {
              "name": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-264v-m8fm-76jm",
              "tags": [
                "x_refsource_CONFIRM"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-264v-m8fm-76jm"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/pull/3659",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/pull/3659"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/commit/6ff0800e8e031363e787c827d8d033e5694e4e6a",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/commit/6ff0800e8e031363e787c827d8d033e5694e4e6a"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
            }
          ],
          "source": {
            "advisory": "GHSA-264v-m8fm-76jm",
            "discovery": "UNKNOWN"
          },
          "title": "nimiq-transaction vulnerable to panic via `HistoryTreeProof` length mismatch"
        }
      },
      "cveMetadata": {
        "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "assignerShortName": "GitHub_M",
        "cveId": "CVE-2026-34067",
        "datePublished": "2026-04-22T19:52:43.916Z",
        "dateReserved": "2026-03-25T16:21:40.867Z",
        "dateUpdated": "2026-04-23T14:17:59.735Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-34066 (GCVE-0-2026-34066)

    Vulnerability from nvd – Published: 2026-04-22 19:47 – Updated: 2026-04-23 12:57
    VLAI
    Title
    nimiq-blockchain: Peer-triggerable panic during history sync
    Summary
    nimiq-blockchain provides persistent block storage for Nimiq's Rust implementation. Prior to version 1.3.0, `HistoryStore::put_historic_txns` uses an `assert!` to enforce invariants about `HistoricTransaction.block_number` (must be within the macro block being pushed and within the same epoch). During history sync, a peer can influence the `history: &[HistoricTransaction]` input passed into `Blockchain::push_history_sync`, and a malformed history list can violate these invariants and trigger a panic. `extend_history_sync` calls `this.history_store.add_to_history(..)` before comparing the computed history root against the macro block header (`block.history_root()`), so the panic can happen before later rejection checks run. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.
    SSVC
    Exploitation: none Automatable: no Technical Impact: partial
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-04-23 12:56 UTC
    CWE
    • CWE-20 - Improper Input Validation
    • CWE-617 - Reachable Assertion
    • CWE-754 - Improper Check for Unusual or Exceptional Conditions
    Assigner
    GitHub_M CNA under the mitre root
    CNA scorecard C 72/100 over 8074 records in the last 180 days details
    Impacted products
    Vendor Product Version
    nimiq nimiq-blockchain Affected: < 1.3.0
    Create a notification for this product.
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-34066",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-04-23T12:56:55.597573Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-04-23T12:57:06.467Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "nimiq-blockchain",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "descriptions": [
            {
              "lang": "en",
              "value": "nimiq-blockchain provides persistent block storage for Nimiq\u0027s Rust implementation. Prior to version 1.3.0, `HistoryStore::put_historic_txns` uses an `assert!` to enforce invariants about `HistoricTransaction.block_number` (must be within the macro block being pushed and within the same epoch). During history sync, a peer can influence the `history: \u0026[HistoricTransaction]` input passed into `Blockchain::push_history_sync`, and a malformed history list can violate these invariants and trigger a panic. `extend_history_sync` calls `this.history_store.add_to_history(..)` before comparing the computed history root against the macro block header (`block.history_root()`), so the panic can happen before later rejection checks run. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "attackComplexity": "HIGH",
                "attackVector": "NETWORK",
                "availabilityImpact": "HIGH",
                "baseScore": 5.3,
                "baseSeverity": "MEDIUM",
                "confidentialityImpact": "NONE",
                "integrityImpact": "NONE",
                "privilegesRequired": "NONE",
                "scope": "UNCHANGED",
                "userInteraction": "REQUIRED",
                "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H",
                "version": "3.1"
              }
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-20",
                  "description": "CWE-20: Improper Input Validation",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            },
            {
              "descriptions": [
                {
                  "cweId": "CWE-617",
                  "description": "CWE-617: Reachable Assertion",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            },
            {
              "descriptions": [
                {
                  "cweId": "CWE-754",
                  "description": "CWE-754: Improper Check for Unusual or Exceptional Conditions",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-04-22T19:47:49.249Z",
            "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
            "shortName": "GitHub_M"
          },
          "references": [
            {
              "name": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-j99g-7rqw-q9jg",
              "tags": [
                "x_refsource_CONFIRM"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-j99g-7rqw-q9jg"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/pull/3656",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/pull/3656"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/commit/6f5511309c199d84b012fe6b9aba7e5582892c50",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/commit/6f5511309c199d84b012fe6b9aba7e5582892c50"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
            }
          ],
          "source": {
            "advisory": "GHSA-j99g-7rqw-q9jg",
            "discovery": "UNKNOWN"
          },
          "title": "nimiq-blockchain: Peer-triggerable panic during history sync"
        }
      },
      "cveMetadata": {
        "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "assignerShortName": "GitHub_M",
        "cveId": "CVE-2026-34066",
        "datePublished": "2026-04-22T19:47:49.249Z",
        "dateReserved": "2026-03-25T16:21:40.867Z",
        "dateUpdated": "2026-04-23T12:57:06.467Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-34065 (GCVE-0-2026-34065)

    Vulnerability from nvd – Published: 2026-04-22 19:45 – Updated: 2026-04-23 14:17
    VLAI
    Title
    nimiq-primitives: Node crash due to missing interlink validation in election macro block proposals
    Summary
    nimiq-primitives contains primitives (e.g., block, account, transaction) to be used in Nimiq's Rust implementation. Prior to version 1.3.0, an untrusted p2p peer can cause a node to panic by announcing an election macro block whose `validators` set contains an invalid compressed BLS voting key. Hashing an election macro header hashes `validators` and reaches `Validators::voting_keys()`, which calls `validator.voting_key.uncompress().unwrap()` and panics on invalid bytes. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.
    SSVC
    Exploitation: none Automatable: yes Technical Impact: partial
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-04-23 14:16 UTC
    CWE
    • CWE-252 - Unchecked Return Value
    • CWE-755 - Improper Handling of Exceptional Conditions
    Assigner
    GitHub_M CNA under the mitre root
    CNA scorecard C 72/100 over 8074 records in the last 180 days details
    Impacted products
    Vendor Product Version
    nimiq nimiq-primitives Affected: < 1.3.0
    Create a notification for this product.
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-34065",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "yes"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-04-23T14:16:52.791989Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-04-23T14:17:01.654Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "nimiq-primitives",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "descriptions": [
            {
              "lang": "en",
              "value": "nimiq-primitives contains primitives (e.g., block, account, transaction) to be used in Nimiq\u0027s Rust implementation. Prior to version 1.3.0, an untrusted p2p peer can cause a node to panic by announcing an election macro block whose `validators` set contains an invalid compressed BLS voting key. Hashing an election macro header hashes `validators` and reaches `Validators::voting_keys()`, which calls `validator.voting_key.uncompress().unwrap()` and panics on invalid bytes. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "attackComplexity": "LOW",
                "attackVector": "NETWORK",
                "availabilityImpact": "HIGH",
                "baseScore": 7.5,
                "baseSeverity": "HIGH",
                "confidentialityImpact": "NONE",
                "integrityImpact": "NONE",
                "privilegesRequired": "NONE",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
                "version": "3.1"
              }
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-252",
                  "description": "CWE-252: Unchecked Return Value",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            },
            {
              "descriptions": [
                {
                  "cweId": "CWE-755",
                  "description": "CWE-755: Improper Handling of Exceptional Conditions",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-04-22T19:45:01.171Z",
            "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
            "shortName": "GitHub_M"
          },
          "references": [
            {
              "name": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-7c4j-2m43-2mgh",
              "tags": [
                "x_refsource_CONFIRM"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-7c4j-2m43-2mgh"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/pull/3662",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/pull/3662"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/commit/e10eaebcd7774e5da6d0ff5e88ed13503474f0ff",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/commit/e10eaebcd7774e5da6d0ff5e88ed13503474f0ff"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
            }
          ],
          "source": {
            "advisory": "GHSA-7c4j-2m43-2mgh",
            "discovery": "UNKNOWN"
          },
          "title": "nimiq-primitives: Node crash due to missing interlink validation in election macro block proposals"
        }
      },
      "cveMetadata": {
        "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "assignerShortName": "GitHub_M",
        "cveId": "CVE-2026-34065",
        "datePublished": "2026-04-22T19:45:01.171Z",
        "dateReserved": "2026-03-25T16:21:40.867Z",
        "dateUpdated": "2026-04-23T14:17:01.654Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-34064 (GCVE-0-2026-34064)

    Vulnerability from nvd – Published: 2026-04-22 19:43 – Updated: 2026-04-23 16:25
    VLAI
    Title
    nimiq-account: Vesting insufficient funds error can panic
    Summary
    nimiq-account contains account primitives to be used in Nimiq's Rust implementation. Prior to version 1.3.0, `VestingContract::can_change_balance` returns `AccountError::InsufficientFunds` when `new_balance < min_cap`, but it constructs the error using `balance: self.balance - min_cap`. `Coin::sub` panics on underflow, so if an attacker can reach a state where `min_cap > balance`, the node crashes while trying to return an error. The `min_cap > balance` precondition is attacker-reachable because the vesting contract creation data (32-byte format) allows encoding `total_amount` without validating `total_amount <= transaction.value` (the real contract balance). After creating such a vesting contract, the attacker can broadcast an outgoing transaction to trigger the panic during mempool admission and block processing. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.
    SSVC
    Exploitation: none Automatable: yes Technical Impact: partial
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-04-23 13:06 UTC
    CWE
    • CWE-191 - Integer Underflow (Wrap or Wraparound)
    Assigner
    GitHub_M CNA under the mitre root
    CNA scorecard C 72/100 over 8074 records in the last 180 days details
    Impacted products
    Vendor Product Version
    nimiq nimiq-account Affected: < 1.3.0
    Create a notification for this product.
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-34064",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "yes"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-04-23T13:06:41.242710Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-04-23T16:25:19.186Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "nimiq-account",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "descriptions": [
            {
              "lang": "en",
              "value": "nimiq-account contains account primitives to be used in Nimiq\u0027s Rust implementation. Prior to version 1.3.0, `VestingContract::can_change_balance` returns `AccountError::InsufficientFunds` when `new_balance \u003c min_cap`, but it constructs the error using `balance: self.balance - min_cap`. `Coin::sub` panics on underflow, so if an attacker can reach a state where `min_cap \u003e balance`, the node crashes while trying to return an error. The `min_cap \u003e balance` precondition is attacker-reachable because the vesting contract creation data (32-byte format) allows encoding `total_amount` without validating `total_amount \u003c= transaction.value` (the real contract balance). After creating such a vesting contract, the attacker can broadcast an outgoing transaction to trigger the panic during mempool admission and block processing. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "attackComplexity": "LOW",
                "attackVector": "NETWORK",
                "availabilityImpact": "NONE",
                "baseScore": 5.3,
                "baseSeverity": "MEDIUM",
                "confidentialityImpact": "NONE",
                "integrityImpact": "LOW",
                "privilegesRequired": "NONE",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
                "version": "3.1"
              }
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-191",
                  "description": "CWE-191: Integer Underflow (Wrap or Wraparound)",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-04-22T19:43:04.453Z",
            "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
            "shortName": "GitHub_M"
          },
          "references": [
            {
              "name": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-vc34-39q2-m6q3",
              "tags": [
                "x_refsource_CONFIRM"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-vc34-39q2-m6q3"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/pull/3658",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/pull/3658"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/commit/4d01946f0b3d6c6e31786f91cdfb3eb902908da0",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/commit/4d01946f0b3d6c6e31786f91cdfb3eb902908da0"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
            }
          ],
          "source": {
            "advisory": "GHSA-vc34-39q2-m6q3",
            "discovery": "UNKNOWN"
          },
          "title": "nimiq-account: Vesting insufficient funds error can panic"
        }
      },
      "cveMetadata": {
        "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "assignerShortName": "GitHub_M",
        "cveId": "CVE-2026-34064",
        "datePublished": "2026-04-22T19:43:04.453Z",
        "dateReserved": "2026-03-25T16:21:40.867Z",
        "dateUpdated": "2026-04-23T16:25:19.186Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-34063 (GCVE-0-2026-34063)

    Vulnerability from nvd – Published: 2026-04-22 19:40 – Updated: 2026-04-23 13:54
    VLAI
    Title
    network-libp2p: Peer can crash the node by opening discovery protocol substream twice
    Summary
    Nimiq's network-libp2p is a Nimiq network implementation based on libp2p. Prior to version 1.3.0, `network-libp2p` discovery uses a libp2p `ConnectionHandler` state machine. the handler assumes there is at most one inbound and one outbound discovery substream per connection. if a remote peer opens/negotiate the discovery protocol substream a second time on the same connection, the handler hits a `panic!(\"Inbound already connected\")` / `panic!(\"Outbound already connected\")` path instead of failing closed. This causes a remote crash of the networking task (swarm), taking the node's p2p networking offline until restart. The patch for this vulnerability is formally released as part of v1.3.0. No known workarounds are available.
    SSVC
    Exploitation: none Automatable: yes Technical Impact: partial
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-04-23 13:51 UTC
    CWE
    Assigner
    GitHub_M CNA under the mitre root
    CNA scorecard C 72/100 over 8074 records in the last 180 days details
    Impacted products
    Vendor Product Version
    nimiq network-libp2p Affected: < 1.3.0
    Create a notification for this product.
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-34063",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "yes"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-04-23T13:51:51.197194Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-04-23T13:54:06.421Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "network-libp2p",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "descriptions": [
            {
              "lang": "en",
              "value": "Nimiq\u0027s network-libp2p is a Nimiq network implementation based on libp2p. Prior to version 1.3.0, `network-libp2p` discovery uses a libp2p `ConnectionHandler` state machine. the handler assumes there is at most one inbound and one outbound discovery substream per connection. if a remote peer opens/negotiate the discovery protocol substream a second time on the same connection, the handler hits a `panic!(\\\"Inbound already connected\\\")` / `panic!(\\\"Outbound already connected\\\")` path instead of failing closed. This causes a remote crash of the networking task (swarm), taking the node\u0027s p2p networking offline until restart. The patch for this vulnerability is formally released as part of v1.3.0. No known workarounds are available."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "attackComplexity": "LOW",
                "attackVector": "NETWORK",
                "availabilityImpact": "HIGH",
                "baseScore": 7.5,
                "baseSeverity": "HIGH",
                "confidentialityImpact": "NONE",
                "integrityImpact": "NONE",
                "privilegesRequired": "NONE",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
                "version": "3.1"
              }
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-617",
                  "description": "CWE-617: Reachable Assertion",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-04-22T19:40:26.837Z",
            "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
            "shortName": "GitHub_M"
          },
          "references": [
            {
              "name": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-74hp-mhfx-m45h",
              "tags": [
                "x_refsource_CONFIRM"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-74hp-mhfx-m45h"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/pull/3666",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/pull/3666"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/commit/e0d4e01994f061bf41d3c2835bc74040d3c084f5",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/commit/e0d4e01994f061bf41d3c2835bc74040d3c084f5"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
            }
          ],
          "source": {
            "advisory": "GHSA-74hp-mhfx-m45h",
            "discovery": "UNKNOWN"
          },
          "title": "network-libp2p: Peer can crash the node by opening discovery protocol substream twice"
        }
      },
      "cveMetadata": {
        "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "assignerShortName": "GitHub_M",
        "cveId": "CVE-2026-34063",
        "datePublished": "2026-04-22T19:40:26.837Z",
        "dateReserved": "2026-03-25T16:21:40.866Z",
        "dateUpdated": "2026-04-23T13:54:06.421Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-34062 (GCVE-0-2026-34062)

    Vulnerability from nvd – Published: 2026-04-22 19:23 – Updated: 2026-04-23 12:57
    VLAI
    Title
    Nimiq has Allocation of Resources Without Limits or Throttling in its libp2p request/response
    Summary
    nimiq-libp2p is a Nimiq network implementation based on libp2p. Prior to version 1.3.0, `MessageCodec::read_request` and `read_response` call `read_to_end()` on inbound substreams, so a remote peer can send only a partial frame and keep the substream open. because `Behaviour::new` also sets `with_max_concurrent_streams(1000)`, the node exposes a much larger stalled-slot budget than the library default. The patch for this vulnerability is formally released as part of v1.3.0. No known workarounds are available.
    SSVC
    Exploitation: none Automatable: yes Technical Impact: partial
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-04-23 12:57 UTC
    CWE
    • CWE-770 - Allocation of Resources Without Limits or Throttling
    Assigner
    GitHub_M CNA under the mitre root
    CNA scorecard C 72/100 over 8074 records in the last 180 days details
    Impacted products
    Vendor Product Version
    nimiq network-libp2p Affected: < 1.3.0
    Create a notification for this product.
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-34062",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "yes"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-04-23T12:57:31.642650Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-04-23T12:57:42.075Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "network-libp2p",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "descriptions": [
            {
              "lang": "en",
              "value": "nimiq-libp2p is a Nimiq network implementation based on libp2p. Prior to version 1.3.0, `MessageCodec::read_request` and `read_response` call `read_to_end()` on inbound substreams, so a remote peer can send only a partial frame and keep the substream open. because `Behaviour::new` also sets `with_max_concurrent_streams(1000)`, the node exposes a much larger stalled-slot budget than the library default. The patch for this vulnerability is formally released as part of v1.3.0. No known workarounds are available."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "attackComplexity": "LOW",
                "attackVector": "NETWORK",
                "availabilityImpact": "LOW",
                "baseScore": 5.3,
                "baseSeverity": "MEDIUM",
                "confidentialityImpact": "NONE",
                "integrityImpact": "NONE",
                "privilegesRequired": "NONE",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
                "version": "3.1"
              }
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-770",
                  "description": "CWE-770: Allocation of Resources Without Limits or Throttling",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-04-22T19:23:36.838Z",
            "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
            "shortName": "GitHub_M"
          },
          "references": [
            {
              "name": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-gh7r-qh4p-q4fr",
              "tags": [
                "x_refsource_CONFIRM"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-gh7r-qh4p-q4fr"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/commit/c021a5337b808c73571b44999f9753051bac7508",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/commit/c021a5337b808c73571b44999f9753051bac7508"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
            }
          ],
          "source": {
            "advisory": "GHSA-gh7r-qh4p-q4fr",
            "discovery": "UNKNOWN"
          },
          "title": "Nimiq has Allocation of Resources Without Limits or Throttling in its libp2p request/response"
        }
      },
      "cveMetadata": {
        "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "assignerShortName": "GitHub_M",
        "cveId": "CVE-2026-34062",
        "datePublished": "2026-04-22T19:23:36.838Z",
        "dateReserved": "2026-03-25T16:21:40.866Z",
        "dateUpdated": "2026-04-23T12:57:42.075Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-33471 (GCVE-0-2026-33471)

    Vulnerability from nvd – Published: 2026-04-22 19:13 – Updated: 2026-04-23 14:15
    VLAI
    Title
    nimiq-block has skip block quorum bypass via out-of-range BitSet indices & u16 truncation
    Summary
    nimiq-block contains block primitives to be used in Nimiq's Rust implementation. `SkipBlockProof::verify` computes its quorum check using `BitSet.len()`, then iterates `BitSet` indices and casts each `usize` index to `u16` (`slot as u16`) for slot lookup. Prior to version 1.3.0, if an attacker can get a `SkipBlockProof` verified where `MultiSignature.signers` contains out-of-range indices spaced by 65536, these indices inflate `len()` but collide onto the same in-range `u16` slot during aggregation. This makes it possible for a malicious validator with far fewer than `2f+1` real signer slots to pass skip block proof verification by multiplying a single BLS signature by the same factor. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.
    SSVC
    Exploitation: none Automatable: no Technical Impact: partial
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-04-23 14:15 UTC
    CWE
    • CWE-20 - Improper Input Validation
    • CWE-190 - Integer Overflow or Wraparound
    • CWE-345 - Insufficient Verification of Data Authenticity
    • CWE-1284 - Improper Validation of Specified Quantity in Input
    Assigner
    GitHub_M CNA under the mitre root
    CNA scorecard C 72/100 over 8074 records in the last 180 days details
    Impacted products
    Vendor Product Version
    nimiq nimiq-block Affected: < 1.3.0
    Create a notification for this product.
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-33471",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-04-23T14:15:09.611330Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-04-23T14:15:20.570Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "nimiq-block",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "descriptions": [
            {
              "lang": "en",
              "value": "nimiq-block contains block primitives to be used in Nimiq\u0027s Rust implementation. `SkipBlockProof::verify` computes its quorum check using `BitSet.len()`, then iterates `BitSet` indices and casts each `usize` index to `u16` (`slot as u16`) for slot lookup. Prior to version 1.3.0, if an attacker can get a `SkipBlockProof` verified where `MultiSignature.signers` contains out-of-range indices spaced by 65536, these indices inflate `len()` but collide onto the same in-range `u16` slot during aggregation. This makes it possible for a malicious validator with far fewer than `2f+1` real signer slots to pass skip block proof verification by multiplying a single BLS signature by the same factor. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "attackComplexity": "LOW",
                "attackVector": "NETWORK",
                "availabilityImpact": "HIGH",
                "baseScore": 9.6,
                "baseSeverity": "CRITICAL",
                "confidentialityImpact": "NONE",
                "integrityImpact": "HIGH",
                "privilegesRequired": "LOW",
                "scope": "CHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H",
                "version": "3.1"
              }
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-20",
                  "description": "CWE-20: Improper Input Validation",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            },
            {
              "descriptions": [
                {
                  "cweId": "CWE-190",
                  "description": "CWE-190: Integer Overflow or Wraparound",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            },
            {
              "descriptions": [
                {
                  "cweId": "CWE-345",
                  "description": "CWE-345: Insufficient Verification of Data Authenticity",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            },
            {
              "descriptions": [
                {
                  "cweId": "CWE-1284",
                  "description": "CWE-1284: Improper Validation of Specified Quantity in Input",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-04-22T19:45:53.754Z",
            "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
            "shortName": "GitHub_M"
          },
          "references": [
            {
              "name": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-6973-8887-87ff",
              "tags": [
                "x_refsource_CONFIRM"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-6973-8887-87ff"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/commit/d02059053181ed8ddad6b59a0adfd661ef5cd823",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/commit/d02059053181ed8ddad6b59a0adfd661ef5cd823"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
            }
          ],
          "source": {
            "advisory": "GHSA-6973-8887-87ff",
            "discovery": "UNKNOWN"
          },
          "title": "nimiq-block has skip block quorum bypass via out-of-range BitSet indices \u0026 u16 truncation"
        }
      },
      "cveMetadata": {
        "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "assignerShortName": "GitHub_M",
        "cveId": "CVE-2026-33471",
        "datePublished": "2026-04-22T19:13:04.687Z",
        "dateReserved": "2026-03-20T16:16:48.969Z",
        "dateUpdated": "2026-04-23T14:15:20.570Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-34068 (GCVE-0-2026-34068)

    Vulnerability from cvelistv5 – Published: 2026-04-22 19:55 – Updated: 2026-04-23 12:56
    VLAI
    Title
    nimiq-transaction: UpdateValidator transactions allows voting key change without proof-of-knowledge
    Summary
    nimiq-transaction provides the transaction primitive to be used in Nimiq's Rust implementation. Prior to version 1.3.0, the staking contract accepts `UpdateValidator` transactions that set `new_voting_key=Some(...)` while omitting `new_proof_of_knowledge`. this skips the proof-of-knowledge requirement that is needed to prevent BLS rogue-key attacks when public keys are aggregated. Because tendermint macro block justification verification aggregates validator voting keys and verifies a single aggregated BLS signature against that aggregate public key, a rogue-key voting key in the validator set can allow an attacker to forge a quorum-looking justification while only producing a single signature. While the impact is critical, the exploitability is low: The voting keys are fixed for the epoch, so the attacker would need to know the next epoch validator set (chosen through VRF), which is unlikely. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.
    SSVC
    Exploitation: none Automatable: no Technical Impact: partial
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-04-23 12:56 UTC
    CWE
    • CWE-347 - Improper Verification of Cryptographic Signature
    Assigner
    GitHub_M CNA under the mitre root
    CNA scorecard C 72/100 over 8074 records in the last 180 days details
    Impacted products
    Vendor Product Version
    nimiq nimiq-transaction Affected: < 1.3.0
    Create a notification for this product.
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-34068",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-04-23T12:56:19.048672Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-04-23T12:56:27.980Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "nimiq-transaction",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "descriptions": [
            {
              "lang": "en",
              "value": "nimiq-transaction provides the transaction primitive to be used in Nimiq\u0027s Rust implementation. Prior to version 1.3.0, the staking contract accepts `UpdateValidator` transactions that set `new_voting_key=Some(...)` while omitting `new_proof_of_knowledge`. this skips the proof-of-knowledge requirement that is needed to prevent BLS rogue-key attacks when public keys are aggregated. Because tendermint macro block justification verification aggregates validator voting keys and verifies a single aggregated BLS signature against that aggregate public key, a rogue-key voting key in the validator set can allow an attacker to forge a quorum-looking justification while only producing a single signature. While the impact is critical, the exploitability is low: The voting keys are fixed for the epoch, so the attacker would need to know the next epoch validator set (chosen through VRF), which is unlikely. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "attackComplexity": "HIGH",
                "attackVector": "NETWORK",
                "availabilityImpact": "NONE",
                "baseScore": 6.8,
                "baseSeverity": "MEDIUM",
                "confidentialityImpact": "NONE",
                "integrityImpact": "HIGH",
                "privilegesRequired": "NONE",
                "scope": "CHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N",
                "version": "3.1"
              }
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-347",
                  "description": "CWE-347: Improper Verification of Cryptographic Signature",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-04-22T19:55:24.731Z",
            "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
            "shortName": "GitHub_M"
          },
          "references": [
            {
              "name": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-pf4j-pf3w-95f9",
              "tags": [
                "x_refsource_CONFIRM"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-pf4j-pf3w-95f9"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/pull/3654",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/pull/3654"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/commit/e7f0ab7d2115e17d6e5548ddc60f10df1a5d645f",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/commit/e7f0ab7d2115e17d6e5548ddc60f10df1a5d645f"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
            }
          ],
          "source": {
            "advisory": "GHSA-pf4j-pf3w-95f9",
            "discovery": "UNKNOWN"
          },
          "title": "nimiq-transaction: UpdateValidator transactions allows voting key change without proof-of-knowledge"
        }
      },
      "cveMetadata": {
        "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "assignerShortName": "GitHub_M",
        "cveId": "CVE-2026-34068",
        "datePublished": "2026-04-22T19:55:08.219Z",
        "dateReserved": "2026-03-25T16:21:40.867Z",
        "dateUpdated": "2026-04-23T12:56:27.980Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-34067 (GCVE-0-2026-34067)

    Vulnerability from cvelistv5 – Published: 2026-04-22 19:52 – Updated: 2026-04-23 14:17
    VLAI
    Title
    nimiq-transaction vulnerable to panic via `HistoryTreeProof` length mismatch
    Summary
    nimiq-transaction provides the transaction primitive to be used in Nimiq's Rust implementation. Prior to version 1.3.0, `HistoryTreeProof::verify` panics on a malformed proof where `history.len() != positions.len()` due to `assert_eq!(history.len(), positions.len())`. The proof object is derived from untrusted p2p responses (`ResponseTransactionsProof.proof`) and is therefore attacker-controlled at the network boundary until validated. A malicious peer could trigger a crash by returning a crafted inclusion proof with a length mismatch. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.
    SSVC
    Exploitation: none Automatable: no Technical Impact: partial
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-04-23 14:17 UTC
    CWE
    Assigner
    GitHub_M CNA under the mitre root
    CNA scorecard C 72/100 over 8074 records in the last 180 days details
    Impacted products
    Vendor Product Version
    nimiq nimiq-transaction Affected: < 1.3.0
    Create a notification for this product.
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-34067",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-04-23T14:17:49.301869Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-04-23T14:17:59.735Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "nimiq-transaction",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "descriptions": [
            {
              "lang": "en",
              "value": "nimiq-transaction provides the transaction primitive to be used in Nimiq\u0027s Rust implementation. Prior to version 1.3.0, `HistoryTreeProof::verify` panics on a malformed proof where `history.len() != positions.len()` due to `assert_eq!(history.len(), positions.len())`. The proof object is derived from untrusted p2p responses (`ResponseTransactionsProof.proof`) and is therefore attacker-controlled at the network boundary until validated. A malicious peer could trigger a crash by returning a crafted inclusion proof with a length mismatch. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "attackComplexity": "HIGH",
                "attackVector": "NETWORK",
                "availabilityImpact": "LOW",
                "baseScore": 3.1,
                "baseSeverity": "LOW",
                "confidentialityImpact": "NONE",
                "integrityImpact": "NONE",
                "privilegesRequired": "NONE",
                "scope": "UNCHANGED",
                "userInteraction": "REQUIRED",
                "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L",
                "version": "3.1"
              }
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-617",
                  "description": "CWE-617: Reachable Assertion",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-04-22T19:52:43.916Z",
            "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
            "shortName": "GitHub_M"
          },
          "references": [
            {
              "name": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-264v-m8fm-76jm",
              "tags": [
                "x_refsource_CONFIRM"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-264v-m8fm-76jm"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/pull/3659",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/pull/3659"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/commit/6ff0800e8e031363e787c827d8d033e5694e4e6a",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/commit/6ff0800e8e031363e787c827d8d033e5694e4e6a"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
            }
          ],
          "source": {
            "advisory": "GHSA-264v-m8fm-76jm",
            "discovery": "UNKNOWN"
          },
          "title": "nimiq-transaction vulnerable to panic via `HistoryTreeProof` length mismatch"
        }
      },
      "cveMetadata": {
        "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "assignerShortName": "GitHub_M",
        "cveId": "CVE-2026-34067",
        "datePublished": "2026-04-22T19:52:43.916Z",
        "dateReserved": "2026-03-25T16:21:40.867Z",
        "dateUpdated": "2026-04-23T14:17:59.735Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-34066 (GCVE-0-2026-34066)

    Vulnerability from cvelistv5 – Published: 2026-04-22 19:47 – Updated: 2026-04-23 12:57
    VLAI
    Title
    nimiq-blockchain: Peer-triggerable panic during history sync
    Summary
    nimiq-blockchain provides persistent block storage for Nimiq's Rust implementation. Prior to version 1.3.0, `HistoryStore::put_historic_txns` uses an `assert!` to enforce invariants about `HistoricTransaction.block_number` (must be within the macro block being pushed and within the same epoch). During history sync, a peer can influence the `history: &[HistoricTransaction]` input passed into `Blockchain::push_history_sync`, and a malformed history list can violate these invariants and trigger a panic. `extend_history_sync` calls `this.history_store.add_to_history(..)` before comparing the computed history root against the macro block header (`block.history_root()`), so the panic can happen before later rejection checks run. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.
    SSVC
    Exploitation: none Automatable: no Technical Impact: partial
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-04-23 12:56 UTC
    CWE
    • CWE-20 - Improper Input Validation
    • CWE-617 - Reachable Assertion
    • CWE-754 - Improper Check for Unusual or Exceptional Conditions
    Assigner
    GitHub_M CNA under the mitre root
    CNA scorecard C 72/100 over 8074 records in the last 180 days details
    Impacted products
    Vendor Product Version
    nimiq nimiq-blockchain Affected: < 1.3.0
    Create a notification for this product.
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-34066",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-04-23T12:56:55.597573Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-04-23T12:57:06.467Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "nimiq-blockchain",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "descriptions": [
            {
              "lang": "en",
              "value": "nimiq-blockchain provides persistent block storage for Nimiq\u0027s Rust implementation. Prior to version 1.3.0, `HistoryStore::put_historic_txns` uses an `assert!` to enforce invariants about `HistoricTransaction.block_number` (must be within the macro block being pushed and within the same epoch). During history sync, a peer can influence the `history: \u0026[HistoricTransaction]` input passed into `Blockchain::push_history_sync`, and a malformed history list can violate these invariants and trigger a panic. `extend_history_sync` calls `this.history_store.add_to_history(..)` before comparing the computed history root against the macro block header (`block.history_root()`), so the panic can happen before later rejection checks run. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "attackComplexity": "HIGH",
                "attackVector": "NETWORK",
                "availabilityImpact": "HIGH",
                "baseScore": 5.3,
                "baseSeverity": "MEDIUM",
                "confidentialityImpact": "NONE",
                "integrityImpact": "NONE",
                "privilegesRequired": "NONE",
                "scope": "UNCHANGED",
                "userInteraction": "REQUIRED",
                "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H",
                "version": "3.1"
              }
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-20",
                  "description": "CWE-20: Improper Input Validation",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            },
            {
              "descriptions": [
                {
                  "cweId": "CWE-617",
                  "description": "CWE-617: Reachable Assertion",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            },
            {
              "descriptions": [
                {
                  "cweId": "CWE-754",
                  "description": "CWE-754: Improper Check for Unusual or Exceptional Conditions",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-04-22T19:47:49.249Z",
            "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
            "shortName": "GitHub_M"
          },
          "references": [
            {
              "name": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-j99g-7rqw-q9jg",
              "tags": [
                "x_refsource_CONFIRM"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-j99g-7rqw-q9jg"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/pull/3656",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/pull/3656"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/commit/6f5511309c199d84b012fe6b9aba7e5582892c50",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/commit/6f5511309c199d84b012fe6b9aba7e5582892c50"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
            }
          ],
          "source": {
            "advisory": "GHSA-j99g-7rqw-q9jg",
            "discovery": "UNKNOWN"
          },
          "title": "nimiq-blockchain: Peer-triggerable panic during history sync"
        }
      },
      "cveMetadata": {
        "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "assignerShortName": "GitHub_M",
        "cveId": "CVE-2026-34066",
        "datePublished": "2026-04-22T19:47:49.249Z",
        "dateReserved": "2026-03-25T16:21:40.867Z",
        "dateUpdated": "2026-04-23T12:57:06.467Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-34065 (GCVE-0-2026-34065)

    Vulnerability from cvelistv5 – Published: 2026-04-22 19:45 – Updated: 2026-04-23 14:17
    VLAI
    Title
    nimiq-primitives: Node crash due to missing interlink validation in election macro block proposals
    Summary
    nimiq-primitives contains primitives (e.g., block, account, transaction) to be used in Nimiq's Rust implementation. Prior to version 1.3.0, an untrusted p2p peer can cause a node to panic by announcing an election macro block whose `validators` set contains an invalid compressed BLS voting key. Hashing an election macro header hashes `validators` and reaches `Validators::voting_keys()`, which calls `validator.voting_key.uncompress().unwrap()` and panics on invalid bytes. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.
    SSVC
    Exploitation: none Automatable: yes Technical Impact: partial
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-04-23 14:16 UTC
    CWE
    • CWE-252 - Unchecked Return Value
    • CWE-755 - Improper Handling of Exceptional Conditions
    Assigner
    GitHub_M CNA under the mitre root
    CNA scorecard C 72/100 over 8074 records in the last 180 days details
    Impacted products
    Vendor Product Version
    nimiq nimiq-primitives Affected: < 1.3.0
    Create a notification for this product.
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-34065",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "yes"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-04-23T14:16:52.791989Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-04-23T14:17:01.654Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "nimiq-primitives",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "descriptions": [
            {
              "lang": "en",
              "value": "nimiq-primitives contains primitives (e.g., block, account, transaction) to be used in Nimiq\u0027s Rust implementation. Prior to version 1.3.0, an untrusted p2p peer can cause a node to panic by announcing an election macro block whose `validators` set contains an invalid compressed BLS voting key. Hashing an election macro header hashes `validators` and reaches `Validators::voting_keys()`, which calls `validator.voting_key.uncompress().unwrap()` and panics on invalid bytes. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "attackComplexity": "LOW",
                "attackVector": "NETWORK",
                "availabilityImpact": "HIGH",
                "baseScore": 7.5,
                "baseSeverity": "HIGH",
                "confidentialityImpact": "NONE",
                "integrityImpact": "NONE",
                "privilegesRequired": "NONE",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
                "version": "3.1"
              }
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-252",
                  "description": "CWE-252: Unchecked Return Value",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            },
            {
              "descriptions": [
                {
                  "cweId": "CWE-755",
                  "description": "CWE-755: Improper Handling of Exceptional Conditions",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-04-22T19:45:01.171Z",
            "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
            "shortName": "GitHub_M"
          },
          "references": [
            {
              "name": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-7c4j-2m43-2mgh",
              "tags": [
                "x_refsource_CONFIRM"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-7c4j-2m43-2mgh"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/pull/3662",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/pull/3662"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/commit/e10eaebcd7774e5da6d0ff5e88ed13503474f0ff",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/commit/e10eaebcd7774e5da6d0ff5e88ed13503474f0ff"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
            }
          ],
          "source": {
            "advisory": "GHSA-7c4j-2m43-2mgh",
            "discovery": "UNKNOWN"
          },
          "title": "nimiq-primitives: Node crash due to missing interlink validation in election macro block proposals"
        }
      },
      "cveMetadata": {
        "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "assignerShortName": "GitHub_M",
        "cveId": "CVE-2026-34065",
        "datePublished": "2026-04-22T19:45:01.171Z",
        "dateReserved": "2026-03-25T16:21:40.867Z",
        "dateUpdated": "2026-04-23T14:17:01.654Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-34064 (GCVE-0-2026-34064)

    Vulnerability from cvelistv5 – Published: 2026-04-22 19:43 – Updated: 2026-04-23 16:25
    VLAI
    Title
    nimiq-account: Vesting insufficient funds error can panic
    Summary
    nimiq-account contains account primitives to be used in Nimiq's Rust implementation. Prior to version 1.3.0, `VestingContract::can_change_balance` returns `AccountError::InsufficientFunds` when `new_balance < min_cap`, but it constructs the error using `balance: self.balance - min_cap`. `Coin::sub` panics on underflow, so if an attacker can reach a state where `min_cap > balance`, the node crashes while trying to return an error. The `min_cap > balance` precondition is attacker-reachable because the vesting contract creation data (32-byte format) allows encoding `total_amount` without validating `total_amount <= transaction.value` (the real contract balance). After creating such a vesting contract, the attacker can broadcast an outgoing transaction to trigger the panic during mempool admission and block processing. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.
    SSVC
    Exploitation: none Automatable: yes Technical Impact: partial
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-04-23 13:06 UTC
    CWE
    • CWE-191 - Integer Underflow (Wrap or Wraparound)
    Assigner
    GitHub_M CNA under the mitre root
    CNA scorecard C 72/100 over 8074 records in the last 180 days details
    Impacted products
    Vendor Product Version
    nimiq nimiq-account Affected: < 1.3.0
    Create a notification for this product.
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-34064",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "yes"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-04-23T13:06:41.242710Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-04-23T16:25:19.186Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "nimiq-account",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "descriptions": [
            {
              "lang": "en",
              "value": "nimiq-account contains account primitives to be used in Nimiq\u0027s Rust implementation. Prior to version 1.3.0, `VestingContract::can_change_balance` returns `AccountError::InsufficientFunds` when `new_balance \u003c min_cap`, but it constructs the error using `balance: self.balance - min_cap`. `Coin::sub` panics on underflow, so if an attacker can reach a state where `min_cap \u003e balance`, the node crashes while trying to return an error. The `min_cap \u003e balance` precondition is attacker-reachable because the vesting contract creation data (32-byte format) allows encoding `total_amount` without validating `total_amount \u003c= transaction.value` (the real contract balance). After creating such a vesting contract, the attacker can broadcast an outgoing transaction to trigger the panic during mempool admission and block processing. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "attackComplexity": "LOW",
                "attackVector": "NETWORK",
                "availabilityImpact": "NONE",
                "baseScore": 5.3,
                "baseSeverity": "MEDIUM",
                "confidentialityImpact": "NONE",
                "integrityImpact": "LOW",
                "privilegesRequired": "NONE",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
                "version": "3.1"
              }
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-191",
                  "description": "CWE-191: Integer Underflow (Wrap or Wraparound)",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-04-22T19:43:04.453Z",
            "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
            "shortName": "GitHub_M"
          },
          "references": [
            {
              "name": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-vc34-39q2-m6q3",
              "tags": [
                "x_refsource_CONFIRM"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-vc34-39q2-m6q3"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/pull/3658",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/pull/3658"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/commit/4d01946f0b3d6c6e31786f91cdfb3eb902908da0",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/commit/4d01946f0b3d6c6e31786f91cdfb3eb902908da0"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
            }
          ],
          "source": {
            "advisory": "GHSA-vc34-39q2-m6q3",
            "discovery": "UNKNOWN"
          },
          "title": "nimiq-account: Vesting insufficient funds error can panic"
        }
      },
      "cveMetadata": {
        "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "assignerShortName": "GitHub_M",
        "cveId": "CVE-2026-34064",
        "datePublished": "2026-04-22T19:43:04.453Z",
        "dateReserved": "2026-03-25T16:21:40.867Z",
        "dateUpdated": "2026-04-23T16:25:19.186Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-34063 (GCVE-0-2026-34063)

    Vulnerability from cvelistv5 – Published: 2026-04-22 19:40 – Updated: 2026-04-23 13:54
    VLAI
    Title
    network-libp2p: Peer can crash the node by opening discovery protocol substream twice
    Summary
    Nimiq's network-libp2p is a Nimiq network implementation based on libp2p. Prior to version 1.3.0, `network-libp2p` discovery uses a libp2p `ConnectionHandler` state machine. the handler assumes there is at most one inbound and one outbound discovery substream per connection. if a remote peer opens/negotiate the discovery protocol substream a second time on the same connection, the handler hits a `panic!(\"Inbound already connected\")` / `panic!(\"Outbound already connected\")` path instead of failing closed. This causes a remote crash of the networking task (swarm), taking the node's p2p networking offline until restart. The patch for this vulnerability is formally released as part of v1.3.0. No known workarounds are available.
    SSVC
    Exploitation: none Automatable: yes Technical Impact: partial
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-04-23 13:51 UTC
    CWE
    Assigner
    GitHub_M CNA under the mitre root
    CNA scorecard C 72/100 over 8074 records in the last 180 days details
    Impacted products
    Vendor Product Version
    nimiq network-libp2p Affected: < 1.3.0
    Create a notification for this product.
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-34063",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "yes"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-04-23T13:51:51.197194Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-04-23T13:54:06.421Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "network-libp2p",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "descriptions": [
            {
              "lang": "en",
              "value": "Nimiq\u0027s network-libp2p is a Nimiq network implementation based on libp2p. Prior to version 1.3.0, `network-libp2p` discovery uses a libp2p `ConnectionHandler` state machine. the handler assumes there is at most one inbound and one outbound discovery substream per connection. if a remote peer opens/negotiate the discovery protocol substream a second time on the same connection, the handler hits a `panic!(\\\"Inbound already connected\\\")` / `panic!(\\\"Outbound already connected\\\")` path instead of failing closed. This causes a remote crash of the networking task (swarm), taking the node\u0027s p2p networking offline until restart. The patch for this vulnerability is formally released as part of v1.3.0. No known workarounds are available."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "attackComplexity": "LOW",
                "attackVector": "NETWORK",
                "availabilityImpact": "HIGH",
                "baseScore": 7.5,
                "baseSeverity": "HIGH",
                "confidentialityImpact": "NONE",
                "integrityImpact": "NONE",
                "privilegesRequired": "NONE",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
                "version": "3.1"
              }
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-617",
                  "description": "CWE-617: Reachable Assertion",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-04-22T19:40:26.837Z",
            "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
            "shortName": "GitHub_M"
          },
          "references": [
            {
              "name": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-74hp-mhfx-m45h",
              "tags": [
                "x_refsource_CONFIRM"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-74hp-mhfx-m45h"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/pull/3666",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/pull/3666"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/commit/e0d4e01994f061bf41d3c2835bc74040d3c084f5",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/commit/e0d4e01994f061bf41d3c2835bc74040d3c084f5"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
            }
          ],
          "source": {
            "advisory": "GHSA-74hp-mhfx-m45h",
            "discovery": "UNKNOWN"
          },
          "title": "network-libp2p: Peer can crash the node by opening discovery protocol substream twice"
        }
      },
      "cveMetadata": {
        "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "assignerShortName": "GitHub_M",
        "cveId": "CVE-2026-34063",
        "datePublished": "2026-04-22T19:40:26.837Z",
        "dateReserved": "2026-03-25T16:21:40.866Z",
        "dateUpdated": "2026-04-23T13:54:06.421Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-34062 (GCVE-0-2026-34062)

    Vulnerability from cvelistv5 – Published: 2026-04-22 19:23 – Updated: 2026-04-23 12:57
    VLAI
    Title
    Nimiq has Allocation of Resources Without Limits or Throttling in its libp2p request/response
    Summary
    nimiq-libp2p is a Nimiq network implementation based on libp2p. Prior to version 1.3.0, `MessageCodec::read_request` and `read_response` call `read_to_end()` on inbound substreams, so a remote peer can send only a partial frame and keep the substream open. because `Behaviour::new` also sets `with_max_concurrent_streams(1000)`, the node exposes a much larger stalled-slot budget than the library default. The patch for this vulnerability is formally released as part of v1.3.0. No known workarounds are available.
    SSVC
    Exploitation: none Automatable: yes Technical Impact: partial
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-04-23 12:57 UTC
    CWE
    • CWE-770 - Allocation of Resources Without Limits or Throttling
    Assigner
    GitHub_M CNA under the mitre root
    CNA scorecard C 72/100 over 8074 records in the last 180 days details
    Impacted products
    Vendor Product Version
    nimiq network-libp2p Affected: < 1.3.0
    Create a notification for this product.
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-34062",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "yes"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-04-23T12:57:31.642650Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-04-23T12:57:42.075Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "network-libp2p",
              "vendor": "nimiq",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 1.3.0"
                }
              ]
            }
          ],
          "descriptions": [
            {
              "lang": "en",
              "value": "nimiq-libp2p is a Nimiq network implementation based on libp2p. Prior to version 1.3.0, `MessageCodec::read_request` and `read_response` call `read_to_end()` on inbound substreams, so a remote peer can send only a partial frame and keep the substream open. because `Behaviour::new` also sets `with_max_concurrent_streams(1000)`, the node exposes a much larger stalled-slot budget than the library default. The patch for this vulnerability is formally released as part of v1.3.0. No known workarounds are available."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "attackComplexity": "LOW",
                "attackVector": "NETWORK",
                "availabilityImpact": "LOW",
                "baseScore": 5.3,
                "baseSeverity": "MEDIUM",
                "confidentialityImpact": "NONE",
                "integrityImpact": "NONE",
                "privilegesRequired": "NONE",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
                "version": "3.1"
              }
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-770",
                  "description": "CWE-770: Allocation of Resources Without Limits or Throttling",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-04-22T19:23:36.838Z",
            "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
            "shortName": "GitHub_M"
          },
          "references": [
            {
              "name": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-gh7r-qh4p-q4fr",
              "tags": [
                "x_refsource_CONFIRM"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-gh7r-qh4p-q4fr"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/commit/c021a5337b808c73571b44999f9753051bac7508",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/commit/c021a5337b808c73571b44999f9753051bac7508"
            },
            {
              "name": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0"
            }
          ],
          "source": {
            "advisory": "GHSA-gh7r-qh4p-q4fr",
            "discovery": "UNKNOWN"
          },
          "title": "Nimiq has Allocation of Resources Without Limits or Throttling in its libp2p request/response"
        }
      },
      "cveMetadata": {
        "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "assignerShortName": "GitHub_M",
        "cveId": "CVE-2026-34062",
        "datePublished": "2026-04-22T19:23:36.838Z",
        "dateReserved": "2026-03-25T16:21:40.866Z",
        "dateUpdated": "2026-04-23T12:57:42.075Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }