i18next i18next-http-backend up to 4.0.1 Backend loadPath/addPath server-side request forgery

Summaryinfo

A vulnerability classified as problematic was found in i18next i18next-http-backend up to 4.0.1. Affected by this issue is some unknown functionality of the component Backend. Executing a manipulation of the argument loadPath/addPath can lead to server-side request forgery. This vulnerability is handled as CVE-2026-105800. The attack can be executed remotely. There is not any exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability classified as problematic was found in i18next i18next-http-backend up to 4.0.1. This vulnerability affects an unknown function of the component Backend. The manipulation of the argument loadPath/addPath with an unknown input leads to a server-side request forgery vulnerability. The CWE definition for the vulnerability is CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. As an impact it is known to affect confidentiality. CVE summarizes:

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.

The advisory is shared for download at github.com. This vulnerability was named CVE-2026-105800 since 10/05/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available.

Upgrading to version 4.0.2 eliminates this vulnerability.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• i18next

Name

• i18next-http-backend

Version

• 4.0.0
• 4.0.1

Website

• Product: https://github.com/i18next/i18next-http-backend/

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion