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-73633 — Proof-of-concept exploit for Apache Struts S2-072 (CVE-2026-73633), demonstrating CPU and memory exhaustion by sending crafted JSON requests to the Struts JSON plugin. | Kitploit
Tools/GitHubGitHub/cuteecat/cve-2026-73633
Vulnerability AnalysisExploitationWeb Application ExploitationWeb SecurityPenetration Testing
GitHubcuteecat/cve-2026-73633

CVE-2026-73633

Proof-of-concept exploit for Apache Struts S2-072 (CVE-2026-73633), demonstrating CPU and memory exhaustion by sending crafted JSON requests to the Struts JSON plugin.

View Repository
3 days 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-73633 (Apache Struts S2-072) — PoC + Environment

Principle:

It comes from the JSON population of the server-side enabled JSON body plugin ("JSON population" is a core feature provided by the JSON plugin in Struts 2, which can be simply understood as an automatic data conversion mechanism.)

When the parser of the JSON population feature processes JSON arrays, it reads all the JSON content of the request body into memory at once (loading item by item)

Causing memory consumption (and CPU consumption)

Testing

I used WSL2 and Tomcat to deploy a Struts application and built a login page, with username admin and password 123456

In actual testing, the most obvious increase on the machine was CPU usage, followed by memory; and after the request was processed, the CPU usage was released

Once OOM occurs, GC collection is triggered, so the memory will never be completely filled up, far from causing a crash

It only causes server resource strain on the container. After rising to a fixed memory usage value (the OOM trigger point), it stops increasing, and will be repeatedly reclaimed by GC, re-occupied, reclaimed again... ...

CPU growth is directly proportional to the fill value (--size)

Setup

Docker Deployment

root@kitploit:~
git clone https://github.com/CuteeCat/CVE-2026-73633.git
cd CVE-2026-73633
cd docker
docker-compose build
docker-compose up -d
cd ..

POC Execution

root@kitploit:~
python poc.py --url http://127.0.0.1:8080/login.action --local
Download Tool