AZL-112475: CVE-2026-119186 affecting package python-tensorboard 2.16.2-6

Q: Which applications are exposed to unauthenticated ciphertext acceptance?

Applications using node-forge AES-GCM decryption through forge.cipher.createDecipher() are exposed if tagLength is derived from received data or is unset or configured with a zero-like value that converts to zero, and the authentication tag is empty or missing. Applications that omit tagLength specifically to use the 128-bit default, or that supply a fixed valid tag length, are unaffected.

Q: What must an attacker control for exploitation?

An attacker must be able to provide ciphertext along with conditions that result in a zero-converting tagLength and an empty or missing authentication tag. Under those conditions, decipher.finish() can accept ciphertext without authentication.

Q: What mitigation is available if an update cannot be applied immediately?

Ensure AES-GCM decryption uses a fixed, valid tagLength and reject empty or missing authentication tags. Do not derive tagLength from received data or allow it to resolve to a zero-like value.

Q: How can I determine whether my use is affected?

Review calls to forge.cipher.createDecipher() and the subsequent start() invocation for AES-GCM decryption. The vulnerable pattern uses tagLength derived from input or an unset or zero-like value; node-forge version 1.4.1 contains the fix.

Published Oct 29, 2026

Updated

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.

Affected Software

1 affected component

azure-linux/python-tensorboard<=2.16.2-6

Event History

Oct 29, 2026

Advisory Published

via OSV·08:17 PM

Data Sourced

via OSV·08:17 PM

DescriptionAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

CVE-2026-119186

Frequently Asked Questions

Which applications are exposed to unauthenticated ciphertext acceptance?

Applications using node-forge AES-GCM decryption through forge.cipher.createDecipher() are exposed if tagLength is derived from received data or is unset or configured with a zero-like value that converts to zero, and the authentication tag is empty or missing. Applications that omit tagLength specifically to use the 128-bit default, or that supply a fixed valid tag length, are unaffected.

What must an attacker control for exploitation?

An attacker must be able to provide ciphertext along with conditions that result in a zero-converting tagLength and an empty or missing authentication tag. Under those conditions, decipher.finish() can accept ciphertext without authentication.

What mitigation is available if an update cannot be applied immediately?

Ensure AES-GCM decryption uses a fixed, valid tagLength and reject empty or missing authentication tags. Do not derive tagLength from received data or allow it to resolve to a zero-like value.

How can I determine whether my use is affected?

Review calls to forge.cipher.createDecipher() and the subsequent start() invocation for AES-GCM decryption. The vulnerable pattern uses tagLength derived from input or an unset or zero-like value; node-forge version 1.4.1 contains the fix.

AZL-112475: CVE-2026-119186 affecting package python-tensorboard 2.16.2-6

Affected Software

Event History

Child vulnerabilities

Frequently Asked Questions

Which applications are exposed to unauthenticated ciphertext acceptance?

What must an attacker control for exploitation?

What mitigation is available if an update cannot be applied immediately?

How can I determine whether my use is affected?

Company

Resources

Contact

Frequently Asked Questions

Which applications are exposed to unauthenticated ciphertext acceptance?

What must an attacker control for exploitation?

What mitigation is available if an update cannot be applied immediately?

How can I determine whether my use is affected?