Improper Validation of Integrity Check Value Affecting arangodb-3.11 package, versions <3.11.14.6-r4
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CHAINGUARDLATEST-ARANGODB311-22107137
- published31 Oct 2026
- disclosed29 Oct 2026
Introduced: 29 Oct 2026
NewCVE-2026-119186 (opens in a new tab)How to fix?
Upgrade Chainguard arangodb-3.11 to version 3.11.14.6-r4 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream arangodb-3.11 package and not the arangodb-3.11 package as distributed by Chainguard.
See How to fix? for Chainguard relevant fixed versions and status.
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.