CVE-2026-15409 — A Server-side request forgery (SSRF) vulnerability has been identified in the SMA1000…¶
Key facts
CVE-2026-15409 is a Critical (10.0) vulnerability: A Server-side request forgery (SSRF) vulnerability has been identified in the SMA1000…. This entry ships a detection-only PoC and a Docker test lab. It is on the CISA Known Exploited Vulnerabilities (KEV) catalog (added 2026-07-14), confirming active exploitation in the wild, and is linked to known ransomware campaigns.
Actively exploited — on the CISA KEV catalog
CVE-2026-15409 is listed on the CISA Known Exploited Vulnerabilities (KEV) catalog (added 2026-07-14), confirming exploitation in the wild. It is linked to known ransomware campaigns. Federal remediation deadline: 2026-07-17. Prioritise patching and deploy the detection and prevention rules below.
| CVE | CVE-2026-15409 |
| Severity | Critical (10.0) |
| CISA KEV | Actively exploited (added 2026-07-14) · ransomware |
| Detection / prevention | — |
| PoC | poc.py |
| Source | 2026/CVE-2026-15409/ |
Details¶
English | 한국어
Description¶
A Server-side request forgery (SSRF) vulnerability has been identified in the SMA1000 Appliance Work Place interface. A remote unauthenticated attacker could potentially cause the appliance to make requests to unintended location.
Vulnerability Details¶
| Property | Value |
|---|---|
| CVE ID | CVE-2026-15409 |
| Type | SSRF |
| CVSS Score | 10.0 |
Proof of Concept¶
Download¶
# Download PoC script
curl -O https://raw.githubusercontent.com/fankh/vulnerability-poc/main/2026/CVE-2026-15409/poc.py
Usage¶
# Run PoC against target
python3 poc.py --target <TARGET_URL>
# With authentication
python3 poc.py --target <TARGET_URL> --username <USER> --password <PASS>
⚠️ Warning: This PoC is for authorized security testing only. It uses detection-only techniques and does not exploit or damage target systems.
Test Lab¶
This repository includes a Docker-based test environment with both vulnerable and patched applications.
Quick Start¶
# Clone and navigate to CVE directory
cd CVE-2026-15409
# Start both applications
docker-compose up -d
# Run tests
./run-tests.sh # Linux/Mac
./run-tests.ps1 # Windows PowerShell
Application Endpoints¶
| Application | URL | Status |
|---|---|---|
| Vulnerable App | http://localhost:8080 | Shows vulnerability |
| Patched App | http://localhost:8081 | Demonstrates fix |
Directory Structure¶
├── README.md # English documentation
├── README_KO.md # Korean documentation
├── poc.py # PoC detection script
├── docker-compose.yml # Container orchestration
├── run-tests.sh # Linux/Mac test runner
├── run-tests.ps1 # Windows test runner
├── vulnerable-app/ # Vulnerable version
│ ├── app.py
│ ├── Dockerfile
│ └── requirements.txt
└── patched-app/ # Fixed version
├── app.py
├── Dockerfile
└── requirements.txt
References¶
- https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2026-0008
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-15409
Generated by PoC Generator on 2026-07-15T06:49:35.221219451
Frequently asked questions¶
What is CVE-2026-15409?¶
CVE-2026-15409 is a Critical (10.0) vulnerability: A Server-side request forgery (SSRF) vulnerability has been identified in the SMA1000…. This entry ships a detection-only PoC and a Docker test lab. It is on the CISA Known Exploited Vulnerabilities (KEV) catalog (added 2026-07-14), confirming active exploitation in the wild, and is linked to known ransomware campaigns.
How do I detect CVE-2026-15409?¶
Run the detection-only PoC included with this entry against your Docker test lab to confirm whether a target is affected; pair it with your own IDS logging.
How do I block or mitigate CVE-2026-15409?¶
Upgrade to a fixed version per the vendor advisory; the NVD record lists the affected versions. Use the included PoC to verify your remediation.
Is CVE-2026-15409 actively exploited?¶
Yes. CVE-2026-15409 is on the CISA Known Exploited Vulnerabilities (KEV) catalog, added 2026-07-14, which means it has been exploited in the wild. CISA also links it to known ransomware campaigns. CISA set a federal remediation deadline of 2026-07-17. Prioritise patching and deploy the detection and prevention rules above.
For authorized security testing and research only. See the full source and NVD record.