React2Shell mass exploitation, WinRAR KEV deadline, Microsoft zero-day, .NET SOAPwn
MAX CVSS
10.0
TOTAL THREATS
4
ACTOR GROUPS
5+
TIME TO EXPLOIT
<5h
Four critical vulnerabilities disclosed this week require immediate action. React2Shell (CVE-2025-55182, CVSS 10.0) is actively exploited by Chinese APT groups, enabling full server compromise of React-based web applications with a single HTTP request β exploitation began within hours of disclosure.
WinRAR path traversal (CVE-2025-6218, CISA KEV deadline Dec 30) is being weaponized by three state-nexus threat actors in phishing campaigns targeting global organizations.
Microsoft Patch Tuesday addressed 57 flaws including one actively exploited zero-day (CVE-2025-62221) enabling privilege escalation on Windows systems.
.NET SOAP client vulnerabilities (CVSS 9.8) allow attackers to write files to disk and achieve remote code execution, with Microsoft declining to patch ("application behavior").
CVE-2025-55182 β Update react-server-dom-* to 19.0.1+ or Next.js 14.2.22+/15.1.4+
β±οΈ Time: ~15 min per service | π€ Owner: Platform/DevOps teams
CVE-2025-62221 actively exploited β Install KB5072033/KB5071417
β±οΈ Time: ~30 min per host | π€ Owner: Windows admins
Check Startup folders (WinRAR), web directories for .aspx shells (SOAPwn), privilege escalation indicators (Microsoft)
β±οΈ Time: ~1 hour | π€ Owner: Security/SOC teams
ββββββββββββ ββββββββββ ββββββββ ββββββ βββββββββ βββββββ βββ
ββββββββββββ ββββββββββββββββββββββββββββββββββββ βββββββββββββ
βββ ββββββββββββββββββββββ ββββββββ βββ βββββββββββββ
βββ ββββββββββββββββββββββ ββββββββ βββ βββββββββ βββ
βββ βββ ββββββ ββββββββββββββ βββ βββ βββββββββ βββ
βββ βββ ββββββ ββββββββββββββ βββ βββ βββββββ βββ
REACT2SHELL β THE EXPLOITATION WAVE
NAME
React2Shell
CVE
CVE-2025-55182
CVSS
10.0
STATUS
Actively exploited; CISA KEV (Dec 5, deadline Dec 26)
One-liner:
Send one HTTP request, own the server. No auth required.
β Check ALL that apply (if 2+ match, prioritize patching):
β οΈ If 3+ boxes checked: Stop reading. Patch now. Come back later.
β° YOUR WINDOW: 18 days left until CISA deadline. Attackers exploited in <5 hours.
While you're waiting for change control approval, deploy these defenses NOW:
1οΈβ£ Block RSC endpoints at the firewall (if app is internal-only)
iptables -A INPUT -p tcp --dport 3000 -s <internal-subnet> -j ACCEPTEffect: External scans can't reach your app (buys you days)
2οΈβ£ Rate-limit POST requests to /_next/data/ (if WAF is available)
Cloudflare: 10 requests/min per IP
Effect: Mass exploitation campaigns fail (attackers move to easier targets)
3οΈβ£ Enable verbose logging for RSC endpoints (free, takes 2 min)
# Next.js: Set DEBUG=* in .envEffect: You'll see exploitation attempts in real-time (early warning)
These won't stop a targeted attack, but they'll filter out 90% of automated scans. Patch is still required β but these buy you breathing room.
β±οΈ Time: ~15 min per service
# Check current versions
npm list react-server-dom-webpack react-server-dom-parcel react-server-dom-turbopack
# Upgrade (example for webpack)
npm install react-server-dom-webpack@19.0.1 --save
# Restart services
pm2 restart all # or systemctl restart your-appβ±οΈ Time: ~20 min per app
β Fixed versions: Next.js 14.2.22+, 15.1.4+
β Malware analysis + IOCs for PeerBlight, CowTunnel, ZinFoq
β Federal patch deadline (Dec 26) + official advisories
β Technical deep-dive + official patch versions
ββββββββββββ ββββββββββ ββββββββ ββββββ βββββββββ βββββββ βββββββ
ββββββββββββ ββββββββββββββββββββββββββββββββββββ βββββββββββββββββ
βββ ββββββββββββββββββββββ ββββββββ βββ βββββββββ βββββββ
βββ ββββββββββββββββββββββ ββββββββ βββ ββββββββββββββββ
βββ βββ ββββββ ββββββββββββββ βββ βββ βββββββββββββββββ
βββ βββ ββββββ ββββββββββββββ βββ βββ βββββββ ββββββββ
WINRAR β THREE APTs, ONE VULNERABILITY
NAME
WinRAR Path Traversal
CVE
CVE-2025-6218
CVSS
7.8
STATUS
Actively exploited by 3 APT groups; CISA KEV (Dec 9, deadline Dec 30)
One-liner:
Malicious RAR archives write files to Startup folder β code execution on next login.
Path traversal vulnerability allows attackers to place files in sensitive Windows locationsβspecifically the Startup folderβvia specially crafted RAR archives. When the victim extracts the archive (or even previews it in some configurations), malicious files auto-execute on next system login.
Three confirmed threat actors:
β° YOUR WINDOW: 20 days until CISA deadline. Attackers have been exploiting for 5+ months.
β Check ALL that apply (if 2+ match, prioritize patching):
β οΈ If 3+ boxes checked: Update TODAY. This is not optional.
While you're waiting for change control approval, deploy these defenses NOW:
1οΈβ£ Block RAR file extraction at email gateway
Office 365: Transport Rule β Block attachments with .rar extension
Gmail: Admin Console β Attachments β Add ".rar" to blocked listβ±οΈ Time: 3 minutes | Effect: Eliminates delivery vector entirely
2οΈβ£ Enable Startup folder monitoring (Sysmon)
# Sysmon config (add to <RuleGroup name="FileCreate">)
<FileCreate onmatch="include">
<TargetFilename condition="contains">\Start Menu\Programs\Startup\</TargetFilename>
</FileCreate>β±οΈ Time: 5 minutes | Effect: Real-time alerts on Startup folder writes
3οΈβ£ Audit existing Startup folders (hunt for compromise NOW)
Get-ChildItem "C:\Users\*\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\" -Recurse | Select-Object FullName, CreationTime, LastWriteTimeβ±οΈ Time: 2 minutes | Effect: Identifies if you're already compromised
β±οΈ Time: ~5 min per endpoint (or deploy via GPO/SCCM)
β±οΈ Time: ~3 min | Effect: Stops phishing delivery entirely
Get-ChildItem "C:\Users\*\AppData\Roaming\Microsoft\Templates\Normal.dotm" | Where-Object {$_.LastWriteTime -gt (Get-Date).AddDays(-60)}β GOFFEE campaign analysis + dual-exploit details
β Federal deadline (Dec 30) + KEV entry details
β Bitter APT campaign documentation + Normal.dotm TTPs
ββββββββββββ ββββββββββ ββββββββ ββββββ βββββββββ βββββββ βββββββ
ββββββββββββ ββββββββββββββββββββββββββββββββββββ βββββββββββββββββ
βββ ββββββββββββββββββββββ ββββββββ βββ βββββββββ βββββββ
βββ ββββββββββββββββββββββ ββββββββ βββ βββββββββ βββββββ
βββ βββ ββββββ ββββββββββββββ βββ βββ βββββββββββββββββ
βββ βββ ββββββ ββββββββββββββ βββ βββ βββββββ βββββββ
MICROSOFT PATCH TUESDAY β 57 FLAWS, 3 ZERO-DAYS
NAME
Microsoft December 2025 Patch Tuesday
CVEs
57 total (3 zero-days)
CVSS MAX
9.0
STATUS
CVE-2025-62221 actively exploited; 2 publicly disclosed
One-liner:
1 zero-day exploited in the wild, 2 publicly disclosed, 19 RCE flaws across Windows/Office.
Microsoft's December 2025 Patch Tuesday addresses 57 vulnerabilities, including:
π΄ ACTIVELY EXPLOITED:
π‘ PUBLICLY DISCLOSED (Not Yet Exploited):
π΄ CRITICAL RCE FLAWS:
β° YOUR WINDOW: Patch THIS WEEK before public PoC drops. CVE-2025-62221 is SYSTEM-level EoP.
β Check ALL that apply (if 3+ match, prioritize patching):
CVE-2025-62221 (Cloud Files EoP):
CVE-2025-54100 (PowerShell RCE):
β οΈ If 5+ boxes checked: You have multiple attack vectors. Patch TODAY.
While you're waiting for change control approval, deploy these defenses NOW:
1οΈβ£ Restrict local admin rights (mitigates CVE-2025-62221)
# Remove users from local Administrators group
net localgroup Administrators /delete DOMAIN\Userβ±οΈ Time: 10 minutes (GPO) | Effect: Limits EoP impact
2οΈβ£ Audit PowerShell scripts for Invoke-WebRequest
Get-ChildItem -Path "C:\Scripts" -Recurse -Filter "*.ps1" | Select-String -Pattern "Invoke-WebRequest|curl" | Select-Object Path, LineNumber, Lineβ±οΈ Time: 5 minutes | Effect: Identifies vulnerable scripts
3οΈβ£ Enable Office Protected View
Group Policy: User Configuration β Administrative Templates β Microsoft Office β Security Settings β Trust Center β Protected View
Enable: "Protected View for files originating from the Internet"β±οΈ Time: 5 minutes (GPO) | Effect: Blocks Office RCE auto-execution
β±οΈ Time: ~30 min per host (or WSUS automation)
β Windows 11 24H2: KB5072033 | Windows 10 22H2: KB5071417
β±οΈ Time: 15-30 min | Effect: Prevents CVE-2025-54100 exploitation
β±οΈ Time: 2 min per developer | Effect: Mitigates CVE-2025-64671
β Official Patch Tuesday details + CVE listings
β Comprehensive breakdown of all 57 vulnerabilities
β GitHub Copilot CVE-2025-64671 technical analysis
ββββββββββββ ββββββββββ ββββββββ ββββββ βββββββββ βββββββ βββ βββ
ββββββββββββ ββββββββββββββββββββββββββββββββββββ ββββββββββββ βββ
βββ ββββββββββββββββββββββ ββββββββ βββ βββββββββββββββββ
βββ ββββββββββββββββββββββ ββββββββ βββ βββββββββββββββββ
βββ βββ ββββββ ββββββββββββββ βββ βββ βββββββββ βββ
βββ βββ ββββββ ββββββββββββββ βββ βββ βββββββ βββ
.NET SOAPwn β WHEN MICROSOFT SAYS "NOT A BUG"
NAME
.NET SOAPwn (WSDL/Proxy Abuse)
CVEs
CVE-2025-34392 (Barracuda), CVE-2025-13659 (Ivanti)
CVSS MAX
9.8
STATUS
Black Hat EU 2025 disclosed; Microsoft declined to patch
One-liner:
Rogue WSDL files β .NET HTTP client proxies write ASPX web shells to disk β RCE.
SOAPwn is a vulnerability class, not a single CVE. It exploits how .NET Framework handles SOAP clientsβspecifically, the ServiceDescriptionImporter class that generates HTTP client proxies from WSDL files.
The Core Bug:
Why This Is Dangerous:
Confirmed Victims:
β° YOUR WINDOW: If you use Barracuda/Ivanti, patch THIS WEEK. Custom .NET apps? Audit NOW.
β Check ALL that apply (if 3+ match, investigate immediately):
Confirmed Vulnerable Products:
Custom .NET Applications:
β οΈ If 3+ boxes checked: You're vulnerable. Start code audit TODAY.
While auditing code or waiting for vendor patches, deploy these defenses NOW:
1οΈβ£ Block file:// scheme at WAF
# ModSecurity rule (example)
SecRule ARGS "@contains file://" \
"id:1001,phase:2,deny,status:403,msg:'Blocked file:// in WSDL URL'"β±οΈ Time: 5 minutes | Effect: Prevents malicious WSDL with file:// handlers
2οΈβ£ Enable file integrity monitoring for web directories
# Monitor for new .aspx/.ashx files
Get-ChildItem -Path "C:\inetpub\wwwroot" -Recurse -Filter "*.aspx" | Where-Object {$_.CreationTime -gt (Get-Date).AddDays(-7)}β±οΈ Time: 10 minutes | Effect: Alerts when new web shells appear
3οΈβ£ Restrict IIS AppPool write permissions
# Remove write access from web root
icacls "C:\inetpub\wwwroot" /remove "IIS APPPOOL\YourAppPool" /Tβ±οΈ Time: 5 minutes | Effect: Prevents web shell creation even if exploited
β±οΈ Time: Vendor-dependent | Effect: Patches CVE-2025-34392
β±οΈ Time: Vendor-dependent | Effect: Patches CVE-2025-13659
Get-ChildItem -Path "C:\Projects" -Recurse -Filter "*.cs" | Select-String -Pattern "ServiceDescriptionImporter"Microsoft won't fix thisβYOU must validate input in your code
β Black Hat EU 2025 presentation + technical analysis
β Service Center RMM vulnerability advisory + patch details
β Endpoint Manager vulnerability advisory + remediation
All four threats share a common pattern: hours-to-exploitation post-disclosure.
| Vulnerability | Disclosure | First Exploit | Time to Exploit |
|---|---|---|---|
| React2Shell | Dec 3, 2025 | Dec 3, 2025 | <5 hours |
| WinRAR | June 2025 | July 2025 | ~30 days |
| Microsoft CVE-2025-62221 | Dec 10, 2025 | In the wild pre-disclosure | Zero-day |
β οΈ YOUR NEW REALITY:
Rate your org's response across all 4 threats (be honest):
YOUR SCORE
0
β 0-99 pts
Critical gaps remain
Click your tech stack to see which threats apply to you:
π‘ Pro Tip:
Running multiple technologies? Your risk compounds. A React app on Windows with .NET backend = exposure to 3 of 4 threats. Use the Red Flag Checklists above to assess your actual risk.
Pre-written messages (copy-paste these):
Slack Your Dev Team
@channel π¨ If you ship React/Next.js apps, drop what you're doing and read this: https://jmfg.ca/security-bulletin/december-10-2025...
Email Your CISO
Subject: URGENT: 4 Critical Vulns Require 48h Patch Window (React2Shell CVSS 10.0)