PULSE
FEED
ransomshiba reclama a IT Foods Industries · Agriculture and Food Productionransomshiba reclama a Friendly Senior Living · Healthcareransomshiba reclama a Morgan White Group · Professional Servicesransomshiba reclama a Antwerp House Dentistry · GB · Healthcareransomeverstake reclama a as*****g.comransomeverstake reclama a ca*****s.comransomeverstake reclama a in*****s.comransomeverstake reclama a corp-smart.com · Technologyransomwhitearmor reclama a rolly.io · Technologyransomemperador reclama a LA PROFUMERIA SRL · IT · Retail & E-Commerceransomscarlettgroup reclama a sunnybrook.ca · CA · Healthcareransomscarlettgroup reclama a au.bank.in · IN · Financial Servicesransomqilin reclama a Udima · ES · Educationransomqilin reclama a W Interactive · GB · Technologyransomshiba reclama a IT Foods Industries · Agriculture and Food Productionransomshiba reclama a Friendly Senior Living · Healthcareransomshiba reclama a Morgan White Group · Professional Servicesransomshiba reclama a Antwerp House Dentistry · GB · Healthcareransomeverstake reclama a as*****g.comransomeverstake reclama a ca*****s.comransomeverstake reclama a in*****s.comransomeverstake reclama a corp-smart.com · Technologyransomwhitearmor reclama a rolly.io · Technologyransomemperador reclama a LA PROFUMERIA SRL · IT · Retail & E-Commerceransomscarlettgroup reclama a sunnybrook.ca · CA · Healthcareransomscarlettgroup reclama a au.bank.in · IN · Financial Servicesransomqilin reclama a Udima · ES · Educationransomqilin reclama a W Interactive · GB · Technology
← Todos los CVEs
CVE Watch29 oct 2026

CVE-2026-118776

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementa

CVSS

3.7

Bajo

EPSS

—

KEV

—

Exploit Today

—

0-100

Publicado: 29 oct 2026 · Última mod.: 29 oct 2026 · CWE-20 · CWE-354

EPSS · 30d

Sin historial EPSS suficiente todavía.

Descripción técnica

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.

Referencias oficiales
CVEs relacionados
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2026-1192803.7 BAJ
—
———MariaDB Connector/J is used to connect applications developed in Java to MariaDB and MySQL databases. From 3.0.0 until 3.3.7, 3.4.5, and 3.5.11, the MariaDbPoolConnection.recover() and MariaDbPoolPinnedConnection.recover() implementations trusted the gtrid_length and bqual_length columns returned by XA RECOVER. The methods allocated and split Xid byte arrays without validating the lengths against Xid.MAXGTRIDSIZE, Xid.MAXBQUALSIZE, or the actual data payload. A malicious or compromised server, or a machine-in-the-middle attacker, could cause large allocations, NegativeArraySizeException, or ArrayIndexOutOfBoundsException during XA recovery. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.11.4h
CVE-2026-1192105.9 MED
—
———MariaDB Connector/J is used to connect applications developed in Java to MariaDB and MySQL databases. From 3.0.0 until 3.3.7, 3.4.5, and 3.5.11, the ClientMessage.validateLocalFileName() check used a regular expression that could match LOAD DATA LOCAL INFILE text inside quoted identifiers, string literals, or comments instead of requiring a real statement. A malicious or compromised server, or a machine-in-the-middle attacker, could return crafted database or table identifiers that the connector reused in metadata or updatable-result queries, then answer with a LOCAL INFILE request for a client file. With allowLocalInfile enabled, this caused the connector to stream any readable client-host file named by the crafted text, including through DatabaseMetaData.getImportedKeys(), DatabaseMetaData.getExportedKeys(), or ResultSet.updateRow() paths. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.11.4h
CVE-2026-1191865.9 MED
—
———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.4h
CVE-2026-1187827.5 ALT
—
———Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, node-forge accepted a PKCS#12 MAC or PKCS#12 password-based encryption iteration count of zero or less. pki.pbe.generatePkcs12Key() then returned a constant key independent of the password and salt, allowing crafted PKCS#12 input processed by forge.pkcs12.pkcs12FromAsn1() to bypass password-based integrity checks. Predictable encryption keys and IVs also affected PKCS#12 PBE using pbeWithSHAAnd3-KeyTripleDES-CBC or pbewithSHAAnd40BitRC2-CBC, including shrouded key bags, encrypted SafeContents, and PKCS#8 ENCRYPTED PRIVATE KEY input processed independently by forge.pki.decryptPrivateKeyInfo(). PBES2/PBKDF2-encrypted content is unaffected. This issue is fixed in version 1.4.1.6h
CVE-2026-908697.5 ALT
—
———A remote attacker who knows a valid account's enrolled SSH public key can terminate the shared SSH service in Progress Software WS_FTP Server versions prior to 2024.0.7 and 2025.0.4 on Windows.9h
CVE-2026-1191302.6 BAJ
—
———Wasmtime before 36.0.18, 37.0.0 before 48.0.6, and 49.0.0 before 49.0.3 does not verify that set-path-with-query values in wasmtime-wasi-http are paths, so absolute-form URLs are written verbatim as the HTTP/1.1 request target while the connection uses the allowed authority. A malicious guest can supply an absolute URL that a forward proxy or gateway at that authority honors, reaching hosts disallowed by embedder filtering policies.4h