Skip to main content
VulnerabilityPublished Updated

CVE-2026-16000: Legion of · Missing Cryptographic Step

Source GCVE Database

0
Authoritative record:CVE-2026-16000· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 2.7.0 soon.

Data as of 27 Oct 2026, 20:15 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 2.7.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade bc-csharp and BouncyCastle.Cryptography to 2.7.0.

Affected software

ProductAffectedFixed in
Legion of the Bouncy Castle Inc.bc-csharpAffected
  • <2.7.0
Fixed in
  • 2.7.0
NuGetBouncyCastle.Cryptographypkg:nuget/BouncyCastle.CryptographyOther threatsAffected
  • <2.7.0
Fixed in
  • 2.7.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Bouncy Castle bc-csharp version 2.7.0 and later. Users should upgrade to version 2.7.0 or newer to remediate this vulnerability. Until then, avoid using KCcmBlockCipher without associated data. No other mitigation is indicated.

Description

A vulnerability in the DSTU 7624 CCM mode implementation (KCcmBlockCipher) in Bouncy Castle bc-csharp before version 2.7.0 allows attackers to forge ciphertexts with valid authentication tags when no associated data is used. This occurs because a critical cryptographic step binding the nonce, message length, and parameter flags into the CBC-MAC was skipped if associated data was absent, causing the authentication tag to be independent of the nonce. Only applications using KCcmBlockCipher directly without associated data are affected.

References

Community reviews

Loading reviews…