CVE-2026-105800
Description
A flaw was found in i18next-http-backend. A remote attacker can supply crafted language or namespace values to applications configured with custom translation path templates that begin directly with placeholders. This manipulation causes the application to generate unintended external web addresses, potentially leading to Server-Side Request Forgery (SSRF, where the server is coerced into making unauthorized network requests) or redirecting browser requests to external destinations.
Statement
A low impact server-side request forgery (SSRF)/URL injection flaw was found in the i18next-http-backend npm package, which Red Hat ships as a bundled dependency in container images across a broad set of products, including Red Hat OpenShift Container Platform, OpenShift Service Mesh, Red Hat Ansible Automation Platform, Red Hat Advanced Cluster Management for Kubernetes, Multicluster Engine for Kubernetes, Cluster Observability Operator, Network Observability Operator, Red Hat AMQ, JBoss Data Grid, Migration Toolkit for Applications, and Red Hat Edge Manager. A remote, unauthenticated attacker can supply crafted language or namespace values that are interpolated into a custom translation path template (loadPath or addPath) that begins directly with the {{lng}} or {{ns}} placeholder. Such input can form an absolute or protocol-relative URL, causing the application to issue requests outside the intended origin, with potential low confidentiality impact (CVSS 3.7, AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N). Exploitation requires a non-default configuration: the default /locales/{{lng}}/{{ns}}.json template and templates that begin with a leading path or origin are not affected, because the attacker-controlled value does not occupy the URL's structural beginning. The Red Hat severity matches the upstream assessment. Because the impact is low, Red Hat has deferred the fix for affected in-support streams and no update is currently planned for them; the residual risk is limited to possible low-severity information exposure through unintended outbound requests from applications configured with vulnerable custom path templates. Product versions whose streams are out of support scope are not scheduled to receive a fix.
Mitigation
Applications can avoid this issue by configuring the i18next-http-backend loadPath and addPath templates so that they do not begin directly with the {{lng}} or {{ns}} placeholder: use the default /locales/{{lng}}/{{ns}}.json template, or prefix the placeholder with a leading path segment or explicit origin, so that attacker-controlled language or namespace values cannot form an absolute or protocol-relative URL. Restricting or validating accepted language and namespace values to the expected formats further reduces exposure. Updating to the upstream i18next-http-backend 4.0.2 release or later also resolves the issue.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 3.7 | N/A | 3.7 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | High | N/A | High |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | Low | N/A | Low |
| Integrity Impact | None | N/A | None |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
cve.org: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Application Data
Integrity
Technical Impact: Execute Unauthorized Code or Commands
Access Control
Technical Impact: Bypass Protection Mechanism
By providing URLs to unexpected hosts or ports, attackers can make it appear that the server is sending the request, possibly bypassing access controls such as firewalls that prevent the attackers from accessing the URLs directly. The server can be used as a proxy to conduct port scanning of hosts in internal networks, use other URLs such as that can access documents on the system (using file://), or use other protocols such as gopher:// or tftp://, which may provide greater control over the contents of requests.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
