CVE-2017-11610
Exploitation reported by one source. First attested on 2023-10-19 by GCVE · shadowserver.
- Published2017-08-23
- WeaknessCWE-276
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
The XML-RPC server in supervisor before 3.0.1, 3.1.x before 3.1.4, 3.2.x before 3.2.4, and 3.3.x before 3.3.3 allows remote authenticated users to execute arbitrary commands via a crafted XML-RPC request, related to nested supervisord namespace lookups.
Timeline
dates in UTC- 2017-08-2314:29CVE publishedNVD
- 2023-10-1907:48Listed as exploited by GCVEGCVE
- 2023-10-1907:48Exploitation first reportedGCVE
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
- 2026-10-2319:23EPSS crossed 10 %FIRST EPSS
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-11610?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-11610?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 3.0 | ≤ 3.0 | no fix published | NVD |
| 3.1 | = 3.1.0 | no fix published | NVD |
| 3.1 | = 3.1.1 | no fix published | NVD |
| 3.1 | = 3.1.2 | no fix published | NVD |
| 3.1 | = 3.1.3 | no fix published | NVD |
| 3.2 | = 3.2.0 | no fix published | NVD |
| 3.2 | = 3.2.1 | no fix published | NVD |
| 3.2 | = 3.2.2 | no fix published | NVD |
| 3.2 | = 3.2.3 | no fix published | NVD |
| 3.3 | = 3.3.0 | no fix published | NVD |
| 3.3 | = 3.3.1 | no fix published | NVD |
| 3.3 | = 3.3.2 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 24.x | = 24 | no fix published | NVD |
| 25.x | = 25 | no fix published | NVD |
| 26.x | = 26 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 8.0 | = 8.0 | no fix published | NVD |
| 9.0 | = 9.0 | no fix published | NVD |
1 more product in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- github.comRelease Notes · Vendor Advisory
- github.comRelease Notes · Vendor Advisory
- github.comRelease Notes · Vendor Advisory
- github.comRelease Notes · Vendor Advisory
- github.comVendor Advisory
Detection
read 2026-10-23 19:23 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- 4 repositories, unverifiedivanitlearning/CVE-2017-11610yaunsky/CVE-2017-11610Dungsocool/CVE-2017-11610CyberCTF/vulhub-supervisor-cve-2017-11610 PoC-in-GitHub
Sources
- GCVEexploitation2023-10-19
- NVDCVSS 3.08.8read 2026-10-23
- NVDCVSS 2.09read 2026-10-23
- NVDweakness (CWE)CWE-276read 2026-10-23
- FIRST EPSSEPSS score87.4 %read 2026-10-23
- PoC-in-GitHubproof of concept4read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- 2017-08-23
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2017-11610?
Is CVE-2017-11610 actively exploited?
What is the CVSS score for CVE-2017-11610?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- For a threat intelligence platform: malware, C2 and ransomware indicators over STIX/TAXII.
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.