Security readout for executives and security teams
Plain-English summary
CVE-2025-65807 describes a local privilege-escalation issue in the sd command version 1.0.0 and earlier. A successful attacker could gain root-level control, with full confidentiality, integrity, and availability impact. The public record is sparse, so urgency is high where this tool exists on multi-user or automation-heavy systems.
Executive priority
Treat this as a high-priority exposure review, not an internet-wide emergency. Focus first on shared servers, CI runners, administrative workstations, and any environment where local code execution could become root compromise.
Technical view
The CVE record assigns CVSS 3.1 score 8.4: local attack vector, low complexity, no privileges, no user interaction, unchanged scope, and high CIA impact. It is classified as CWE-266 and described as root privilege escalation through a crafted command. Affected CPE and vendor fields are not populated.
Likely exposure
Likely exposure is limited to systems with sd command v1.0.0 or earlier installed, especially where local untrusted users or privileged scripts can invoke it. The source bundle does not identify package names, distributions, or CPEs.
Exploitation context
The CVE is not listed as CISA KEV in the provided bundle, and no supplied source states active exploitation. The issue is local rather than remote, but no-privilege CVSS scoring means shared systems deserve attention.
Researcher notes
Evidence is incomplete: affected vendor/product metadata is n/a, no CPEs are listed, and the bundle does not name a fixed version. Avoid assuming all similarly named sd utilities are affected without confirming they match the referenced project and version lineage.
Mitigation direction
Inventory hosts and build images for sd command installations.
Identify installed sd versions and flag v1.0.0 or earlier.
Check the upstream repository and vendor package channels for fixed guidance.
Restrict privileged automation from invoking vulnerable sd until reviewed.
Remove sd from systems where it is unnecessary.
Validation and detection
Confirm whether sd is installed on Linux and developer workstations.
Record version evidence for every discovered installation.
Review privileged scripts, cron jobs, and CI tasks that invoke sd.
Check vendor advisories or repository releases for remediation status.
Monitor CVE and upstream references for corrected affected-version details.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-266: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.