wgcloud resource exhaustion denial of service in minTask endpoint
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
A flaw in the minTask endpoint of tianshiyeben's wgcloud lets a remote attacker, without logging in or any user action, trigger excessive allocation of resources. The attack can cause a limited loss of availability.
Written by a model
Original description
A vulnerability was determined in tianshiyeben wgcloud up to 4.0.1. This vulnerability affects unknown code of the file AgentController.java of the component minTask Endpoint. Executing a manipulation can lead to allocation of resources. The attack can be executed remotely.
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133607 (tianshiyeben wgcloud minTask Endpoint AgentController.java allocation of resources), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133607 (entry last updated 2026-11-20):
Affected:
- tianshiyeben wgcloud: versions 4.0.0, 4.0.1
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133607 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133607 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/tianshiyeben/wgcloud/issues/99
- https://vuldb.com/vuln/441137
- https://vuldb.com/vuln/441137/cti
- https://vuldb.com/cve/CVE-2026-133607
- https://vuldb.com/submit/1050069
- https://github.com/tianshiyeben/wgcloud/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133607
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133607"}.Affected versions
- tianshiyeben wgcloud4.0.0, 4.0.1
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.9/10CVSS 6.9
- No patch5/5No patch listed yet
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
- Would score about 37 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Evidence 8
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133607 |
| Record | NVD · CVE-2026-133607 |
| Other links 6 | |
| Advisory | VulDB · Advisory #441137 |
| Advisory | VulDB · Threat intelligence #441137 |
| Advisory | VulDB · CVE-2026-133607 record |
| Advisory | VulDB · Submission #1050069 |
| Report | GitHub · tianshiyeben/wgcloud · Issue #99 |
| Repository | GitHub · tianshiyeben/wgcloud · Repository |
Questions about CVE-2026-133607
Is CVE-2026-133607 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-133607?
wgcloud: versions 4.0.0, 4.0.1.
Source: cve.now feed data
Related
- CVE-2026-61827netty-incubator-codec-ohttp: BinaryHttpParser should enforce limits for variable lengths fields
- CVE-2026-104199aMQTT: Inefficient Regular Expression Complexity and Uncontrolled Resource Consumption and Improper Input Validation
- CVE-2026-122247Budibase: Unauthenticated global-admin & database creation via tenant-confusion bypass of the one-time init guard (`POST…
- CVE-2026-132275svglib: Exponential resource consumption via nested <use> references in svg2rlg
- CVE-2026-118233Apache Tomcat: Memory leak on HTTP upgrade leads to DoS
- CVE-2026-63202netty-incubator-codec-ohttp BinaryHttpParser: Unauthenticated CPU-exhaustion DoS via infinite loop in field-section decoding
No corrections so far. Something wrong on this page? Report an error.