https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T07:43:56.638670+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/certfr-2026-avi-1256 certfr-2026-avi-1256 — De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquan… 2026-10-03T07:43:56.692050+00:00 certfr-2026-avi-1256 https://cve.radiocsirt.org/vuln/cleanstart-2026-fv05780 Withdrawn: CLEANSTART-2026-FV05780 — Security fixes in langfuse 3.213.0-r1 2026-10-03T07:43:56.692092+00:00

Withdrawn by the publisher.

Affected: CleanStart: langfuse

Package langfuse version 3.213.0-r1 fixes 24 vulnerabilities: CVE-2026-59895, CVE-2026-59896, CVE-2026-59897, CVE-2026-69207, CVE-2026-71848...

 https://cve.radiocsirt.org/vuln/euvd-2026-341426 EUVD-2026-341426 2026-10-03T07:43:56.692123+00:00 EUVD-2026-341426 https://cve.radiocsirt.org/vuln/fkie_cve-2026-64647 fkie_cve-2026-64647 2026-10-03T07:43:56.692136+00:00

Next.js is a React framework for building full-stack web applications. In versions 12.0.0 through 15.5.20 and 16.0.0 through 16.2.10, a server-side fetch with a request body may return a cached response body from a different request to the same URL but different body. Confidential data in the POST's response body would then leak to unauthorized requests. Though the request itself will not be deduped. This is only an issue when receiving request bodies with a content type charset other than UTF-8. For example, the UTF-16 byte sequences for 삃삃 and 섄섄 in the request body would share the same cache. This issue has been fixed in versions 15.5.21 and 16.2.11.

 https://cve.radiocsirt.org/vuln/ghsa-4633-3j49-mh5q GHSA-4633-3j49-mh5q — Next.js: Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences 2026-10-03T07:43:56.692165+00:00

Affected: npm: next

## Impact

A server-side `fetch` with a request body may return a cached **response** body from a different request to the same URL but different body. Confidential data in the `POST`'s **response** body would then leak to unauthorized requests. Though the request itself will not be deduped.

This is only an issue when receiving request bodies with a content type charset other than UTF-8. For example, the UTF-16 byte sequences for `삃삃` and `섄섄` in the request body would share the same cache.

## Workarounds

If you cannot upgrade, consider only making fetch requests with UTF-8 bodies (default in Next.js). Applications using Pages Router are not vulnerable.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2468 WID-SEC-W-2026-2468 — Vercel Next.js: Mehrere Schwachstellen 2026-10-03T07:43:56.692195+00:00

Ein Angreifer kann mehrere Schwachstellen in Vercel Next.js ausnutzen, um Daten zu manipulieren, um Informationen offenzulegen, um einen Denial of Service Angriff durchzuführen, und um Sicherheitsvorkehrungen zu umgehen.