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 VendorProductAffected 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.
Fix within
Internet-facing 14 days
Internal 60 days
  • Not known to be exploited
  • Can be exploited automatically (estimated)
  • Gives an attacker partial control (estimated)
Severity
3.7 Low
Timeline
Published14 Nov 2026
Updated16 Nov 2026
First seen16 Nov 2026
Sources
Track software like this
Free during beta