How abraxas/cve-2026-5430 works
This repository is a loopback security-research lab for checking CVE-2026-5430 against WSO2 API Manager. The user starts the lab and runs a Python client, which forges HS256 JWTs, probes scoped Admin/Publisher endpoints with and without a token, and checks responses for evidence of unauthorized access. The graph separates the client’s workflow from the local lab setup. The Python excerpt shows token creation and orchestration; README statements support the lab and target relationships. The request implementation itself was not sampled.
Main entry points: CVE-2026-5430-Abraxas-Labs.py Probe client · run.sh Lab launcher · docker-compose.yml APIM lab
Components 8
PoC client
- Probe client
CVE-2026-5430-Abraxas-Labs.py - HS256 forging
CVE-2026-5430-Abraxas-Labs.py - Endpoint probes
CVE-2026-5430-Abraxas-Labs.py - Response check
CVE-2026-5430-Abraxas-Labs.py
Loopback lab
- Lab launcher
lab/run.sh - APIM lab
lab/docker-compose.yml
Other components
- Researcher
- WSO2 API Manager
Connections 9
- Researcher → Lab launcher: starts lab
README.md - Lab launcher → APIM lab: launches
- APIM lab → WSO2 API Manager: runs APIM
README.md - Researcher → Probe client: runs client
README.md - Probe client → HS256 forging: creates tokens
CVE-2026-5430-Abraxas-Labs.py - Probe client → Endpoint probes: sends probes
CVE-2026-5430-Abraxas-Labs.py - Endpoint probes → WSO2 API Manager: tests endpoints
README.md - Probe client → Response check: checks response
CVE-2026-5430-Abraxas-Labs.py - Endpoint probes → Response check: returns status/body
CVE-2026-5430-Abraxas-Labs.py