Loading story…
Two articles focus on server-side request forgery (SSRF): one provides generic, prompt-driven guidance for bug bounty hunters on generating SSRF payloads and bypass techniques (including targeting cloud metadata services like 169.254.169.254 for potential credential theft and escalation paths), and another describes a practical SSRF scenario arising from a misconfigured Sentry “tunnel” endpoint (POST /tunnel/) where attacker-influenced input can cause the server to make outbound HTTP requests across a trust boundary.
A separate vendor blog post discusses Praetorian Guard research claiming discovery of multiple high-severity vulnerability classes (including SSRF, RCE, auth bypass, path traversal, and command injection) across open-source ecosystems and mentions coordinated disclosure efforts, but it is not specifically about the Sentry tunnel SSRF case or the ChatGPT/bug bounty SSRF prompt content. Overall, the actionable overlap across the non-vendor posts is SSRF exploitation mechanics and risk, while the Praetorian post is broader supply-chain/vulnerability-research positioning rather than the same discrete SSRF event.
See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
A separate blog post published a prompt template and examples for SSRF testing against URL-fetching application features such as webhooks, link previews, avatar imports, and PDF generation. It included payloads, filter-bypass techniques, and cloud metadata endpoint targets for AWS, GCP, and Azure.
A security researcher documented a Server-Side Request Forgery issue involving a misconfigured Sentry "/tunnel/" endpoint on a target application. The write-up explains that attacker-controlled input could cause the server to make outbound requests, potentially reaching internal services and private infrastructure.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
osintteam.blog
Open sourceinfosecwriteups.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Security teams reported rapid, opportunistic exploitation of newly disclosed **unauthenticated remote code execution (RCE)** flaws, with attackers moving quickly from scanning to compromise. JPCERT/CC documented active compromise following disclosure of **React2Shell** in React Server Components (**CVE-2025-55182**), where multiple threat actors exploited the same exposed environment within days—initially dropping coin miners (e.g., `xmrig`), then deploying additional payloads including the **HISONIC** backdoor, **SNOWLIGHT** downloader, and **CrossC2**, and culminating in actions like cron-based persistence and website defacement. Separately, GreyNoise telemetry cited by BleepingComputer indicated that exploitation of two critical Ivanti Endpoint Manager Mobile (EPMM) RCEs (**CVE-2026-21962**, **CVE-2026-24061**) was heavily concentrated, with a single bulletproof-hosted source IP (193[.]24[.]123[.]42, PROSPERO OOO/AS200593) responsible for **83%** of observed activity and widespread use of OAST-style DNS callbacks consistent with initial-access validation. Several other items in the set were not tied to a single, specific exploitation event. A Help Net Security “week in review” roundup mixed interviews and assorted security items (including mention of an exploited BeyondTrust RCE) without providing a cohesive, single-incident account, while an NCSC-themed weekly highlights post primarily summarized guidance and calls for participation rather than detailing a discrete compromise. A CloudATG “insights” page contained unrelated, older recap and generic security content, and a Risky Business bulletin focused on law-enforcement developments around **IcedID** operators (including an alleged developer faking his death) rather than vulnerability exploitation activity.
Jun 29, 2026
Multiple application-layer vulnerabilities were disclosed across popular developer components, including an **XSS escaping bypass in LeafKit** (Vapor’s Swift templating engine) and an **SSRF bypass in `@langchain/community`**. Vapor released an updated LeafKit version to address an HTML escaping flaw where **Unicode extended grapheme clusters** could bypass escaping in Leaf templates: Swift treats certain sequences as a single character while browsers parse them as multiple characters, enabling attackers to break out of HTML attributes and inject malicious attributes/scripts. The issue was reported by **bawolff** and fixed in a LeafKit release referenced by Vapor’s advisory. Separately, `@langchain/community` was reported vulnerable to **CVE-2026-26019** (also tracked as **GHSA-gf3v-fwqg-4vh7**), affecting versions **≤ 1.1.13** and fixed in **1.1.14**. The flaw sits in `RecursiveUrlLoader`, where a non-semantic `String.startsWith()` check could be bypassed with crafted hostnames (e.g., `https://example.com.attacker.com`), and where insufficient filtering allowed access to **private/reserved IP ranges** and **cloud metadata endpoints** such as `169.254.169.254`, potentially exposing IAM credentials/tokens in cloud-hosted deployments. A separate write-up describes a *different* SSRF scenario involving a **misconfigured Sentry tunnel** endpoint and provides general SSRF background, but it does not appear to be part of the same LeafKit or LangChain disclosure.
Jun 29, 2026
Multiple web application vulnerabilities have been disclosed, highlighting the risks associated with misconfigured APIs and file upload functionalities. One report demonstrates how a misconfigured GraphQL endpoint, which accepts `application/x-www-form-urlencoded` content types, can be exploited for Cross-Site Request Forgery (CSRF) attacks. Attackers can craft malicious HTML forms to submit GraphQL mutations, such as changing user email addresses, without proper user consent. Another case details a $100 bug bounty awarded for discovering XSS via malicious PDF uploads and input validation bypasses that led to denial-of-service conditions on a coding platform. Further research describes a blind XML External Entity (XXE) vulnerability in a "Check stock" feature, where attackers can trigger out-of-band DNS and HTTP requests using Burp Collaborator, confirming the presence of XXE. Additionally, a $1,500 bounty was awarded for exploiting an image upload feature at Rockstar Games, where a vulnerable ImageMagick instance enabled a chain of attacks including Local File Inclusion (LFI), Server-Side Request Forgery (SSRF), and remote file access via SMB paths. These incidents underscore the importance of strict input validation, secure API configurations, and careful handling of file uploads in web applications.
Jun 29, 2026