Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
3.7
Docker hardened images with ArangoDB allow prototype manipulation
published 8 days ago
Summary
The ArangoDB Docker images that include the Joi library (versions 16.0.0‑17.13.4 and 18.0.0‑18.2.3) can be tricked into altering the internal prototype of objects created during data validation. An attacker can send a specially crafted key that changes how the object is built, potentially leading to unexpected behavior in the application. Updating the images to include Joi 17.13.5 or later (or 18.2.4 or later) resolves the issue; apply the latest Docker image or upgrade the Joi package in your code.
What to do
The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| Docker Hardened Images:Debian:13 | docker hardened images | arangodb | All versions |
Original advisory text
joi is a schema description language and data validator for JavaScript. From 16.0.0 until 17.13.5 and 18.2.4, joi's…
joi is a schema description language and data validator for JavaScript. From 16.0.0 until 17.13.5 and 18.2.4, joi's lib/types/keys.js internals.rename() implementation used by object().rename() permits a schema that renames keys with a regular-expression source and a Joi.expression() or Joi.x() target that interpolates the pattern's own match data, combined with { multiple: true }, to derive a target from an attacker-controlled input key. An attacker can send x-__proto__ with an object value, causing the target to render as __proto__ and set the prototype of the object returned by validate() instead of creating an own key. The global Object.prototype is not modified, so the effect is confined to the object returned by that validation call. Static-string targets and schemas using the default { multiple: false } are not affected. This issue is fixed in versions 17.13.5 and 18.2.4.
References
- https://scout.docker.com/v/DHI-jtmh-mjnd-e54g-apsc Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-84367 Vendor Advisory
- https://github.com/advisories/GHSA-gg4h-3hg2-grpc Vendor Advisory
- https://github.com/hapijs/joi/security/advisories/GHSA-gg4h-3hg2-grpc Vendor Advisory
- https://github.com/hapijs/joi/pull/3135 Patch
- https://github.com/hapijs/joi/pull/3134 Patch
- https://github.com/hapijs/joi/commit/172ececa192feda532b743d77bc9d3e523d19b01 Patch
- https://github.com/hapijs/joi/commit/162f367aa178d2e1ebec8dc1164e5fe16536ddf6 Patch
- https://github.com/hapijs/joi/releases/tag/v18.2.4 URL
- https://github.com/hapijs/joi/releases/tag/v17.13.5 URL
Internet-facing
14 days
Internal
60 days
- Not known to be exploited
- Can be exploited automatically (estimated)
- Gives an attacker partial control (estimated)
Timeline
Published14 Nov 2026
Updated16 Nov 2026
First seen16 Nov 2026
Sources
DHI-jtmh-mjnd-e54g-apsc · OSV
Track software like this
Free during beta