appsec.fyi

Server-Side Request Forgery (SSRF) Resources

Post Share

A curated AppSec resource library covering XSS, SQLi, SSRF, IDOR, RCE, XXE, OSINT, and more.

Server-Side Request Forgery (SSRF)

In a Server-Side Request Forgery (SSRF) attack, the attacker abuses functionality on the server to read or update internal resources. By supplying or modifying a URL that the server-side code processes, the attacker can reach internal services, read cloud metadata, and access systems that are not exposed to the internet.

SSRF has become one of the highest-impact vulnerability classes in modern cloud environments. Accessing the cloud metadata endpoint (http://169.254.169.254) from an SSRF can yield temporary IAM credentials, leading to full cloud account compromise. Even in non-cloud environments, SSRF enables port scanning of internal networks, accessing internal admin panels, and reaching databases or caches that trust requests from localhost.

Attackers use a wide range of bypass techniques to defeat SSRF filters: DNS rebinding, IP address encoding variations (decimal, octal, hex), URL parser inconsistencies, IPv6 representations, and redirect chains. Partial SSRF — where the attacker controls only part of the URL — can still be exploitable through open redirects or URL fragment abuse.

SSRF commonly appears in webhook integrations, URL preview features, PDF generators, image processors, and any functionality that fetches remote resources on behalf of the user.

This page collects SSRF research, bypass techniques, cloud exploitation methods, and real-world writeups from bug bounty programs and security research.

From OWASP

Date Added Link Excerpt
2026-05-22 NEW 2026Mr Binu: Can anyone share their SSRF hunting methodology? Like how you approach recon identify potential sinks detect SSRF and test bypasses Trying to level up my SSRF game would love to learn from other hunters #bugbounty #ssrf #cybersecurity intermediateA cybersecurity researcher, Mr. Binu, is seeking insights into effective Server-Side Request Forgery (SSRF) hunting methodologies from fellow bug bounty hunters. They are looking for guidance on reconnaissance, identifying potential vulnerable endpoints (sinks), detection techniques, and bypass strategies. Mr. Binu aims to enhance their SSRF exploit skills by learning from the community's experiences.
2026-05-18 NEW 2026CCB Alert: Warning: Critical vulnerability in #Node.js server CVE-2026-44578 CVSS: 8.6. When using the built-in server server-side request forgery #SSRF is possible causing the server to proxy any requests to in- or external destinations. More info: #Patch #Patch newsA critical vulnerability, CVE-2026-44578 (CVSS 8.6), has been identified in Node.js's built-in server. This Server-Side Request Forgery (SSRF) flaw allows attackers to make the server proxy requests to any internal or external destination. Users are advised to patch their Node.js installations to mitigate this risk.
2026-05-18 NEW 2026Gray Hats: Critical SSRF vulnerability CVE-2026-44578 impacts self-hosted Next.js applications. Upgrade to version 15.5.16 or 16.2.5 immediately to block the exploit. #NextJS #SSRF #CVE202644578 #WebSecurity2026 #NodeJS #DevSecOps #AppSec newsA critical Server-Side Request Forgery (SSRF) vulnerability, CVE-2026-44578, has been discovered affecting self-hosted Next.js applications. This vulnerability poses a significant security risk and can be exploited. Developers are urged to immediately upgrade their Next.js installations to either version 15.5.16 or 16.2.5 to patch this critical flaw and prevent potential exploitation.
2026-05-17 NEW 2026CiberInteligencia Chile: NEXT.JS CRÍTICO: CVE-2026-44578 (SSRF) Falla en WebSocket robo de credenciales cloud API keys y acceso a paneles internos Afecta self-hosted. Actualiza para evitar explotación #Nextjs #SSRF #CVE #Ciberseguridad newsCiberInteligencia Chile: 🚨 NEXT.JS CRÍTICO: CVE-2026-44578 (SSRF) 🔓 Falla en WebSocket → robo de credenciales cloud, API keys y acceso a paneles internos ⚠️ Afecta self-hosted. Actualiza para evitar e...
2026-05-17 NEW 2026xHackInSeconds: URL field accepted internal addresses. 169.254.169.254. IAM role credentials in the response. Full S3 and RDS access. #infosec #cloud #ssrf newsxHackInSeconds discovered a critical vulnerability where a URL field accepted internal IP addresses, specifically 169.254.169.254. This allowed for Server-Side Request Forgery (SSRF) attacks. The vulnerability led to the exposure of IAM role credentials within the response, granting attackers full access to S3 buckets and RDS instances. The specific payout amount for this bug bounty was not stated.
2026-05-17 NEW 2026White Rabbitx : CVE-2026-7221 A vulnerability in TencentCloudBase CloudBaseMCP up to 2.17.0 affects openUrl; manipulating req.body.url can lead to remote SSRF. #CVE-2026-7221 #CloudBaseMCP #SSRF #Vulnerability #CWE918 nvd.nist.gov/vuln/detail/CVE newsA vulnerability, CVE-2026-7221, has been identified in TencentCloudBase CloudBase-MCP versions up to 2.17.0. The issue, related to the `openUrl` function, allows for remote Server-Side Request Forgery (SSRF) by manipulating the `req.body.url`. This could enable attackers to make unauthorized requests on behalf of the server.
2026-05-15 NEW 2026Rasputin.DZ: got my first "exceptional technical depth" on a duplicate report half compliment half punishment. building my way up one dupe at a time. The grind continues. #bugbounty #infosec #SSRF #OWASP #WebAppSec #APIsecurity #CloudSecurity #GCP beginnerRasputin.DZ received their first "exceptional technical depth" rating on a duplicate bug bounty report, viewing it as both a compliment and a setback. They are focusing on building their experience through these reports, emphasizing the ongoing "grind" in the bug bounty and infosec space. The report involved an SSRF vulnerability and touched upon web application security, API security, and cloud security on GCP.
2026-05-15 NEW 2026Critical Next.js Vulnerability Exposes Cloud Credentials API keys and Admin Panels newsA critical vulnerability in Next.js has been disclosed, potentially exposing sensitive cloud credentials, API keys, and admin panels. This flaw could allow attackers to gain unauthorized access to vital system resources. Further details on the exploit and mitigation strategies are available through the provided link, which was shared via IFTTT. → cybersecuritynews.com
2026-05-13 2026BRute Logic: Localhost with Ideographic Full Stop (IFS) http://127%E3%80%820%E3%80%820%E3%80%821 http://127%EF%BD%A10%EF%BD%A10%EF%BD%A11 Combining these with the other bypass techniques described below can make all the difference. #SSRF #BugBounty intermediateBRute Logic: Localhost with Ideographic Full Stop (IFS) http://127%E3%80%820%E3%80%820%E3%80%821 http://127%EF%BD%A10%EF%BD%A10%EF%BD%A11 Combining these with the other bypass techniques described bel...
2026-05-10 2026Multiple Critical Flaws Fixed in Next.js and React Server Components newsLibrary patches address critical vulnerabilities in Next.js versions 13.x to 16.x. These include CVE-2026-44575 and CVE-2026-44574, which allow unauthenticated middleware and authentication bypasses through specially crafted URLs and query parameters. Denial of Service (DoS) vulnerabilities, CVE-2026-23870 and CVE-2026-44579, exploit server function deserialization and cache component deadlocks, respectively. Additionally, CVE-2026-44578 enables Server-Side Request Forgery (SSRF) via manipulated WebSocket upgrade requests in self-hosted deployments. Updates to versions 15.5.16 and 16.2.5 are urgently recommended. → gbhackers.com
2026-05-08 2026Multiple Critical Vulnerabilities Patched in Next.js and React Server Components newsLibrary patches address critical vulnerabilities in Next.js and React Server Components, including CVE-2026-44575 and CVE-2026-44574 for middleware bypasses, CVE-2026-44573 for SSRF in legacy i18n setups, DoS flaws CVE-2026-23870 and CVE-2026-44579, and a critical SSRF in CVE-2026-44578 affecting self-hosted deployments. Developers must update to versions 15.5.16 or 16.2.5. → cyberpress.org
2026-05-08 2026Upwind Security MDR: GitHub Enterprise Server SSRF: CVE-2026-8034 A high-severity SSRF vulnerability in the GitHub Enterprise Server notebook viewer could allow attackers to access internal services via URL parser confusion. #GitHub #SSRF #CVE #CyberSecurity newsUpwind Security MDR reports a high-severity Server-Side Request Forgery (SSRF) vulnerability (CVE-2026-8034) in GitHub Enterprise Server's notebook viewer. This flaw, stemming from URL parser confusion, enables attackers to access internal services.
2026-05-08 2026Multiple Critical Vulnerabilities Patched in Next.js and React Server Components newsMultiple critical vulnerabilities have been patched in Next.js and React Server Components. These security flaws could have allowed for unauthorized code execution and data exposure. Developers are urged to update their Next.js and React Server Components to the latest versions immediately to mitigate these risks. The exact payout amounts for the bounties related to these vulnerabilities were not specified in the provided content. → cybersecuritynews.com
2026-05-06 2026Nitin Gavhane: SSRF and Business Logic flaws create high severity attack chains. Map workflows deeply and test actions that should never be possible. Parallel requests often reveal hidden race conditions. #BugBounty #SSRF #BusinessLogic #WebSecurity intermediateNitin Gavhane highlights how Server-Side Request Forgery (SSRF) and business logic vulnerabilities can be chained together to create high-severity attack chains. He advises bug bounty hunters to deeply map application workflows and specifically test actions that should be impossible. Gavhane also notes that using parallel requests can uncover hidden race conditions, a crucial technique for web security testing.
2026-05-05 2026Common SSRF targets include webhooks import features and URL previews. Protocols like gopher can be used for deeper service exploitation. Blind SSRF requires creativity and observation of side effects. #BugBounty #BugHunting #SSRF #InfoSec intermediateCommon SSRF targets include webhooks import features and URL previews. Protocols like gopher can be used for deeper service exploitation. Blind SSRF requires creativity and observation of side effects...
2026-05-05 2026Chetan Biranje: AppSec Tip #6 SSRF Making servers attack themselves. How to test: Find URL input fields Point to 127.0.0.1 Try 169.254.169.254 (cloud metadata) Server responds? = SSRF Fix: Whitelist allowed URLs Block internal IP ranges #AppSec #BugBounty #SSRF beginnerChetan Biranje: 🔐 AppSec Tip #6 SSRF — Making servers attack themselves. How to test: → Find URL input fields → Point to 127.0.0.1 → Try 169.254.169.254 (cloud metadata) → Server responds? = SSRF ✅ Fi...
2026-05-04 2026Real world SSRF often leads to IAM credential exposure. Even blind SSRF can prove impact through timing or external callbacks. Strong reports with clear business impact increase payout chances. #BugBounty #InfoSec #SSRF #CyberSecurity intermediateReal world SSRF often leads to IAM credential exposure. Even blind SSRF can prove impact through timing or external callbacks. Strong reports with clear business impact increase payout chances. #BugBo...
2026-05-04 2026SSRF can be chained into advanced exploitation paths. Examples include Redis command injection internal file access and remote code execution. Blind SSRF can be detected using timing or out of band techniques. #BugBounty #EthicalHacking #SSRF #InfoSec intermediateSSRF can be chained into advanced exploitation paths. Examples include Redis command injection internal file access and remote code execution. Blind SSRF can be detected using timing or out of band te...
2026-05-02 2026Oxygen Theme WP =6.0.8: Unauth SSRF in laborator_calc_route AJAX. No URL validation hit cloud metadata or internals. CVSS 7.2. Patch it. #SSRF #WordPress #DevSecOps #CVE #infosec #developers Info: newsOxygen Theme WP =6.0.8: Unauth SSRF in laborator_calc_route AJAX. No URL validation, hit cloud metadata or internals. CVSS 7.2. Patch it. #SSRF #WordPress #DevSecOps #CVE #infosec #developers Info: ht...
2026-05-02 2026SSRF: It allows the server to make requests to internal networks and cloud metadata. Look for features like image fetchers webhooks PDF generators and URL previews. Test by replacing URLs with your Interactsh domain to detect callbacks. #BugBounty #SSRF #EthicalHacking pic. beginnerSSRF: It allows the server to make requests to internal networks and cloud metadata. Look for features like image fetchers webhooks PDF generators and URL previews. Test by replacing URLs with your In...
2026-05-02 2026Advanced SSRF exploitation techniques are explained in detailed guides. They include bypass methods and cloud metadata attacks. Read #BugBounty #SSRF #CyberSecurity #Research intermediateAdvanced SSRF exploitation techniques are explained in detailed guides. They include bypass methods and cloud metadata attacks. Read #BugBounty #SSRF #CyberSecurity #Research https://ift.tt/flbmEPv
2026-05-02 2026Advanced SSRF requires bypass techniques like IPv6 and redirect chains. Cloud metadata access remains a high impact target. AI systems introduce new vulnerabilities like prompt injection. #BugBounty #SSRF #AISecurity #CyberSecurity intermediateAdvanced SSRF requires bypass techniques like IPv6 and redirect chains. Cloud metadata access remains a high impact target. AI systems introduce new vulnerabilities like prompt injection. #BugBounty #...
2026-05-02 2026Advanced SSRF bypass techniques include decimal IP encoding and hexadecimal formats. DNS rebinding and parser differences can bypass filters effectively. Protocols like gopher enable deeper exploitation scenarios. #BugBounty #SSRF #CyberSecurity #Hacking advancedAdvanced SSRF bypass techniques include decimal IP encoding and hexadecimal formats. DNS rebinding and parser differences can bypass filters effectively. Protocols like gopher enable deeper exploitati...
2026-05-01 2026SSRF combined with cloud metadata access leads to high impact vulnerabilities. AWS metadata endpoints expose temporary credentials for IAM roles. These credentials can lead to full cloud compromise if exploited. #BugBounty #CloudSecurity #SSRF #CyberSecurity advancedSSRF combined with cloud metadata access leads to high impact vulnerabilities.  AWS metadata endpoints expose temporary credentials for IAM roles.  These credentials can lead to full cloud compromise ...
2026-05-01 2026How Escape AI Pentesting Exploited SSRF in LiteLLM intermediateWriteup detailing SSRF vulnerabilities in LiteLLM, specifically highlighting three sinks found by Escape AI pentesting. The first sink, a blind SSRF via the `/v1/rag/ingest` endpoint, is exploitable by any authenticated user, allowing access to loopback and cloud-metadata addresses without destination validation. The second sink, found in `/search_tools/test_connection`, bypasses a previously implemented security gate by nesting `api_base` within `litellm_params`, enabling SSRF for admin users. The third sink, `/health/test_connection`, also requires admin privileges and demonstrates full-read SSRF through a similar nested `api_base` parameter. → securityboulevard.com
2026-04-29 2026Nginx-UI SSRF (GHSA-wr32-99hh-6f35) CVSS 8.5 Authenticated users can access internal services & metadata endpoints potential RCE chain. #SSRF #CVE newsNginx-UI is vulnerable to a critical Server-Side Request Forgery (SSRF) vulnerability (GHSA-wr32-99hh-6f35) with a CVSS score of 8.5. Authenticated users can exploit this flaw to access internal services and metadata endpoints. This could potentially lead to a Remote Code Execution (RCE) chain.
2026-04-29 2026CVE-2026-33626: Critical SSRF Vulnerability in LMDeploy Rapidly Exploited in the Wild Technical Analysis and Mitigation Guide newsAnalysis of CVE-2026-33626 details a critical Server-Side Request Forgery (SSRF) vulnerability in LMDeploy, exploited rapidly in the wild. This flaw, affecting versions up to 0.12.0 with vision-language support, allows attackers to fetch arbitrary URLs, leading to the exfiltration of cloud metadata, probing of internal services like Redis and MySQL, and network reconnaissance. Exploitation attempts utilized callback infrastructure such as cw2mhnbd.requestrepo.com, originating from IP 103.116.72.119. Mitigation involves upgrading LMDeploy, enforcing IMDSv2, restricting egress, and implementing runtime detection of suspicious outbound connections. → rescana.com
2026-04-28 2026Already cycled through 400 vectors. Looking for a wizard to bypass this response filtering or pivot via OOB exfiltration. #BugBounty #InfoSec #SSRF #RedTeam #CyberSecurity intermediateA security researcher is seeking assistance with a bug bounty challenge, having exhausted over 400 vectors to bypass response filtering or achieve Out-of-Band (OOB) exfiltration. They are looking for an expert ("wizard") to help crack this particular vulnerability. The post is tagged with #BugBounty, #InfoSec, #SSRF, #RedTeam, and #CyberSecurity, indicating the context of a bug bounty program and the nature of the security testing involved. No specific payout amount is mentioned.
2026-04-28 2026To be clear: this is a "gov-related" scope. I strictly follow the program's terms and will not disclose anything further publicly. I am only seeking assistance to find an optimal bypass for the response filtering. #BugBounty #InfoSec #SSRF #CyberSecurity intermediateA cybersecurity professional is seeking help within a bug bounty program focused on a government-related scope. They emphasize adherence to program terms and will not publicly disclose details. Their primary objective is to find an optimal bypass for response filtering, suggesting a focus on Server-Side Request Forgery (SSRF) vulnerabilities. No payout amount is mentioned.
2026-04-28 2026SSRF Hunter Challenge | ive got a 100% functional Open SSRF on a high-value target. WAF bypassed via Decimal IP encoding but i'm hitting a wall: the response body is strictly filtered/stripped by egress inspection.#BugBounty #InfoSec #SSRF #RedTeam #CyberSecurity intermediateA security researcher has achieved a functional Open SSRF on a high-value target, successfully bypassing WAF using Decimal IP encoding. However, they are facing a challenge as the response body is heavily filtered by egress inspection. The researcher shared this experience as part of an #SSRF Hunter Challenge on social media, seeking solutions or insights from the #BugBounty and #InfoSec communities. No payout amount was specified.
2026-04-27 2026Old but gold. #SSRF = #LFD intermediateThis content highlights a security vulnerability where Server-Side Request Forgery (SSRF) can be exploited to achieve Local File Disclosure (LFD). The accompanying link likely details a specific instance or method of this combined attack. No bug bounty payout amount is mentioned.
2026-04-27 2026NEW THREAT INTEL: LMDeploy SSRF (CVE-2026-33626) - Unauth SSRF in load_image() coerces AI inference servers to fetch arbitrary URLs. Exploited 13h after disclosure. 9 detections 18 IOCs. #ThreatIntel #CyberSecurity #SSRF #AISecurity pic. newsA critical Server-Side Request Forgery (SSRF) vulnerability, CVE-2026-33626, has been discovered in LMDeploy's `load_image()` function. This vulnerability allows unauthenticated attackers to force AI inference servers to fetch arbitrary URLs, posing a significant security risk. The exploit was observed in the wild just 13 hours after its disclosure, indicating its severity and immediate impact. Security teams have identified 9 detections and 18 Indicators of Compromise (IOCs) related to this threat.
2026-04-27 2026If an app fetched PDFs via ?url= classic SSRF setup. Bypass? Enumerate internal PDF subdomains. Swap the file ID other users' docs. SSRF IDOR chained. #bugbounty #SSRF intermediateThis bug bounty report details a chained SSRF (Server-Side Request Forgery) and IDOR (Insecure Direct Object Reference) vulnerability. The flaw arises when an application fetches PDFs using a `?url=` parameter, a common SSRF setup. Attackers can potentially bypass security measures to enumerate internal PDF subdomains. By manipulating the file ID, they can access documents belonging to other users. This combination of SSRF and IDOR creates a significant security risk.
2026-04-26 2026A critical LMDeploy SSRF vulnerability exploitation campaign launched under 13 hours after disclosure. #SSRF #CVE #AIsecurity #LLMsecurity #Sysdig #ActiveExploitation #CloudSecurity #GenAI #InfoSec pic. newsA critical Server-Side Request Forgery (SSRF) vulnerability in LMDeploy was actively exploited within 13 hours of its disclosure. This indicates a rapid threat response by attackers, highlighting the immediate risks associated with newly revealed vulnerabilities in AI and LLM security. The exploitation underscores the importance of swift patching and security measures in cloud and AI environments.
2026-04-24 2026LMDeploy SSRF alert CVE-2026-33626 exploited within hours Attackers can access internal services & cloud metadata. Update now & restrict outbound requests.vulert.com/blog/lmdeploy-p #CyberSecurity #SSRF #AIsecurity #Vulert news🚨 LMDeploy SSRF alert CVE-2026-33626 exploited within hours ⚠️ Attackers can access internal services & cloud metadata. Update now & restrict outbound requests.vulert.com/blog/lmdeploy-…p #CyberSecuri...
2026-04-24 2026LMDeploy CVE-2026-33626 Flaw Exploited Within 13 Hours of Disclosure newsLibrary that facilitates the deployment and serving of large language models, LMDeploy, is vulnerable to CVE-2026-33626, a high-severity Server-Side Request Forgery (SSRF) flaw. This vulnerability, discovered by Igor Stepansky and observed being exploited by Sysdig within 13 hours of disclosure, allows attackers to fetch arbitrary URLs via the `load_image()` function in `lmdeploy/vl/utils.py`. Exploitation can lead to accessing cloud metadata services, internal networks, sensitive data, and port scanning of internal systems, as demonstrated by active attempts against AWS IMDS and Redis. → thehackernews.com
2026-04-23 2026Attackers Exploit LMDeploy Flaw in the Wild Within 12 Hours of Advisory newsAttackers Exploit LMDeploy Flaw in the Wild Within 12 Hours of Advisory https://ift.tt/xWknlfA → gbhackers.com
2026-04-23 2026CVE-2026-33626 exposes an SSRF in LMDeploys vision-language image loader. Attackers accessed AWS IMDS scanned local services and confirmed egress within 12 hours. Update to v0.12.3 and enforce IMDSv2. #LMDeploy #SSRF #USA ift.tt/PVn3XMk newsCVE-2026-33626 exposes an SSRF in LMDeploy’s vision-language image loader. Attackers accessed AWS IMDS, scanned local services, and confirmed egress within 12 hours. Update to v0.12.3 and enforce IMDS...
2026-04-23 2026CVE-2026-33626: A critical SSRF in LMDeploy exploited in under 13 hours. Learn how attackers hijack AI nodes and how to secure your inference cloud now. #CVE202633626 #SSRF #AISecurity #LMDeploy #InfoSec #CyberAttack #CloudSecurity #LLM #PatchNow securityonline.info/cve-2026-33626 pic.x.com/09IZxf21rQ newsCVE-2026-33626: A critical SSRF in LMDeploy exploited in under 13 hours. Learn how attackers hijack AI nodes and how to secure your inference cloud now. #CVE202633626 #SSRF #AISecurity #LMDeploy #Info...
2026-04-22 2026Critical Spring Authorization Server Issue Exposes Systems to XSS and SSRF Attacks newsCritical Spring Authorization Server Issue Exposes Systems to XSS and SSRF Attacks https://ift.tt/y4laiIW → gbhackers.com
2026-04-22 2026Critical Spring Authorization Server Flaw Enables XSS Privilege Escalation and SSRF newsCritical Spring Authorization Server Flaw Enables XSS, Privilege Escalation, and SSRF https://ift.tt/b2pauUc → cyberpress.org
2026-04-22 2026LibreChat SSRF Bypass via IPv6 Mapped Address Confusion intermediateWriteup of CVE-2026-31943 in LibreChat details a Server-Side Request Forgery bypass where authenticated users can exploit the `isPrivateIP()` function's failure to detect hex-normalized IPv4-mapped IPv6 addresses. This allows the LibreChat server to send HTTP requests to internal network resources, including cloud metadata services and loopback addresses, undermining SSRF protections. Versions prior to 0.8.3 are affected. → thehackerwire.com
2026-04-22 2026SSRF Vulnerability: Bypassing Protection with DNS Rebinding Attack intermediateWriteup detailing CVE-2025-69660, a Server-Side Request Forgery (SSRF) vulnerability in simstudioai/sim's proxy and file parsing APIs. The writeup explains how this SSRF could be bypassed using a DNS rebinding attack, specifically by exploiting a time-of-check-to-time-of-use (TOCTOU) vulnerability. It further details the fix implemented by the development team, DNS pinning, which resolves hostnames to IP addresses once to prevent subsequent malicious rebinding.
2026-04-22 2026is-localhost-ip 2.0.0 SSRF via Restrictions Bypass (CVE-2025-9960) newsLibrary is-localhost-ip 2.0.0 suffers from a Server-Side Request Forgery (SSRF) vulnerability due to a bypass of its localhost restrictions. The library misclassifies IPv6-mapped IPv4 addresses like ::ffff:127.0.0.1 and certain private/link-local IP ranges as localhost, incorrectly expanding the trust boundary. This allows attackers to target internal services by crafting requests that exploit these misclassifications, as documented in CVE-2025-9960.
2026-04-22 2026See-SURF: Tool to Find Potential Vulnerable SSRF Parameters beginnerTool for detecting Server-Side Request Forgery (SSRF) vulnerabilities. See-SURF automates reconnaissance by crawling web applications, parsing Burp Suite sitemaps, and identifying potential SSRF parameters using regex. It incorporates AI-powered validation with providers like Google Gemini and OpenAI for context-aware payload generation and exploitation of services such as AWS Metadata. For blind SSRF, it leverages Out-of-Band (OOB) detection via Webhook.site or custom domains.
2026-04-22 2026Hacking Next.js Targets: Advanced SSRF Exploitation Guide advancedGuide detailing advanced Server-Side Request Forgery (SSRF) vulnerabilities in Next.js applications. It covers exploitation techniques targeting the Image component, Next.js Middleware (CVE-2025-57822), and Server Actions (CVE-2024-34351). The guide highlights how misconfigurations in these features can lead to arbitrary outbound requests and potential data leakage or remote code execution. → intigriti.com
2026-04-22 2026Catflix CTF: Exploiting SSRFs in Next.js Middleware intermediateWalkthrough of CVE-2025-57822 in Next.js Middleware, chaining SSRF to RCE via Jenkins. This article details exploiting a misconfiguration in Next.js middleware that allows processing of the `Location` header to perform server-side requests. The SSRF is then escalated by identifying an open Jenkins instance on port 8080, enabling command execution through its Groovy Script console to retrieve sensitive files, demonstrating a practical vulnerability exploitation chain. → intigriti.com
2026-04-22 2026SSRF Guard Bypass via Full-Form IPv4-Mapped IPv6 Literal intermediateLibrary advisory detailing an SSRF protection bypass vulnerability in OpenClaw's `ssrf.ts` component. Versions up to `2026.2.13` are affected by CWE-918, where full-form IPv4-mapped IPv6 literals like `0:0:0:0:0:ffff:7f00:1` bypassed loopback and private network blocking. A fix is available in versions `2026.2.14` and later, addressed by commit `c0c0e0f9aecb913e738742f73e091f2f72d39a19`.
2026-04-22 2026Next.js Improper Middleware Redirect Handling Leads to SSRF (CVE-2025-57822) newsLibrary update addressing CVE-2025-57822 in Next.js Middleware, where improper handling of request headers passed to `NextResponse.next()` could lead to Server-Side Request Forgery (SSRF) in self-hosted applications. Versions v14.2.32 and v15.4.7 resolve this vulnerability by preventing sensitive headers from being reflected back in responses. Users with custom middleware in self-hosted environments should upgrade and verify `next()` function usage.
2026-04-22 2026Craft CMS Cloud Metadata SSRF Protection Bypass via IPv6 Resolution intermediateAdvisory detailing a bypass of Craft CMS's GraphQL SSRF protection. The vulnerability, a bypass of CVE-2025-68437 (GHSA-x27p-wfqw-hfcc), occurs because `gethostbyname()` only resolves IPv4 addresses. When a hostname has only AAAA (IPv6) records, the function returns the hostname string itself, failing the blocklist comparison. This allows attackers with GraphQL schema permissions to steal AWS credentials by targeting the AWS IMDS IPv6 endpoint via crafted URLs.

Frequently Asked Questions

What is SSRF and why is it critical?
Server-Side Request Forgery (SSRF) tricks the server into making HTTP requests to unintended destinations. It is critical because it can access internal services, cloud metadata endpoints (169.254.169.254), and private networks that are not reachable from the internet, potentially leading to full cloud account compromise.
What are common SSRF bypass techniques?
Common bypasses include DNS rebinding, IP encoding tricks (decimal, octal, hex, IPv6), URL parser inconsistencies between the filter and the HTTP library, open redirect chains, and alternative URL schemes. Attackers also use shortened URLs and domain names that resolve to internal IPs.
Where does SSRF commonly appear?
SSRF is frequently found in webhook integrations, URL preview and unfurling features, PDF and screenshot generators, image/file processing pipelines, and any functionality where the application fetches a remote resource based on user-supplied URLs.

Weekly AppSec Digest

Get new resources delivered every Monday.