Vulnerability feed

CVE and vendor PSIRT advisories from 13 sources, last 30 days. Updated hourly, last run Oct 26 07:05 UTC

Critical in the last 24 hours

1602 in 30 days

Newly known exploited

In the last 24 hours, CISA KEV and vendor reports

Sources checked

Every hour, see the list

New in the last 24 hours

164-72% vs 7-day avg of 596

3 critical, 57 high, 70 medium, 29 low

Expand	Severity	Score	Advisory	Title	Source	Published
	Low	2.3	CVE-2026-115730	i18next-http-backend 4.0.2 contains an incomplete fix in interpolateUrl() that allows attackers to redirect translation requests by supplying an ns value starting with a slash i18nexti18next-http-backend	NVD	Oct 23 13:17 UTC
CVE-2026-115730i18next-http-backend 4.0.2 contains an incomplete fix in interpolateUrl() that allows attackers to redirect translation requests by supplying an ns value starting with a slash Executive summary The i18next-http-backend library version 4.0.2 has an incomplete fix for a flaw that lets attackers redirect translation requests to another website by supplying a namespace value that starts with a slash. The advisory does not state a severity rating. The vendor's recommendation is to upgrade to version 4.0.3, which adds a whole-URL check. Technical summary The flaw is an incomplete fix in the interpolateUrl() function, which builds translation request URLs from templates. When a template places {{ns}} directly after a leading slash, such as /{{ns}}/{{lng}}.json, a namespace value of /evil.example produces a protocol-relative URL (//evil.example/en.json) that browsers send to another origin. The 4.0.2 check only inspected the value and missed this case. The fix in 4.0.3 checks the interpolated URL as a whole and refuses URLs starting with // or backslash variants unless the template does the same, and the advisory references GHSA-9jhj-wvmw-cfx5. The advisory does not state a CVSS score, exploitation status, or a separate workaround, and it does not provide specific detection guidance beyond the test cases. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Summarized from github.com/i18next/i18next-http-backend…a76b22cb45d48f1e35b7 Impact if exploited ConfidentialityNone IntegrityLow AvailabilityNone How it is exploited Attack vector Network Attack complexity Low Attack requirements Present Privileges required None User interaction Passive CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X Affects i18next i18next-http-backend NIST National Vulnerability DatabasePublished Oct 23, 2026 13:17 UTC Read the advisory
	Low	3.7	CVE-2026-105800	i18next-http-backend is a backend layer for i18next that loads translation resources in Node.js, browsers, and Deno i18nexti18next-http-backend	NVD	Oct 6 15:17 UTC
CVE-2026-105800i18next-http-backend is a backend layer for i18next that loads translation resources in Node.js, browsers, and Deno From the advisory 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. Impact if exploited ConfidentialityLow IntegrityNone AvailabilityNone How it is exploited Attack vector Network Attack complexity High Privileges required None User interaction None Scope Unchanged CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N Affects i18next i18next-http-backend NIST National Vulnerability DatabasePublished Oct 6, 2026 15:17 UTC Read the advisory

Example	Finds
	Every word appears somewhere: title, summaries, IDs, vendor, or product
	An exact phrase
	One vendor. product: for a product, vp: for either
	Commas mean any of them, in every field
	Severity: critical, high, medium, low, or unknown
	CVSS score, with >, >=, <, or <=
	A score range
	Known exploited. is:kev works too, and kev:no leaves them out
	One source, by name
	Confidentiality impact: high, low, none, or any (low or high)
	Integrity and availability work the same way
	An advisory or CVE ID, or part of one
	A minus sign leaves out whatever the term matches

Vulnerability feed

Executive summary

Technical summary

Impact if exploited

How it is exploited

Affects

From the advisory

Impact if exploited

How it is exploited

Affects

Search syntax

Welcome to CVEsee.org

What is CVEsee.org?

Disclaimer

You are leaving CVEsee.org

Install CVEsee