Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-44578 | 8.6 HIGH | Next.js: Server-side request forgery in applications using WebSocket upgrades |
| CVE-2026-44574 | 8.1 HIGH | Next.js: Middleware / Proxy bypass through dynamic route parameter injection |
| CVE-2026-45109 | 7.5 HIGH | Next.js: Middleware / Proxy bypass in App Router applications via segment-prefetch routes |
| CVE-2026-44579 | 7.5 HIGH | Next.js: Denial of Service via connection exhaustion in applications using Cache Component |
| CVE-2026-44573 | 7.5 HIGH | Next.js: Middleware / Proxy bypass in Pages Router applications using i18n |
| CVE-2026-44580 | 6.1 MEDIUM | Next.js: Cross-site scripting in beforeInteractive scripts with untrusted input |
| CVE-2026-44577 | 5.9 MEDIUM | Next.js: Denial of Service in the Image Optimization API |
| CVE-2026-44479 | 5.5 MEDIUM | Vercel: Non-interactive mode includes CLI arguments in suggested command output |
| CVE-2026-44576 | 5.4 MEDIUM | Next.js: Cache poisoning in React Server Component responses |
| CVE-2026-44581 | 4.7 MEDIUM | Next.js: Cross-site scripting in App Router applications using CSP nonces |
| CVE-2026-44572 | 3.7 LOW | Next.js: Middleware / Proxy redirects can be cache-poisoned |
| CVE-2026-44582 | 3.7 LOW | Next.js: Cache poisoning via collisions in React Server Component cache-busting |
No comments yet