Server-side Request Forgery (SSRF) Affecting org.webjars.npm:i18next-http-backend package, versions [,4.0.2)


Severity

Recommended
0.0
medium
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

Exploit Maturity
Proof of Concept
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-JAVA-ORGWEBJARSNPM-20580645
  • published13 Oct 2026
  • disclosed6 Oct 2026
  • creditUnknown

Introduced: 6 Oct 2026

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

How to fix?

Upgrade org.webjars.npm:i18next-http-backend to version 4.0.2 or higher.

Overview

org.webjars.npm:i18next-http-backend is an i18next-http-backend is a backend layer for i18next using in Node.js, in the browser and for Deno.

Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via insufficient validation in isSafeUrlSegment functions in lib/utils.js, where user-controlled lng or ns values are interpolated into loadPath/addPath URL templates without rejecting scheme-bearing strings. When a template begins directly with a placeholder (e.g. {{lng}}/{{ns}}.json with no leading origin or path), an attacker can supply a lng value such as http:127.0.0.1:8080 to cause the HTTP backend to issue a request to an arbitrary absolute URL, or an ns value of //evil.example/x to produce a protocol-relative URL in browsers, redirecting requests outside the intended origin.

Note: This is only exploitable when the loadPath or addPath template begins directly with a placeholder, with no leading origin or path segment. The default /locales/{{lng}}/{{ns}}.json template and any template with a leading path or origin are not affected.

CVSS Base Scores

version 4.0
version 3.1