CVE-2026-85632 is a critical vulnerability in the WooCommerce Virtual POS Module by Sipay Electronic Money and Payment Services Inc. It involves missing authentication for critical functions and improper validation of integrity check values, enabling authentication bypass and manipulation of application API messages via man-in-the-middle attacks. The issue affects versions from 26.8.3 up to but not including 26.9.1 and is fixed in version 26.9.1.
JetBrains Ktor versions before 3.6.1 contain a vulnerability that allows session forgery via tampered encrypted session cookies due to improper validation of integrity check values. This flaw was fixed in version 3.6.1.
undici, an HTTP client for Node.js, has a vulnerability in versions 7.15.0 through 7.30.1 and 8.0.0 through 8.12.3 where Subresource Integrity (SRI) metadata is improperly validated. The client incorrectly splits the integrity string only on spaces, ignoring other ASCII whitespace like tabs. This causes integrity values with whitespace to be skipped, allowing attacker-controlled responses to bypass integrity checks. The issue is fixed in versions 7.30.2 and 8.12.4.
bitcoinjs-lib versions from 2.3.0 up to but not including 5.2.1, from 6.0.0 up to 6.1.8, and from 7.0.0-rc.0 up to 7.0.2 contain a vulnerability in their Merkle root validation logic. The library's fastMerkleRoot function pads odd Merkle-tree levels by hashing the final node with itself but fails to detect adjacent duplicate hashes. This allows a peer to append duplicate transactions without changing the Merkle root or block identifiers, potentially causing consumers relying on block-root validation to process duplicated transactions or reject valid blocks. The issue is fixed in versions 5.2.1, 6.1.8, and 7.0.2.
Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, node-forge did not validate the AES-GCM tagLength option passed to start() during decryption through forge.cipher.createDecipher(). When an application derived tagLength from received data or used an unset or zero-like configuration value, a value that converted to zero together with an empty or missing authentication tag caused the calculated and supplied tags to compare as empty, so decipher.finish() accepted unauthenticated ciphertext. Applications that omit tagLength to use the 128-bit default or pass a fixed valid tag length are unaffected. This issue is fixed in version 1.4.1.
A vulnerability in digitalbazaar forge versions prior to 1.4.1 allows bypassing password-based integrity checks in PKCS#12 processing due to acceptance of zero or negative iteration counts. This leads to predictable encryption keys and IVs in certain password-based encryption schemes, compromising integrity verification. The issue is fixed in version 1.4.1.
A vulnerability in digitalbazaar's forge library (prior to version 1.4.1) involves improper input validation of PKCS#7 padding during CBC and ECB mode decryption. The library only validated the final padding byte and accepted zero, oversized, or mismatched padding bytes, which could allow malformed ciphertext to be accepted and cause silent removal of up to four plaintext blocks. This leads to an integrity failure in applications that rely on successful decryption as proof of valid padding. The issue is fixed in version 1.4.1.
Dell PowerProtect Data Domain versions 7.7.1.0 through 8.8 and several LTS releases contain a vulnerability involving improper validation of integrity check values. This flaw could allow a high privileged local attacker to bypass protection mechanisms. The vulnerability is tracked as CVE-2026-90720 with a CVSS score of 6.7, indicating a medium severity impact. Fixed versions are available starting from 8.9.0.0 and corresponding LTS patch levels.
CVE-2026-65625 is a vulnerability in the potatosalad jose library affecting versions from 1.2.0 up to but not including 1.11.13. The issue arises in the pure-Erlang AES-GCM fallback implementation where the authentication tag length is derived from attacker-supplied data without proper validation. This allows an attacker controlling a JWE token to truncate the authentication tag to as little as 8 bits, drastically reducing forgery resistance and enabling reliable forgery within 256 attempts. Supplying an overly long tag causes a crash. The vulnerability is fixed in version 1.11.13.
A vulnerability in the zip-rs zip2 library versions from 0.6.0 up to but not including 9.0.0 allows improper validation of the AES entry reader's HMAC authentication tag. Under certain conditions, such as when the encrypted entry has no payload or the underlying reader reaches the end of the archive prematurely, the library may accept modified plaintext without triggering an authentication error. This flaw is fixed in version 9.0.0.
CVE-2026-89320 is a vulnerability in Eclipse KeyPont - GOSE where the HmacShaCryptor.Hash function does not hash its input and always returns the MAC of an empty message under the key. This causes the authentication tag in AES-CBC-HMAC JWE tokens to be constant per key and independent of the message, effectively removing ciphertext integrity.
CVE-2026-35501 is a vulnerability in NLnet Labs Unbound DNS resolver versions 1.0.1 through 1.26.1. It occurs when Unbound is configured with both a root trust anchor and an additional trust-anchor for an island-of-security zone whose parent is insecure. A malicious actor can exploit this by sending a forged NSEC reply with the SOA bit cleared, causing Unbound to incorrectly treat the trust island as insecure. This happens because the DNSSEC validator accepts and caches the NSEC insecure response without proper RRSIG validation. The issue stems from an old fix related to DS and NSEC queries when a trust anchor exists for that name. The vulnerability has a low CVSS score of 3.7 and was fixed in version 1.26.2.
CVE-2026-113714 is a low-severity vulnerability in pypa virtualenv prior to version 21.14.9. It involves improper validation of integrity check values during package wheel downloads, allowing a controlled package index to inject misleading verification data. This can cause the system to cache and later select unverified or rejected archives, potentially undermining package integrity verification. The issue is fixed in version 21.14.9.
CVE-2026-85243 is a vulnerability in Apache Camel's Crypto PGP component affecting versions from 4.0.0 before 4.18.5 and from 4.19.0 before 4.22.1. The issue arises because the unmarshal() function only verifies the modification detection code for OpenPGP symmetrically encrypted integrity protected data packets, but older packet types lack this integrity check. This allows an attacker who can modify messages in transit to bypass integrity validation. Apache Camel 4.23.0, 4.18.5, and 4.22.1 include fixes that add a requireIntegrityProtection option to enforce integrity checks on incoming messages.
CVE-2026-105280 is an improper validation of integrity check value vulnerability in the hex package manager (hexpm hex). It allows a malicious package mirror to substitute the tarball output by the command 'mix hex.package fetch PACKAGE VERSION --output -' to standard output without verifying its checksum. This occurs because the standard output branch bypasses the checksum comparison that normally protects file writes or unpacking. Additionally, error responses from mirrors containing tar archives can be written to standard output before verification, potentially causing untrusted files to be extracted. This affects hex versions from 0.20.2 up to but not including 2.5.2. The issue is fixed in version 2.5.2.
CVE-2026-94447 is a high-severity vulnerability in the Go toolchain's cmd/go component involving improper validation of integrity check values. A user working within a malicious Go project that defines a bogus golang.org/toolchain go.sum entry and uses a malicious GOMODPROXY can bypass the intended checksum verification. The issue is addressed by ensuring that golang.org/toolchain always fetches the canonical checksum from the network.
CVE-2026-94444 is a high-severity vulnerability in the Go toolchain's cmd/go module related to improper validation of integrity check values. It allows a user working inside a malicious Go project that defines a fake golang.org/fips140 module and connects to a malicious GOMODPROXY to have an arbitrary module served in place of the legitimate one. The issue is addressed by unpacking and verifying the trusted ziphash for the bundled golang.org/fips140 module to ensure its integrity.
CVE-2026-106434 is a medium severity vulnerability in MongoDB libmongocrypt versions 1.5.0 up to but not including 1.20.5. The flaw involves improper validation of the integrity check value during explicit decryption, allowing unrecognized encrypted payloads to be returned unchanged instead of triggering a decryption error. This could lead to applications treating manipulated ciphertext as decrypted plaintext.
Previous versions of HP ThinPro (prior to HP ThinPro 8.1 SP10) could potentially contain security vulnerabilities. HP has released HP ThinPro 8.1 SP10, which includes updates to mitigate potential vulnerabilities.
Previous versions of HP ThinPro (prior to HP ThinPro 9 SP3) could potentially contain security vulnerabilities. HP has released HP ThinPro 9 SP3, which includes updates to mitigate potential vulnerabilities.
CVE-2026-93317 is a medium severity vulnerability in moby BuildKit where an unauthenticated attacker controlling a registry or OCI-layout blob source can supply blob contents that do not match the claimed digest. This can cause the snapshot to be cached incorrectly and reused in subsequent builds, compromising the integrity of build inputs. The affected versions are from 0.28.0 up to but not including 0.33.1.