i18next-fs-backend: Path traversal via unsanitised lng/ns allows arbitrary file read/overwrite

Summary Versions of i18next-fs-backend prior to 2.6.4 interpolate the caller-supplied lng and ns values directly into the configured loadPath and addPath templates with no path-component validation and no sanitisation. When an application exposes the resolved language code to user-controlled inpu...

GHSA-8847-338W-5HCJ i18next-fs-backend: Path traversal via unsanitised lng/ns allows arbitrary file read/overwrite

Summary Versions of i18next-fs-backend prior to 2.6.4 interpolate the caller-supplied lng and ns values directly into the configured loadPath and addPath templates with no path-component validation and no sanitisation. When an application exposes the resolved language code to user-controlled inpu...

External Control of File Name or Path

Overview i18next-fs-backend is an i18next-fs-backend is a backend layer for i18next using in Node.js and for Deno to load translations from the filesystem. Affected versions of this package are vulnerable to External Control of File Name or Path that leads to raw interpolation of lng and ns value...

@diia-inhouse/i18n (>=2.8.2, <=2.8.14), @genie23/electron-base (>=0.0.4-alpha, <=0.0.225) +56 more potentially affected by CVE-2026-41693 via i18next-fs-backend (>=2.0.0, <=2.6.3)

i18next-fs-backend NPM version =2.0.0, =2.8.2, =0.0.4-alpha, =3.0.0-rc.0, =7.1.2, =2.4.2, =1.1.8, =1.1.8, =2.4.2, =2.4.2, =2.6.9, =2.4.2, =2.4.2, =2.4.2, =2.4.2, =2.5.5 and more Source cves: CVE-2026-41693 Source advisory: OSV:GHSA-8847-338W-5HCJ...

@diia-inhouse/i18n (>=2.8.2, <=2.8.14), @genie23/electron-base (>=0.0.4-alpha, <=0.0.225) +56 more potentially affected by CVE-2026-41693 via i18next-fs-backend (>=2.0.0, <=2.6.3)

i18next-fs-backend NPM version =2.0.0, =2.8.2, =0.0.4-alpha, =3.0.0-rc.0, =7.1.2, =2.4.2, =1.1.8, =1.1.8, =2.4.2, =2.4.2, =2.6.9, =2.4.2, =2.4.2, =2.4.2, =2.4.2, =2.5.5 and more Source cves: CVE-2026-41693 Source advisory: SNYK:JS-I18NEXTFSBACKEND-16415529...

PT-2026-36656

Summary Versions of i18next-fs-backend prior to 2.6.4 interpolate the caller-supplied lng and ns values directly into the configured loadPath and addPath templates with no path-component validation and no sanitisation. When an application exposes the resolved language code to user-controlled inpu...

PT-2026-37153

Name of the Vulnerable Software and Affected Versions i18next-fs-backend versions prior to 2.6.4 Description i18next-fs-backend substitutes the lng and ns options directly into the configured loadPath and addPath templates to read or write files from the disk. Because this interpolation is...

The vulnerability of the Container Isolation FS Filter driver for Windows operating systems, which allows attackers to exploit their privileges.

The vulnerability of the Container Isolation FS Filter driver for Windows operating systems relates to the possibility of exploiting memory after it is freed. Exploiting this vulnerability could allow an attacker to gain increased privileges...

CVE-2026-33098 Windows Container Isolation FS Filter Driver Elevation of Privilege Vulnerability

...

CVE-2026-33098

CVE-2026-33098 affects Windows container isolation via the FS Filter Driver causing Elevation of Privilege. The advisory indicates a LOCAL attack vector with LOW attack complexity and LOW privileges required, no user interaction, and HIGH impact to confidentiality, integrity, and availability. Th...

PT-2026-32872

Name of the Vulnerable Software and Affected Versions Windows Container Isolation FS Filter Driver affected versions not specified Description A use after free issue in the Windows Container Isolation FS Filter Driver allows an authorized attacker to elevate privileges locally. Use after free is ...

CVE-2026-33098: Use After Free

Use after free in Windows Container Isolation FS Filter Driver allows an authorized attacker to elevate privileges locally...

ROS-20260408-73-0031

A vulnerability in the fs/nfs component of the Linux kernel is related to incorrect privilege assignment. Exploitation of the vulnerability allows an attacker to gain access to sensitive data, compromise its integrity, and cause a denial-of-service condition...

CVE-2026-39364

The frontend tooling framework Vite is vulnerable to an access control bypass in the development server. Specifically, files intended to be blocked by the server.fs.deny configuration (such as .env or *.crt) can be retrieved with HTTP 200 responses. This occurs when an unauthenticated attacker ap...

ROS-20260407-73-0034

A vulnerability in the fs/buffer.c component of the Linux operating system kernel is related to the use of memory after it has been freed. Exploitation of the vulnerability allows an intruder to affect the integrity and availability of protected information...

SUSE CVE-2026-31410

In the Linux kernel, the following vulnerability has been resolved: ksmbd: use volume UUID in FSOBJECTIDINFORMATION Use sb-suuid for a proper volume identifier as the primary choice. For filesystems that do not provide a UUID, fall back to stfs.ffsid obtained from vfsstatfs...

CVE-2026-5573

A weakness has been identified in Technostrobe HI-LED-WR120-G2 5.5.0.1R6.03.30. This impacts an unknown function of the file /fs. Executing a manipulation of the argument cwd can lead to unrestricted upload. The attack can be launched remotely. The exploit has been made available to the public an...

CVE-2026-34783

CVE-2026-34783 is a path traversal in Ferret’s IO::FS::WRITE (and related IO::FS::READ) that lets an attacker cause arbitrary file writes during web scraping by supplying filenames containing ".." sequences. A malicious website can manipulate output paths so the attacker controls destination and ...

EUVD-2026-19353

Ferret is a declarative system for working with web data. Prior to 2.0.0-alpha.4, a path traversal vulnerability in Ferret's IO::FS::WRITE standard library function allows a malicious website to write arbitrary files to the filesystem of the machine running Ferret. When an operator scrapes a...

EUVD-2026-19194

In the Linux kernel, the following vulnerability has been resolved: ksmbd: use volume UUID in FSOBJECTIDINFORMATION Use sb-suuid for a proper volume identifier as the primary choice. For filesystems that do not provide a UUID, fall back to stfs.ffsid obtained from vfsstatfs...