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-06-11 NEW 2026Pre-auth XXE → HTTP SSRF on ArubaOS 8.13.2 closed as "theoretical / no valid PoC" despite TCP pcap, sshd localhost log, and internal port scan — documenting for community review advanced XXEA researcher reported a pre-authentication XXE vulnerability leading to an HTTP SSRF on ArubaOS 8.13.2. Despite providing evidence including TCP packet captures, SSH localhost logs, and an internal port scan, the vendor closed the report as "theoretical with no valid PoC." The researcher is documenting this for community review. No bounty amount was mentioned.
2026-06-10 NEW 2026TechEarl: Cloud metadata SSRF: how one vulnerable URL fetcher reaching the instance metadata endpoint escalates to full cloud account compromise. #CloudSecurity #SSRF intermediateThis article by TechEarl details a vulnerability where a Server-Side Request Forgery (SSRF) in a URL fetcher can lead to the compromise of an entire cloud account. By exploiting a vulnerable URL fetcher that can access the instance metadata endpoint, an attacker can gain unauthorized access to sensitive cloud credentials. This highlights a critical security flaw in cloud environments that allows for escalation from a simple request forgery to full account takeover.
2026-06-09 NEW 2026C0deRevenant: Turned a McDonald's meme into a Bounty A chatbot that shouldn't have done what it did. SSTI SSRF. Two programs. Two payouts. Full story here : #BugBounty #SSTI #SSRF #InfoSec #HappyHacking intermediateC0deRevenant discovered vulnerabilities in a McDonald's meme-themed chatbot, leading to two successful bug bounty payouts. The identified issues were Server-Side Template Injection (SSTI) and Server-Side Request Forgery (SSRF). These vulnerabilities allowed the chatbot to perform actions it was not intended to.
2026-06-08 NEW 2026AI Security Guard: Server-Side Request Forgery: What It Is & How To Fix It beginnerAI Security Guard: Server-Side Request Forgery: What It Is & How To Fix It https://ift.tt/cSCjzlL
2026-06-08 NEW 2026Precious Isiani: Day 20 #VACyberMentorship Learned SSRF set up my first cybersecurity lab on my machine. Now I can safely practice real attack scenarios hands-on. #Cybersecurity #SSRF beginnerOn Day 20 of #VACyberMentorship, Precious Isiani learned about Server-Side Request Forgery (SSRF) and successfully set up a personal cybersecurity lab. This allows for safe, hands-on practice of real attack scenarios.
2026-06-08 NEW 2026Cisco Unified Communications Manager Server-Side Request Forgery Vulnerability (CVE-2026-20230) news 1 min readWriteup of CVE-2026-20230, a critical Cisco Unified Communications Manager (Unified CM) and Cisco Unified Communications Manager Session Management Edition (Unified CM SME) vulnerability. This server-side request forgery (SSRF) flaw, caused by improper input validation for HTTP requests, allows unauthenticated, remote attackers to write files to the underlying operating system, potentially leading to root privilege escalation. Exploitation requires the WebDialer service to be enabled, which is disabled by default. → systemtek.co.uk
2026-06-08 NEW 2026Update: The Ending of My $500 Loss and Web Cache Poisoning Story. intermediateThe author recounts a personal experience where a $500 loss prompted them to revisit a previously discovered Web Cache Poisoning vulnerability. The initial discovery was documented but later forgotten. This unexpected financial setback led the author back to investigate the bug further, with the aim of resolving outstanding questions and understanding the implications of the vulnerability, ultimately turning a loss into a learning opportunity. → infosecwriteups.com
2026-06-06 NEW 2026Merge News: Cisco warns of a critical SSRF vulnerability (CVE-2026-20230) in Unified CM. Unauthenticated attackers can write files via WebDialer risking remote #cisco #vulnerability #ssrf #remotecodeexecution newsCisco has issued a warning about a critical SSRF vulnerability (CVE-2026-20230) in its Unified CM software. Unauthenticated attackers can exploit this flaw through the WebDialer feature to write files, potentially leading to remote code execution. This vulnerability poses a significant security risk, allowing unauthorized access and control over affected systems.
2026-06-06 NEW 2026ThreadLinqs: NEW THREAT INTEL: Cisco Unified CM WebDialer SSRF (CVE-2026-20230) - unauth flaw chains to file write for root. Public PoC. #ThreatIntel #Cisco #SSRF newsA critical vulnerability in Cisco Unified CM WebDialer (CVE-2026-20230) allows unauthenticated attackers to achieve root-level file writes. This is accomplished by chaining a Server-Side Request Forgery (SSRF) flaw, enabling attackers to write arbitrary files to the system. A public Proof-of-Concept (PoC) is available, highlighting the immediate threat to Cisco Unified Communications Manager deployments.
2026-06-06 NEW 2026Hi: callback services like pingback are criminally underrated. the gap between "suspicious behavior in a black box" and "here's the TCP transcript source IP and timing" is literally the difference between a triaged $4k report and a dup-closed nothing-burger. #bugbounty #SSRF intermediateCallback services like pingback are crucial but often overlooked in bug bounty hunting. Demonstrating suspicious behavior with detailed evidence, such as TCP transcripts, source IP, and timing, is the key differentiator between a valuable, triaged report and a dismissed one. This level of detail can turn a potential "nothing-burger" into a significant bounty, with the example given highlighting a $4k payout for such a well-supported finding related to SSRF vulnerabilities.
2026-06-06 NEW 2026Thinkkun: SSRF turns your server into an attacker's proxy. One URL preview feature = stolen AWS credentials in 2 requests. Blocklisting IPs fails -- 0x7f000001 2130706433 and [::1] all hit localhost. Use allowlists. #Pentesting #SSRF #Websecurity #Security #Linux intermediateThinkkun's URL preview feature suffers from a critical Server-Side Request Forgery (SSRF) vulnerability. This flaw allows attackers to leverage the server as a proxy, potentially leading to the theft of AWS credentials in just two requests. Traditional IP blocklisting methods are ineffective as attackers can bypass them by targeting localhost using various representations like `0x7f000001`, `2130706433`, and `[::1]`. The recommended mitigation is to implement allowlists instead of blocklists to prevent unauthorized server requests.
2026-06-05 NEW 2026CVE-2026-20230: Cisco Unified CM WebDialer SSRF Can Lead to Root-Level Compromise news 4 min readWriteup of CVE-2026-20230, a critical SSRF vulnerability in Cisco Unified CM and SME, enabling root-level compromise through arbitrary file writes. Exploitation requires the WebDialer service to be enabled, though it is disabled by default. Public Proof-of-Concept exploit code exists, making patching or disabling WebDialer the recommended immediate actions. Targeted monitoring for SSRF and post-exploitation signals can also aid defenders. → socradar.io
2026-06-04 NEW 2026Doyensec: A #security update for #safeurl addressing an #SSRF bypass in non-default configs affecting those with IPv6 support enabled. A fix was released within 12 hours of report. Upgrade to version 0.2.4: Thanks to @tonghuaroot for the report! #doyensec newsDoyensec has released a security update (version 0.2.4) for safeurl to address an SSRF bypass vulnerability. This bypass affects non-default configurations, specifically for users with IPv6 support enabled. A fix was deployed within approximately 12 hours of the vulnerability being reported by @tonghuaroot. Users are advised to upgrade to the latest version. No bug bounty payout amount was specified.
2026-06-04 NEW 2026Cisco Unified CM SSRF Flaw CVE-2026-20230: Public Exploit Code Opens Path to Root news 7 min readTool analysis of CVE-2026-20230, a critical Server-Side Request Forgery vulnerability in Cisco Unified Communications Manager's WebDialer Web Service. This flaw, CWE-918, allows arbitrary file writes and privilege escalation to root without authentication, with public exploit code now available. Mitigation involves disabling the WebDialer service or upgrading to patched versions (14SU6 or interim COP for 15SU5). → techtimes.com
2026-06-04 NEW 2026PoC Exploit Released for Cisco Unified Communications Manager Security Vulnerability newsA Proof-of-Concept (PoC) exploit has been released for a security vulnerability affecting Cisco Unified Communications Manager (CUCM). This vulnerability, detailed in a Cisco security advisory, allows attackers to potentially gain unauthorized access or disrupt services. The release of the PoC means that exploits are now publicly available, increasing the risk for organizations using vulnerable CUCM versions. It is crucial for users to apply the necessary patches and updates provided by Cisco to mitigate this threat. → gbhackers.com
2026-06-04 NEW 2026Critical Cisco Unified CM Bug Patched as Public Exploit Code Emerges news 1 min readAdvisory for CVE-2026-20230 details a critical vulnerability in Cisco Unified CM and Unified CM SME. Improper HTTP request validation allows unauthenticated remote attackers to perform SSRF attacks, potentially writing files to the OS for root privilege escalation. While public exploit code exists, exploitation requires the WebDialer service to be enabled, which is disabled by default. Mitigation involves disabling the WebDialer service until a patch is applied. → securityaffairs.com
2026-06-04 NEW 2026Cisco Unified Communications Manager Vulnerability Exposed Along With PoC Exploit Code newsCisco Unified Communications Manager (CUCM) has a critical vulnerability that has been publicly disclosed. Researchers have released Proof of Concept (PoC) exploit code for this vulnerability, meaning attackers can readily use it to compromise affected systems. This vulnerability poses a significant risk to organizations relying on CUCM for their communication infrastructure. Further details about the specific nature and impact of the exploit are expected to emerge. → cybersecuritynews.com
2026-06-04 NEW 2026Cisco Warns of Available PoC for Critical Unified CM Vulnerability news 2 min readAdvisory regarding CVE-2026-20230, a critical server-side request forgery (SSRF) vulnerability in Cisco Unified Communications Manager (Unified CM) and Unified CM SME. This flaw, with a CVSS score of 8.6, allows attackers to write files to the operating system, potentially leading to root privilege escalation. Proof-of-concept code is publicly available, though Cisco is unaware of active exploitation. The vulnerability impacts appliances with the WebDialer service enabled. Patches are available in Unified CM and Unified CM SME version 14SU6, with version 15SU5 expected in September. → securityweek.com
2026-06-04 NEW 2026Gray Hats: A critical Cisco Unified CM vulnerability is exposed. This public PoC code disclosure highlights a severe SSRF risk in WebDialer. #Cisco #SSRF #CVE202620230 #WebDialer #Cybersecurity #PoC intermediateA critical vulnerability in Cisco Unified Communications Manager (CM) has been publicly disclosed, featuring proof-of-concept (PoC) code. This exposes a severe Server-Side Request Forgery (SSRF) risk within the WebDialer component, identified by CVE-202620230. The disclosure, originating from Gray Hats, highlights a significant cybersecurity threat for Cisco users utilizing this feature.
2026-06-03 2026How an Unauthenticated MCP Server Led to SSRF LFI and AWS Credential Theft intermediate 13 min readWriteup of a real-world attack chaining Server-Side Request Forgery (SSRF), Local File Inclusion (LFI), and AWS credential theft via an unauthenticated Model Context Protocol (MCP) server. This finding highlights the rapid adoption of MCP for AI integrations, outpacing security maturity and leaving systems vulnerable to exploitation, as demonstrated by the theft of live AWS IAM credentials and database secrets from a customer environment. → cloudsek.com
2026-06-02 2026How an Unauthenticated MCP Server Led to SSRF LFI and AWS Credential Theft intermediate 13 min readLibrary for discovering and analyzing security risks in AI integrations. It highlights vulnerabilities in Model Context Protocol (MCP) servers, such as Server-Side Request Forgery (SSRF) and Local File Inclusion (LFI), demonstrated by a real-world case study where an unauthenticated MCP server led to AWS credential theft. The library addresses the growing attack surface created by rapid AI adoption and the security maturity gap in new AI-native technologies. → cloudsek.com
2026-06-02 2026xHackInSeconds: URL field accepted internal addresses. 169.254.169.254. IAM role credentials in the response. Full S3 and RDS access. #infosec #cloud #ssrf intermediatexF HackInSeconds discovered a vulnerability where a URL field accepted internal IP addresses, including the metadata service address 169.254.169.254. This allowed attackers to retrieve IAM role credentials from the response. With these credentials, they gained full access to S3 buckets and RDS instances. This highlights a critical Server-Side Request Forgery (SSRF) flaw in cloud environments.
2026-06-02 2026Hi: that NASA XXE chain is filthy. multiline DOCTYPE bypass SSRF chaining to get AWS metadata is exactly the kind of creative attack chain that gets $50k bounties. insane find honestly #WebSecurity #SSRF advancedA researcher discovered a "filthy" XXE (XML External Entity) chain attack against NASA. This sophisticated attack involves a multiline DOCTYPE bypass to achieve SSRF (Server-Side Request Forgery), ultimately enabling the retrieval of AWS metadata. This type of creative attack chain is highly valued in bug bounty programs, with potential payouts exceeding $50,000. The find is described as "insane" and highlights advancements in web security exploitation.
2026-06-02 2026Gray Hats: A critical Apache Fesod SSRF vulnerability has been found. Learn about the CVE-2026-49328 patch released to protect internal network resources. #ApacheFesod #SSRF #CVE202649328 #JavaSecurity #Cybersecurity newsA critical Server-Side Request Forgery (SSRF) vulnerability, identified as CVE-2026-49328, has been discovered in Apache Fesod. A patch has been released to address this security flaw, which could have allowed attackers to access internal network resources. The vulnerability highlights ongoing concerns within Java security and the broader cybersecurity landscape.
2026-06-01 2026TechEarl: SSRF makes a server fetch what the attacker chooses; in the cloud that means 169.254.169.254 leaking credentials. Why allowlists beat blocklists plus IMDSv2. #SSRF #WebSecurity techearl.com/server-side-req intermediateServer-Side Request Forgery (SSRF) allows attackers to force servers to fetch arbitrary data. In cloud environments, this vulnerability can expose sensitive credentials by targeting the Instance Metadata Service (IMDS) at `169.254.169.254`. The article highlights the superiority of allowlists over blocklists for security and mentions the importance of Instance Metadata Service Version 2 (IMDSv2) in mitigating such risks.
2026-05-27 2026AI Security Guard: Server-Side Request Forgery: What It Is & How To Fix It beginnerThis article from AI Security Guard explains Server-Side Request Forgery (SSRF). SSRF is a vulnerability where an attacker can trick a server into making requests to unintended locations, potentially accessing internal resources or external services. The article likely details how SSRF attacks work, their potential impact, and provides guidance on how to prevent and mitigate these vulnerabilities. It is presented as a guide to understanding and securing against SSRF. No bounty payout amount is mentioned.
2026-05-27 2026AI Security Guard: Server-Side Request Forgery: What It Is & How To Fix It beginnerServer-Side Request Forgery (SSRF) is a vulnerability where an attacker can trick a server into making unintended requests to internal or external resources. This can lead to data breaches, unauthorized access, and even remote code execution. The article explains SSRF and outlines methods to prevent it, focusing on proper input validation, network segmentation, and disallowing direct access to sensitive internal systems. It emphasizes treating all user-supplied input as untrusted. No bug bounty payout amount is mentioned.
2026-05-27 20260xk4rim: WAF bypass via IP décimale (DWORD) comment 127.0.0.1 devient 2130706433 et contourne les filtres naïfs. #BugBounty #SSRF #WebSecurity @yeswehack @Hacker0x01 @Bugcrowd intermediateThis content describes a Web Application Firewall (WAF) bypass technique discovered by 0xk4rim. The method involves converting an IP address, specifically localhost (127.0.0.1), into its decimal (DWORD) equivalent, 2130706433. This decimal representation circumvents naive WAF filters that may not properly validate or process IP addresses in this format. The technique is relevant to Bug Bounty hunting, SSRF vulnerabilities, and general web security.
2026-05-27 2026Vulert: CVE-2026-45568: Critical SSRF risk in zrok Python ProxyShare. Attackers may abuse the flaw to send unauthorized requests to internal systems or protected backend resources. #CVE #SSRF #zrok #CyberSecurity #Vulert newsA critical Server-Side Request Forgery (SSRF) vulnerability, CVE-2026-45568, has been identified in zrok Python ProxyShare. This flaw allows attackers to send unauthorized requests to internal systems or protected backend resources.
2026-05-27 2026Mahmoud BARRY ( Docteur JS): Day #11 of #100DaysOfCyber | Exploitation d'un #SSRF Avant hier on a vu la théorie derrière le SSRF (Server-Side Request Forgery). Aujourd'hui place au lab pratique de PortSwigger pour voir comment ça se passe concrètement dans Burp Suite. Le scénario : L'application propose intermediateMahmoud BARRY ( Docteur JS👨‍💻): Day #11 of #100DaysOfCyber | Exploitation d'un #SSRF Avant hier, on a vu la théorie derrière le SSRF (Server-Side Request Forgery). Aujourd'hui, place au lab pratique d...
2026-05-26 2026SNI proxy SSRF vulnerabilities: Misconfigurations exploitation and defense intermediateThis article discusses Server-Side Request Forgery (SSRF) vulnerabilities specifically in SNI proxies. It details how misconfigurations in these proxies can be exploited, leading to SSRF attacks. The content also covers methods for defending against these vulnerabilities. The provided link offers further insights into this technical security topic. No specific bounty amounts are mentioned. → securityboulevard.com
2026-05-24 2026Mahmoud BARRY ( Docteur JS): Day #9 of #100DaysOfCyber | Le Concept du Jour : Le #SSRF Hier lors du Day 8 on a parlé de WAF et de Rate Limiting pour sécuriser notre infrastructure et nos applications. Sauf que les attaquants vont toujours chercher des techniques pour contourner ces barrières. L'une de beginnerThis post, Day 9 of #100DaysOfCyber by Mahmoud BARRY, introduces the concept of Server-Side Request Forgery (SSRF). It follows a discussion on Web Application Firewalls (WAF) and Rate Limiting from Day 8. The author notes that attackers continuously seek methods to bypass security measures, highlighting SSRF as one such technique. The summary focuses on the core topic of SSRF and its relation to bypassing security controls. No bounty amount is mentioned.
2026-05-24 2026Vishal Vishwakarma: Day 11 / 30 SSRF DORKS PAYLOADS First payload should always be Collaborator. Confirm DNS hit then chase metadata. #bugbountytips #ssrf #bugbounty #cybersecurity #infosec intermediateThis entry from Vishal Vishwakarma's 30-day bug bounty challenge focuses on Server-Side Request Forgery (SSRF) techniques. The core advice for day 11 is to prioritize using a Collaborator payload first to confirm a DNS hit. Once confirmed, the next step is to attempt to retrieve metadata. This strategy aims to efficiently identify and exploit SSRF vulnerabilities.
2026-05-24 2026Gray Hats: A critical Angular hostname hijacking vulnerability allows SSRF attacks. Discover the impact on platform-server and how to patch your apps. #Angular #SSRF #WebSecurity #Vulnerability #AppSec intermediateA critical vulnerability in Angular allows for hostname hijacking, enabling Server-Side Request Forgery (SSRF) attacks. This impacts the platform-server component, posing a significant web security risk. Developers are advised to understand the full implications and apply necessary patches to their applications. The content highlights the importance of addressing this vulnerability to prevent potential exploitation and maintain application security.
2026-05-23 2026xHackInSeconds: URL field accepted internal addresses. 169.254.169.254. IAM role credentials in the response. Full S3 and RDS access. #infosec #cloud #ssrf intermediateA vulnerability was discovered where a URL field accepted internal addresses, specifically `169.254.169.254`. This allowed for Server-Side Request Forgery (SSRF), leading to the exposure of IAM role credentials. Consequently, attackers gained full access to S3 buckets and RDS instances. The report highlights a critical security flaw in cloud environments related to SSRF.
2026-05-23 2026Afzal .: They don't attack the firewall directly. They trick your own server into doing it for them. Let's talk about Server-Side Request Forgery (SSRF) and why it's a critical vulnerability in modern web apps. #BugBounty #SSRF #CyberSecurity #InfoSec #InfosecTwitter #WebSecurity beginnerServer-Side Request Forgery (SSRF) is a critical vulnerability in modern web applications. Instead of directly attacking a firewall, attackers exploit SSRF by tricking the application's own server into making requests on their behalf. This allows them to access internal systems or cloud metadata that would otherwise be inaccessible. Understanding and mitigating SSRF is crucial for robust web security.
2026-05-22 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 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 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 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 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 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 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 2026Critical Next.js Vulnerability Exposes Cloud Credentials API keys and Admin Panels news 1 min readLibrary update for Next.js versions 15.5.16 and 16.2.5 addresses CVE-2026-44578, a critical Server-Side Request Forgery (SSRF) vulnerability. This flaw, disclosed as GHSA-c4j6-fc7j-m34r, allows attackers to exploit WebSocket upgrade requests to exfiltrate cloud credentials, harvest API keys, and access internal admin panels by routing malicious requests through the vulnerable Node.js server. Security patches implement stricter checks on WebSocket handling, and organizations are advised to upgrade, implement network-level protections, or block unused WebSocket upgrade requests. → 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 news 2 min readLibrary 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 news 3 min readLibrary 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 news 2 min readAdvisories detail multiple critical vulnerabilities in Next.js and React Server Components, including CVE-2026-23870 (Denial of Service via React Server Components deserialization), CVE-2026-44578 (Server-Side Request Forgery via WebSocket Upgrade Requests), and CVE-2026-44573 (Pages Router i18n Middleware Bypass). Other patched issues include middleware bypass (GHSA-267c-6grr-h53f), cross-site scripting (GHSA-ffhc-5mcf-pf4q), and denial-of-service in the Image Optimization API (GHSA-h64f-5h5j-jqjh). Organizations should upgrade immediately or implement specific mitigations like in-route authorization and network egress restrictions. → 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.

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.