CVE-2026-24516
A public proof of concept exists; no exploitation attested.
- Published2026-03-23
- WeaknessCWE-94
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
A command injection vulnerability exists in DigitalOcean Droplet Agent through 1.3.2. The troubleshooting actioner component (internal/troubleshooting/actioner/actioner.go) processes metadata from the metadata service endpoint and executes commands specified in the TroubleshootingAgent.Requesting array without adequate input validation. While the code validates that artifacts exist in the validInvestigationArtifacts map, it fails to sanitize the actual command content after the "command:" prefix. This allows an attacker who can control metadata responses to inject and execute arbitrary OS commands with root privileges. The attack is triggered by sending a TCP packet with specific sequence numbers to the SSH port, which causes the agent to fetch metadata from http://169.254.169.254/metadata/v1.json. The vulnerability affects the command execution flow in internal/troubleshooting/actioner/actioner.go (insufficient validation), internal/troubleshooting/command/exec.go (direct exec.CommandContext call), and internal/troubleshooting/command/command.go (command parsing without sanitization). This can lead to complete system compromise, data exfiltration, privilege escalation, and potential lateral movement across cloud infrastructure.
Timeline
dates in UTC- 2026-03-2317:16CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-24516?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-24516?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 0.0 | ≤ 0.0.0-20260107162243-1101ffcb5672 | no fix published | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
No fix published by the sources we read yet. NVD record
Detection
read 2026-10-23 19:25 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- 2 repositories, unverifiedpoxsky/CVE-2026-24516-DigitalOcean-RCEpoxsky/CVE-2026-24516-DigitalOcean-RCE. PoC-in-GitHub
Sources
- NVDCVE recordread 2026-10-23
- CISA-ADPSSVC decisionpoc2026-03-24
- OpenCVESSVC decisionpoc—
- CISA-ADPCVSS 3.18.82026-03-24
- CISA-ADPweakness (CWE)CWE-942026-03-24
- FIRST EPSSEPSS score2.6 %2026-10-23
- PoC-in-GitHubproof of concept2read 2026-10-23
- OSVaffected packages—
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- 2026-03-23
- Last Modified
- 2026-06-17
- NVD status
- Awaiting Analysis
Frequently asked questions
What is CVE-2026-24516?
Is CVE-2026-24516 actively exploited?
What is the CVSS score for CVE-2026-24516?
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
- 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.