Forge: Incomplete PKCS#7 padding validation in AES/DES CBC and ECB decryption
Impact
Forge, a JavaScript TLS implementation, has a vulnerability in versions prior to 1.4.1, where incomplete PKCS#7 padding validation in AES/DES CBC and ECB decryption can lead to integrity failures. The issue arises from accepting malformed ciphertext with invalid padding. This can cause up to four plaintext blocks to be silently removed.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
digitalbazaar · GitHub_M
forge
1 range
digitalbazaar · GitHub_M
forge
Compare with this publisher’s ranges. This does not inspect your installation.
affected
< 1.4.1
Other versions: unknown
Original source description
Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used decipher.finish(), CBC and ECB modes, PKCS#7 padding to process the relevant input or security decision. node-forge validated only the final byte of PKCS#7 padding during CBC and ECB decryption and accepted zero, oversized, or mismatched padding bytes. Malformed ciphertext could consequently be accepted and up to four plaintext blocks could be silently removed, causing an integrity failure in applications that treated successful decryption as proof of valid padding. This issue is fixed in version 1.4.1.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-118776View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 1
Assigning organization
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.