Arbitrary Code Injection Affecting node-i18next-http-backend package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.29% (20th percentile)

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-ECHOLATEST-NODEI18NEXTHTTPBACKEND-20557245
  • published7 Oct 2026
  • disclosed6 Oct 2026

Introduced: 6 Oct 2026

NewCVE-2026-105800  (opens in a new tab)
CWE-74  (opens in a new tab)
CWE-918  (opens in a new tab)

How to fix?

There is no fixed version for Echo:latest node-i18next-http-backend.

NVD Description

Note: Versions mentioned in the description apply only to the upstream node-i18next-http-backend package and not the node-i18next-http-backend package as distributed by Echo. See How to fix? for Echo:latest relevant fixed versions and status.

i18next-http-backend is a backend layer for i18next that loads translation resources in Node.js, browsers, and Deno. Prior to 4.0.2, attacker-controlled language or namespace values interpolated into a custom loadPath or addPath that begins directly with {{lng}} or {{ns}} can make colon-based input become an absolute URL or, in browsers, make a double-slash namespace become a protocol-relative URL. The resulting request can leave the intended origin and cause URL injection or server-side request forgery. The default /locales/{{lng}}/{{ns}}.json template and templates with a leading path or origin are not affected because the placeholder does not occupy the URL's structural beginning. This issue is fixed in version 4.0.2.

CVSS Base Scores

version 3.1