Signal is active with 1 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD description
Next.js is a React framework that can provide building blocks to create web applications. A Server-Side Request Forgery (SSRF) vulnerability was identified in Next.js Server Actions. If the `Host` header is modified, and the below conditions are also met, an attacker may be able to make requests that appear to be originating from the Next.js application server itself. The required conditions are 1) Next.js is running in a self-hosted manner; 2) the Next.js application makes use of Server Actions; and 3) the Server Action performs a redirect to a relative path which starts with a `/`. This vulnerability was fixed in Next.js `14.1.1`.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
AVAILABLE
Momentum
STABLE
If you run products in this scope, you should treat this CVE as relevant to your environment.
CVE-2024-34351 in Next.js is a good reminder that SSRF isn't a solved problem. full-read SSRF through a popular framework used by millions of production apps. the attack surface keeps growing as the abstraction layers pile up
Post summary
The statement highlights a full‑read SSRF vulnerability in Next.js (CVE‑2024‑34351) and notes its prevalence, but it provides no PoC, exploit code, active usage data, or patch information.
#RCE attempt targeting Langflow (CVE-2024-34351) 2026-09-14 00:44:14 UTC Source IP: 91.92.40.236 🇸🇪 POST / IOCs: hxxp://217.60.195.239/x86 217.60.195.239 🇦🇪 be809872eb1115c985a6685e54790bb4 https://t.co/qRxp3ZD1La
1 of 1 entries
| Part | Vendor | Product | Version | Target SW | Target HW |
|---|---|---|---|---|---|
| App | vercel | next.js | - | node.js | - |