Unauthenticated code execution via report scheduling service
Published Aug 12, 2026 · Updated Aug 12, 2026
Code injection in WhatsUp Gold before 26.0.2 allows remote attackers to execute arbitrary code through the report scheduling service. Progress identifies missing authentication, externally controlled paths, SSRF, and code injection in the internal service, but has not disclosed the request flow or unsafe operation that links them. Adjacent-network access to the affected service is sufficient, and execution occurs as the IIS application service account.
Summary
What happened
Code injection in WhatsUp Gold before 26.0.2 allows remote attackers to execute arbitrary code through the report scheduling service. Progress identifies missing authentication, externally controlled paths, SSRF, and code injection in the internal service, but has not disclosed the request flow or unsafe operation that links them. Adjacent-network access to the affected service is sufficient, and execution occurs as the IIS application service account.
The record
- CVE
- CVE-2026-65941
- Published
- Aug 12, 2026
- Updated
- Aug 12, 2026
- Vendor
- Progress Software Corporation
- Product
- WhatsUp Gold
- Classifications
- CWE-94, CWE-306, CWE-918, CWE-73, T1210
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 12, 2026CVE publishedPublication date reported by the CVE source.
- Aug 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <26.0.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo