CVE-2026-12817 is a high-severity vulnerability in Legion of the Bouncy Castle Inc.'s BC-JAVA library affecting multiple versions before certain fixed releases. The flaw involves improper validation of the integrity check value during OpenPGP AEAD decryption, where the final tag is skipped on chunk-aligned data. This affects Bouncy Castle for Java versions prior to 1.85, LTS versions before 2.73.12, and several BC-FJA series versions before their respective fixed releases.
CVE-2026-12816 is a high-severity vulnerability in Legion of the Bouncy Castle Inc.'s BC-JAVA library affecting versions before 1.85 and LTS versions before 2.73.12. It involves improper validation of the integrity check value in the IESEngine stream-mode MAC, allowing MAC forgery via a length-dependent key derivation function split.
CVE-2026-12803 is a high-severity vulnerability in Legion of the Bouncy Castle Inc.'s BC-JAVA cryptographic library. It affects versions before 1.85 and LTS versions before 2.73.12. The issue arises because the KCCMBlockCipher MAC does not bind the nonce when Additional Authenticated Data (AAD) is absent, leading to a cross-nonce AEAD forgery vulnerability. This flaw allows attackers to potentially forge authenticated encryption data across different nonces.
CVE-2026-12802 is a high-severity vulnerability in Legion of the Bouncy Castle Inc.'s BC-JAVA library. It involves improper validation of the integrity check value in the CMS AuthEnvelopedData decryption process, specifically failing to enforce tag-length. This affects versions of Bouncy Castle for Java before 1.85 and certain LTS and FIPS versions prior to specified patch releases.
CVE-2026-58061 affects Bouncy Castle for Java (BC-JAVA) in versions prior to 1.85 and certain LTS and FIPS releases. The vulnerability involves CCM-family encryption modes writing plaintext to the caller's buffer before verifying the authentication tag, leading to improper validation of the integrity check value.
CVE-2026-59642 is a high-severity vulnerability in Bouncy Castle for Java (BC-JAVA) affecting versions before 1.85 and certain LTS and FIPS versions prior to specified patch releases. The issue involves improper validation of the integrity check value in CMS AuthenticatedData when authenticated attributes are present, meaning the content is not properly bound to the MAC. This could undermine the integrity guarantees of the cryptographic message syntax implementation.
In NLnet Labs Unbound up to and including version 1.25.1, when the validator builds the canonical RDATA form for an RRSIG-covered PX/RP/MINFO/SOA RRset, it computes the address of the second embedded domain name as 'datstart + dname_valid(datstart, ...)' and passes it straight to 'query_dname_tolower()' without checking that a second name is actually present in the RDATA. The wire-format parser accepts multi-dname RRs whose RDATA ends after the first name, so an attacker who runs a DNSSEC-signed authoritative server can deliver a record with an absent second domain name (e.g. SOA record) and cause 'query_dname_tolower()' to walk label-by-label through stale bytes in the per-worker 'env->scratch_buffer', past the end of that heap allocation if 'msg-buffer-size' has been lowered from the default. This leads to heap buffer overflow and on a release build the outcome relies heavily on the contents of the buffer tail and the adjacent heap chunk.
An Improper Validation of Integrity Check Value and Improper Certificate Validation in certain ASUS router models allows a remote man-in-the-middle(MITM) user to make the router download and execute arbitrary command via a spoofed server.
Refer to the '
Security Update for ASUS Router Firmware ' section on the ASUS Security Advisory for more information.
A denial-of-service security issue exists across all the 1756-EN2, EN3, and ENBT communication module due to improper validation of CIP Implicit Connection packets. An attacker on the network can exploit this by sending crafted packets to continuously disrupt device connections, though device connections will recover immediately after.
CVE-2026-50021 is a vulnerability in the pnpm package manager where integrity verification is skipped if the integrity field is missing from the lockfile resolution. This allows an attacker who can modify the pnpm-lock.yaml file and control the registry URL to cause pnpm to install altered packages without detecting integrity errors. The issue is fixed in pnpm versions 10.34.0 and 11.4.0.
Improper Validation of Integrity Check Value vulnerability in Apache APISIX.
The jwe-decrypt plugin under default configuration is vulnerable to authentication bypass.
This issue affects Apache APISIX: from 3.8.0 through 3.16.0.
Users are recommended to upgrade to version 3.17.0, which fixes the issue.
A security issue exists within 1769 CompactLogix controllers due to the missing validation of sequence numbers and source IP addresses in the CIP protocol. This allows attacker to abuse the exposed Connection ID’s visible on the web interface to perform denial-of-service attacks, resulting in a minor fault.
CVE-2026-8863 is a vulnerability in OracleLinux(7.2) shim version 0.9 involving improper verification of cryptographic signatures. This flaw allows an attacker with administrative privileges or the ability to modify the boot process to bypass Secure Boot protections by exploiting Microsoft-signed UEFI SHIM bootloaders. Successful exploitation could enable arbitrary code execution before the operating system loads. No official patch or remediation guidance is currently provided, but a specific UEFI DBX update is required to block the vulnerable boot loaders.
Missing integrity verification in the Triton inference handler in Amazon SageMaker Python SDK v2 before v2.257.2 and v3 before v3.8.0 might allow a remote authenticated actor to achieve code execution in inference containers via replacement of model artifacts in S3 with a specially crafted pickle payload that is deserialized without verification. This issue requires a remote authenticated actor with S3 write access to the model artifact path.
To remediate this issue, we recommend upgrading to Amazon SageMaker Python SDK v2.257.2 or v3.8.0 and rebuild any Triton models previously created with ModelBuilder using the updated SDK.
Insufficient Verification of Data Authenticity vulnerability in hexpm hex (Hex.RemoteConverger module) allows dependency integrity bypass via unverified lockfile checksums.
Hex stores checksums for dependencies in the mix.lock file to ensure reproducible and integrity-checked builds. However, Hex.RemoteConverger.verify_resolved/2 never executes checksum verification because the lock data returned by Hex.Utils.lock/1 uses string-based dependency names, while the verification logic compares against atom-based names. This type mismatch causes the verification code path to be silently skipped. Checksums are still validated when packages are initially downloaded from the registry, but mismatches between the lockfile and resolved dependencies are not detected.
An attacker who can influence cached packages (e.g., via local cache poisoning or a compromised registry) can provide modified dependency contents that will be accepted without detection. The mix.lock file is silently rewritten with the checksum values from the registry, erasing evidence of tampering.
This issue affects hex: from 0.16.0 before 2.4.2.
SP1 is a zero‑knowledge virtual machine that proves the correct execution of programs compiled for the RISC-V architecture. In versions 6.0.0 through 6.0.2, a soundness vulnerability in the SP1 V6 recursive shard verifier allows a malicious prover to construct a recursive proof from a shard proof that the native verifier would reject. Version 6.1.0 fixes the issue.
xrdp is an open source RDP server. In versions through 0.10.5, xrdp does not implement verification for the Message Authentication Code (MAC) signature of encrypted RDP packets when using the "Classic RDP Security" layer. While the sender correctly generates signatures, the receiving logic lacks the necessary implementation to validate the 8-byte integrity signature, causing it to be silently ignored. An unauthenticated attacker with man-in-the-middle (MITM) capabilities can exploit this missing check to modify encrypted traffic in transit without detection. It does not affect connections where the TLS security layer is enforced. This issue has been fixed in version 0.10.6. If users are unable to immediately upgrade, they should configure xrdp.ini to enforce TLS security (security_layer=tls) to ensure end-to-end integrity.
CVE-2026-5479 is a high-severity vulnerability in wolfSSL's EVP layer affecting the ChaCha20-Poly1305 AEAD decryption implementation. The flaw causes the decryption function to fail to verify the authentication tag before returning plaintext, potentially allowing unauthenticated ciphertext to be accepted as valid. This improper validation of the integrity check value (CWE-354) undermines the security guarantees of the AEAD cipher.
CVE-2026-26928 is a high-severity vulnerability in Krajowa Izba Rozliczeniowa's SzafirHost software. The issue arises because SzafirHost does not verify the hash or the vendor's digital signature of uploaded DLL, SO, JNILIB, or DYLIB files, allowing an attacker to supply a malicious file that is saved in the user's temporary folder and executed by the application. JAR files are properly verified, but this gap in validation for other file types creates a risk of arbitrary code execution. This vulnerability was fixed in SzafirHost version 1.1.0.
CVE-2026-33026 is a critical vulnerability in the 0xJacky nginx-ui web user interface for the Nginx web server. Versions prior to 2.3.4 have a flaw in the backup restore mechanism that allows attackers to tamper with encrypted backup archives and inject malicious configuration during restoration. This issue involves cleartext storage of sensitive information and improper validation of backup archives. The vulnerability has been patched in version 2.3.4. The CVSS 4.0 score is 9.4, indicating a critical severity level.